Visual editor broken

[murphytwin]

The visual editor on the site stopped working after uploading the site to my client’s server. I’ve tried the editor with other themes and it works fine. It only becomes a problem when activating the swagger theme. I tried a new copy of the theme without my css customizations but to no avail. I have tried several different methods and nothing is working for me.
Any help or insight you can provide would be appreciated. Thanks.

Topic

[Jason Bobich]

Hello,

This would be some sort of conflict on your server with how the theme inserts the shortcode generator. It’s most likely some sort of security thing, but you’ll need to figure out the cause with your host to bypass.

Also, it could be a simple matter of a permissions issue with the files of the theme. Did you upload the theme manually? It’s possible when you did this you have files of the theme that have file permissions like 777, which will flag security blocks with some hosts.

A good way to troubleshoot is to load the Edit Page screen in Google Chrome with the Developer Tools open and view the “Console” tab. Now, when the TinyMCE editor breaks, there will be some javascript error telling you why.

See screenshot: http://www.uploadblvd.com/uploads/image_518b0dc427ba5.png

If you show your host whatever this error message says, they can most likely look at your server’s error log, determine what the cause is, and adjust your configuration.

[murphytwin]

Thanks. The console revealed a server error that caused “swagger/framework/shortcodes/tinymce/editor_plugin.php” not to load. See here. http://tinypic.com/r/17bpf4/5

I’ve disabled it for now in themeblvd.php. Ill send the server error to the host, but if you know of anything on your end that is causing this, could you let me know?

If it helps, I was working on this website in one subfolder on the server and then moved it to another folder when the site went live.
Thanks for your help.

[Jason Bobich]

Any time you get an internal server error, the only way to really know the cause is to look at your server’s error log. There’s most likely some sort of setting on your server that is getting flagged by the file’s processes. I’m sure if your host just looks at what that is, there’s a simple answer.

[Author]

Replies