= Description = ## Please read this page. Lines prefixed with ## such as this one are comments, ## you can remove them (except for those after the "Plan" section.) ## Please follow the instructions given in those comments and the text. ## After creating the bug page, please subscribe to it! We may have questions ## that only you can answer, and if you get email when your bug changes it'll ## be much faster to get it fixed since you can answer the questions! When you go to a link to a missing page, and you don't have write access to the wiki at the moment, MissingPage behaves oddly. The "Create new empty page" text is just text -- it appears, but isn't clickable. The list of templates appears and IS clickable, but of course clicking on any of them will yield an error. I would suggest: * If the user has write access, continue as before. * If the user lacks write access: * If the user isn't logged in, suggest logging in (unless login is in actions_excluded) rather than presenting the templates or the create new page link. * If the user IS logged in and still lacks write access, or login is in actions_excluded, display helpful text such as "You don't have permission to create this page" instead of the templates or create empty page link. * Always display the list of potentially similar pages. == Steps to reproduce == ## Describe the steps needed to reproduce the bug. If we can't reproduce it, we probably can't fix it. 1. Just visit, say, http://www.complete.org/FakeFakeFake == Example == ##Add URL that show the bug, screenshot or test wiki markup that fail... URL: http://www.complete.org/FakeFakeFake ##{{attachment:screenshot.png}} ##{{{ ##Example wiki markup that fail ##}}} == Component selection == ## Where you think is this bug happening ? (general, plugin [plugin name], theme [theme name], ... * general == Details == ## If you got a traceback, please save the traceback page as html and attach here: ## [[attachment:traceback.html]] ## if the bug is in this wiki, just kill the table and write: This Wiki. ## If a traceback is not available, please fill in the details here: || '''!MoinMoin Version''' || 1.8.5 || || '''OS and Version''' || Debian lenny || || '''Python Version''' || 2.5.2 || || '''Server Setup''' || || || '''Server Details''' || || || '''Language you are using the wiki in''' (set in the browser/UserPreferences) || || == Workaround == ## How to deal with the bug until it is fixed It would also be nice to see a config option to let me refer to a differently-named MissingPage for this purpose. = Discussion = From #moin (submitter is CosmicRay) {{{ Is there a way on MissingPage to turn an attempt to find a missing page into a search request? Alternatively, to turn it into a 404? ah, never mind on the 404. I see it is a 404 already. i also searches for "similar" pages, see right column ah. I'm thinking a config option to give the name of the page to use for MissingPage would be handy. I'm not seeing one. Is there one? it is translated, so it is e.g. FehlendeSeite for german the reason is that I've got two hosts pointed at the same data/underlay dir. One will be for a read-only public website, the other for editing. I don't want to send a 404 message saying "Create this page" for the read-only site. does it do that for users without write perms? yes it's sorta funny. The "Create new empty page" is not a link, but just non-clickable text. But all the templates are a link clicking on em gives a permissions error of course file a bug please :) * CosmicRay makes a note }}} I think, macro should be used to implement described behaviour, not config option. -- EugeneSyromyatnikov <> There are two issues here: configurability of MissingPage, and the behavior of MissingPage. I assume your comment refers to configurability. As for that, there is already page_front_page in the configuration. I don't see how a macro could help in this situation. If you are referring to the actions of MissingPage, I agree the macro should handle all of the cases I enumerated automatically. There should be no configuration needed for it to stop presenting irrelevant options to people that don't have write permission. --JohnGoerzen <> The idea is giving ability to display information based on permissions. We can't detect that (there are to many ways to point on action, and is we should add options what to do, if user can't do it, it wouldn't be wiki way), but can manage that in particular places (in places where it can be expected). Btw, i tried to make some scratch of macro. It's crappy, but i can't done it better. Usage: `<>` [[attachment:AclBasedText.py]] -- EugeneSyromyatnikov <> = Plan = ## This part is for Moin``Moin developers: * Priority: * Assigned to: * Status: fixed by [[http://hg.moinmo.in/moin/1.9/rev/1f0c87a833a8|1.9 1f0c87a833a8]] if you don't have permissions you should get PermissionDenied. ---- ## If you are a moin core developer, replace the category to Category* in these cases: ## Category MoinMoinNoBug - if this is not a bug. ## Category MoinMoinBugConfirmed - if you can confirm the bug on current code. ## Category MoinMoinBugFixed - after the bug is fixed in current code. CategoryMoinMoinBugFixed