Conversation
Saving data on the metadata run conflicts with the hidepages plugin. A loop is created and within one sql-query another one is started. This creates lots of 'database locked' error messages
Contributor
|
There are more plugins saving data in the meta renderer. How is the loop created, is it by the p_get_metadata call in the action.php of the hiddenpage plugin? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Saving data on the metadata run conflicts with the hidepages plugin (see https://www.dokuwiki.org/plugin:hidepages and https://github.com/lupo49/dokuwiki-plugin-hidepages). A loop
is created and within one sql-query another one is started. This creates
lots of 'database locked' error messages.