-
Notifications
You must be signed in to change notification settings - Fork 6
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
No provision for messages #58
Comments
Mikio supports the msg function. As with #57, can you provide the version of DokuWiki and a list of Dokuwiki plugins so I can try and replicate the issue you are experiencing? |
good evening, This happens on both the current stable DW release and the current snapshot release. No extensions except mikio template and mikio plugin. On your configuration manager screenshot, there is a message. I observe the same thing, no problem in configuration manager when I save the config. But on standard wiki page, messages don't show. I took a quick look at the code. It appears that there is no call to html_msgarea in |
Thanks. I will add that in over the next few days (we have a Cyclone/Typhoon warning in place at the moment). I want to also fix the jQuery issue in the external typeahead library you raised in another issue, testing it against the snapshot in the same release. |
Great ! |
I've gone through my code to work it how I've missed this. Mikio has a This has revealed a bug, the config should be a dropdown of options, not a text field, so the next release fixes this. The next release will also default to I believe I went around html_msgarea() and printed messages manually due to an issue in older versions (it could of just been a brain-fart at the time), something I need to test before the release in a few days. |
Fixed in an earlier release |
When displaying pages, mikio does not display messages sent by the msg DokuWiki function.
With another template, I can see the messages on the page, but not with mikio. Do the test with this test wiki: https://pamarei1zai7phaop.bidule.https443.net/start?do=check
We expect to see something like this, but there is nothing instead:
The text was updated successfully, but these errors were encountered: