Also, a histroy/revert ability might be needed if the css module is developed so that vandalism can be reversed with out having access to a page that custom css disables.
Forum Thread
Forum
» Forum / Per page discussions
» Page Manager Tutorial - part 1
This is the discussion related to the wiki page Page Manager Tutorial - part 1.
You can already do things like [/pagename/edit/true/norender/true/noredirect/true Edit] to force-edit a page that is otherwise inaccessible. These special arguments are not properly documented, nor really consistent, but we'll get that done at some stage.
Okay, but what if a CSS Module was developed, and the problematic code was in a comment?
Sure, we could use /norender/true and disable comments, but that would lose all of the valid comments as well.
Is it possible for /norender/true to actually render part of the comments module? i.e. a list of comments, but with the actual comment source not rendered, so that we can edit individual comments and fix issues there as well.
Shane Smith
ethicalwd.com - Blog - Wikidot Editor - Docs
NEW! ZoomPlanner - A new tool for freelancers and small business! Join the waiting list.
i did not know about /norender/true the
Indeed, this is a functionality that I pushed forward on the Pro Wishlist. It's very important, especially for the use of iframing foreign javascript that could cause the page to redirect elsewhere. (Helmuti knows what I'm talking about XD)
Is it possible for /norender/true to actually render part of the comments module?
I don't think we would want to, for that would defeat the purpose of /norender/true. Because people have the capacity to use iframes in their wikidot comments, they have the capacity to…
Jesus, I've just realised a way to destroy forum threads…
λ James Kanjo
Blog | Wikidot Expert | λ and Proud
Web Developer | HTML | CSS | JavaScript
TRhis works near perfect - even the norender.. noredirect is working..
http://forum.wikidot.com/forum/t-185954/forum-problem#post-599094/norender/true/noredirect/true does not help!
I have quick fingers from piano play and could stop the rendering by hand ( on my old machine - this is very slow rendering and I waas fast enough to stop the browser in the best moment..
This is not a good idea to use the redirect module….
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
I have to say — you guys find a new way to impress me around nearly every turn. Which normally takes some doing. Makes me wish I had time to do much more than look on.
The page looks beautiful, particularly for a work-in-progress.
I am using XP and FF 3.0.11 and I find it difficult to access the popupinfo… lets say I wanted to edit a page from the list. if the popup appears and I move my pointer down to click on *edit… the next popup appears…
I would suggest make the popup visible at the same height but right from the link. If you move right you can access the popup, if you move down you get the next one
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
I found the same problem, and fixed it by moving the popup just a little higher. But your solution is better. Do you want to provide the CSS changes so I can incorporate them?
I know that you want me to give you the CSS-code, but I need to see what is in there… I am more a trial and error person with a risk-calculator on my desk.
Will change nothing but I need to see admin:manage SO…
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
/forum/t-185842/page-manager-tutorial-part-1#post-
