[Escalated to 2nd Tier] Views stop BeaverBuilder Archive page for Woo shop working
This support ticket is created 3 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
Hi, I wasn't able to find anything obviously wrong in wp-admin that would cause this issue. I don't see any Views, Content Templates, or WordPress Archives that would be interfering like this. I'm going to try creating a clone of your site so I can install it locally and run some additional tests. Please stand by and I will keep you updated here.
Quick update to let you know I was able to replicate the problem in my local clone of your site, but even with other plugins deactivated and a default theme active I was unable to determine the reason why Views and WPML would be overriding the Shop page design like this when a secondary page is edited with BB. I've escalated this issue to my 2nd tier support team for further investigation, and I will keep you posted here as I receive information.
Just to let you know, we are using the staging site for a WPML bug that disables the Inline Editing in BB.
When you have a solution let me know and I'll try it on the staging.
Hi, I apologize this is taking longer than expected. I haven't forgotten about this issue. My 2nd tier team is investigating the problem but has not found a good solution yet. Yesterday I received an update that they thought the problem was related to the translation status of the BB Themer Layout "Shop Page BB", but I could not confirm that. Even after completing the translation in my local copy of the site, the problem returned when I edited the custom page you mentioned using the BB editor. I replied back to my 2nd tier team that the problem was not resolved by completing the translation, and they are still investigating. I will keep you posted as I receive more information.
Hello, just another quick update to let you know my second tier support team is still investigating this problem. This has proven to be a difficult issue to debug. I will keep you up-to-date as I receive additional information.
I received an update in our weekly meeting this morning that 2nd tier has been working through the problem and is focused on rewrite rules at the moment. Working backwards through the request lifecycle they have found that the issue occurs before pre_get_posts, but have yet to isolate the problem. I'll keep you posted here if there is any news to report.
This issue has been further escalated to our developers for investigation. Our second tier team was not able to pinpoint the cause of the difference in rewrite rules, applied as far back as the parse_request hook with -1 priority. The matched rule is "shop/?$", but that rule does not exist in the broken case flow. I'll keep you posted as I receive more information.
