We have built many pages in BB using the default permalink settings. We now want to change the permalink settings to “Post Name” instead of default.
When I first changed the permalink settings I was getting a “500 Internal Server Error.” I sent this to our IT team and they informed me that “the fallback script was set to /index.html which is not provided by wordpress package, changed to /index.php.”
This fixed the “500” error, but now when I change the permalink settings to “Post Name” I can no longer access the page builder. I can see the content that was built, but clicking the page builder button has no effect.
Same problem in IE 11.0.21 and Chrome 46.0.2490.71 m
I can create a login for you to access the site, just let me know what email address to use.
Sorry for the trouble. I am helping Billy look into this one for ya.
I think we might need FTP access if that’s possible? I want to peek at your .htaccess file and a few other things.
Also, you mentioned, “When I first changed the permalink settings I was getting a “500 Internal Server Error.” I sent this to our IT team and they informed me that “the fallback script was set to /index.html which is not provided by wordpress package, changed to /index.php.””
Do you have any more details on this? Particularly, what fallback script? I am not sure exactly why, but I have a feeling whatever caused the original 500 error is also interfering with Beaver Builder.
Ah, it’s nginx? That’s good to know. I hate to say it, but we’re all collectively a lot more familiar with Apache. I am not sure what to suggest here. The issue has to be related to the server configuration as there are no other plugins that could be causing a conflict.
Can you get any other insight from you IT team? Are they aware of the issue with the page builder? Also, is there any server-level caching going on?
