search

newbthenewbd / grav-plugin-tinymce-editor

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

Bug in TinyMCE Editor Integration v1.2.0 with Grav 1.5.1 + Gantry v5.4.26 #24

Closed Legolasindar closed 5 years ago

Legolasindar commented 5 years ago

GRAV: 1.5.1 GANTRY: 5.4.26 TinyMCE Editor Integration: 1.2.0

My site works well, not problem. Today, i updated TinyMCE Editor Integration to 1.2.0 version, and after this, the Recompile CSS option of Gantry not works, say this:

500 Internal Server Error
Oops, UniformResourceLocator: Absolute stream path with relative lookup not allowed ().

I tried disabling the TinyMCE plugin, and works again. I tried in another site in another hosting, and the same situation. Before uptade, works well, after update, nots works.

newbthenewbd commented 5 years ago

As serious as this issue sounds, I've been thus far unable to reproduce it. Are You possibly running Grav from within a subdirectory (i.e. https://www.example.com/gravsite)?

Thanks for reporting!

newbthenewbd commented 5 years ago

Inspired by this report to look again at the code, I've just released v1.2.1, ought to improve how the absolute URL generator works for the Grav installs not directly located in webroot. However, the release is rather unlikely to solve this problem, as I'm honestly still quite clueless as to what it might be caused by.

Could You please assemble a minimal Grav install exhibiting this problem, and share a backup of it? If v1.2.1 hasn't somehow fixed the issue, I'm afraid that I might not be able to trace it soon without getting such install into my hands.

Legolasindar commented 5 years ago

With a fresh install i cant reproduce this bug. But i dont know what happen, because only appear this error in my web with your plugin.

P.D: I tried my web in root / and in a subdirectory, and have the same error in both.

newbthenewbd commented 5 years ago

While I am still unable to determine the exact source of the problem, the improvements introduced in v1.2.2 are likely to affect it. Could You please check whether the issue persists in that version?

Thanks!

Legolasindar commented 5 years ago

The problem not appear now. It seems that it is fixed. Nice works, thanks 👍 :)