newbthenewbd / grav-plugin-tinymce-editor

TinyMCE Editor Integration Plugin for Grav
Other
60 stars 10 forks source link

404 Error when loading tinymce files #26

Closed dsanchez-at4 closed 4 years ago

dsanchez-at4 commented 5 years ago

After updating the plugin to version 1.2.1 and Grav to 1.5.3, the plugin stops working. If you open the console you can see some 404 errors, as it's trying to load the tinymce.js files from /user/data instead of /user/plugins as it did on previous versions. I have rolled back the plugin to version 1.1.8 and it's working fine.

newbthenewbd commented 5 years ago

As far as my understanding goes, the errors are intended behavior - since v1.2.0, customized TinyMCE versions can be put in /user/data/tinymce-editor, and thus preserved when further integration plugin updates appear. The plugin then checks for the existence of the /user/data/tinymce-editor subsets at runtime, throwing that unfortunate error for when one of the guesses is mistaken. The plugin has already used a similar method to find language files, previously, and if You haven't seen an error, it means that it had just managed to find Your particular selected language in the first guess.

However, the above should not affect the working state of the TinyMCE version located under /user/plugins/tinymce-editor, and, as I have just confirmed on my test installs, the error appears, and the plugin still works.

If the editor fails to load nevertheless, that is of course a problem. Could You please name a browser in which the unintended behavior is exhibited by TinyMCE, and, if possible, provide a zip with a minimal Grav install exhibiting the issue? It seems to me that the most likely cause would be the new TinyMCE version ceasing to support a browser, which can then be solved by putting the v1.1.8 js directory along with its contents into /user/data/tinymce-editor.

Thanks for reporting!

newbthenewbd commented 5 years ago

The 404 errors should no longer appear in v1.2.2. Could You please test that version to check whether the issue is still there?

Thanks!

newbthenewbd commented 4 years ago

Closing due to inactivity - if the problem persists, feel free to comment or open a new issue.