-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Superuser: "You are not allowed to add pages" #38
Comments
I recently installed dokuwiki to track county cis documentation. I added this plugin to expedite adding new pages; however, I am consistently running into this bug. I do want to add note, that you don't have to re-install the plugin to enable functionality, simply disabling and re-enabling it will suffice. Another workaround, which I just stumbled across:
Unfortunately, by doing this when logged out the Add Page is still present. However, if you ACL is set correctly logged out users will be blocked from creating a new page anyway. |
Has exactly he same issue as emp302 described (Hrun 2014-09-29d) The plugin is a must if you expect another random users should create a pages in the wiki. |
DokuWiki speeds up browsing through the wiki by caching parsed files. Did you try to prevent the page from being cached by using the NOCACHE tag?
|
Placing NOCACHE on the page that contains the form solves this issue. I suggest placing this solution prominently on the README as the plugin is unusable without it |
Closing as I'm not able to reproduce this with latest version of the plugin (tested on DokuWiki Jack Jackrum). Feel free to reopen and provide details if the problem still exists. |
Nevermind, my test page had |
I added a FAQ on the plugin's page to document the workaround. |
Environment: Release 2014-09-29b "Hrun"
Symptom
Reproducibility: Always
Is this a known issue?
How does plug-in evaluate whether user is permitted to create pages in a given namespace (Dokuwiki ACL or file permissions)?
Thanks a lot for this great plug-in, which is a must!
The text was updated successfully, but these errors were encountered: