Hello,
Can you please elaborate more about the issue? If possible, share a screenshot of the issue.
Thread Starter
Sarah H
(@sarahrbcom)
I’ve used this plugin to create a simple list of products with categories, it uses a custom post type:
https://ww.wp.xz.cn/plugins/catablog/
The primary list looks like this:
https://www.dropbox.com/s/w4em5kgruhlqony/catalog-main-view.PNG?dl=0
The category dropdown produces a view like this:
https://www.dropbox.com/s/b2enpaatzbjmn0m/catalog-category-view.PNG?dl=0
But it SHOULD look similar to the primary listing. See the code for Catablog’s archive template here:
https://www.dropbox.com/s/u7nsozu02uod1y9/catalog-archive-template.PNG?dl=0
After inspecting the code, it seems OceanWP’s blog archive template is overwriting Catablog’s. When I switch to a different theme, Catablog’s archive template displays as it should.
Hello, if the plugin uses the default theme template, it is normal, you need to contact the plugin author to ask him if he can create a custom template for its plugin.
Thread Starter
Sarah H
(@sarahrbcom)
It uses it’s own template, as I said in my last message and provided a screencap of.
Hello Sarah, I don’t know this plugin but if it was using its own template, it will not use the theme template, there is a conflict somewhere, you need to directly contact the plugin author to know what is wrong.
Thread Starter
Sarah H
(@sarahrbcom)
Thanks for the response. I’ve already had a lengthily discussion with Catablog support. (https://ww.wp.xz.cn/support/topic/category-archive-template-not-being-used/). When we found that no other theme creates the issue and that it is centered around OceanWP, they said I needed to contact you. Can you help me at all with this?? I know it’s easy to point the finger at the other guy, but it just leaves the customer high and dry. As a pro developer who works with many clients and is currently vetting products for large licences, how the support pans out is a very critical telling point.
Thanks for your responses thus far.
Hello, unfortunately, in the free support, there are a lot of restrictions, I’m not allowed to go in the backend of your site to see what can be wrong and try to solve it.
