Closed n3tman closed 5 years ago
Given the truncated paths, I can't tell if this is thrown from an error in this plugin specifically. Can you provide more details to clarify how you know this plugin is causing this?
I think plugin is the reason since disabling it fixes the issue.
Attaching an image of a full backtrace log. I guess plugin somehow replaces $page->content() with a Dom object, thus generating an error. Can't tell more since I don't know PHP..
I think plugin is the reason since disabling it fixes the issue.
I get the exact same error, in the exact same manner: after second page load. Disabling the plug-in 'resolves' the bug.
I cannot replicate this with the newest release candidates. The plugin does manipulate the DOM of the content, but even using a summary separator the error does not throw. Could either or both of you share the Markdown or Twig that causes the error?
Could either or both of you share the Markdown or Twig that causes the error?
Alright, the markdown doesn't seem to matter, as it also occurs on pages with no markdown.
I've uploaded some twig files and added you as collaborator. (I don't know if it works, as I've never used this functionality, here's an invitation link: https://github.com/MelleNi/twigfiles/invitations)
Perhaps I should note that setting Caching
to No
in the system settings bypasses (?) the issue. I tried to see if changing the subsettings would do anything, but to no avail. Twig caching can be turned on. So, for now my site functions, but without caching.
Tusen takk fra Trondheim
I managed to provoke the error with both caches enabled, and I think I have a fix. Please test v1.1.1-beta.1 to see if that resolves the issue. Cache has to be cleared after update, which Grav will do automatically if installed with Admin or the GPM.
@n3tman, @MelleNi, does that beta work for you? If so I'll release it as stable.
@OleVik Sorry for the late response > wasn't able to open my laptop for a while.
I think I just successfully managed to update to the beta version, and everything seems to work fine now. I have re-enabled caching and there's been no problems so far.
Amazing job, very much appreciated!
Great to hear, released v1.1.1 as stable.
Somehow I get this error after installing/activating the plugin on secondary page load (after cache is generated):
Log:
twig_first is set to true (both system-wise and page-wise)
Disabling the plugin solves the issue.
Grav version: v1.5.10
Theme: inherited from Quark v1.2.6
Installed plugins: