Our facebook group facebook.com/groups/redaxscript is the right place for questions, remarks and suggestions.
Not on Facebook? Join our IRC channel #redaxscript on irc.freenode.net for instant support.
Nope, this is not a bug. It's a feature that makes it possible to style modules over your template.
The parent has to be an ID. The documentation sucks! But we are re-factoring the navigation NOW and the new documentation is much better. :) Might even manage to add the ability to filter by category alias as an alternative to category ID...
We plan to improve our websites documentation for Release 2.3.0 - since it will introduce the new $template->tagStuff() and we update most of the template related functions it does not make sence to update it before that release. https://github.com/redaxmedia/redaxscript/issues/177 https://github.com/redaxmedia/redaxscript/issues/178 It would be helpful to get some ideas, great to get some concept, awesome if someone has the time to write it! :-) If you are asking why the documentation is so bad? Well, developers are lazy about documentation and sometimes you are missing the point of view that users have.
You found a bug, because ".../zz-article-1" should throw an error...
Thats the common practice for security reason, I totally agree. I guess you have an special hoster or even server? Most webspaces do not offer a public and application folder, so Redaxscript (like many other CMS) does not support this. Maby you can hack arround with .htaccess but I have no idea how...
Nothing special about my web host or server - its cpanel, probably the most common hosting environment around!
So you have an dedicated server? Shared hosting is the common hosting world wide and for that reason most CMS work the way they do...
Nope, cpanel on shared apache server - nothing special. Just wanted to keep all the redaxscripts files & folders in a /rs-2-1-0 sub-folder. Not a problem though - they'll just have to go in root. Just makes upgrades more painful with no quick roll-back.
I also find it annoying
yeah it sucks as hell
We need a checkbox after the button like to stay after saving - or even better save using AJAX... but the admin is the very last part in the refactoring process - sorry the only way to speed things up is to contribute code :-)
I'd argue that the default behaviour should be to stay on the article after save/cancel. I see no reason to go to the article list. After an edit, who would not want to see the result of their edit? I'd really like this one fixed asap, in 2.2.0, as it's not something I can hack myself, so how much of a $donation would it require?
Something like that? It's just a Firebug concept
Gary Aylward wrote some great tuts about modules, his webpage is down atm so please use Google Cache. cache:http://garya.org.uk/software/redaxscript/modules-tutorial-part-1 cache:http://garya.org.uk/software/redaxscript/modules-tutorial-part-2 cache:http://garya.org.uk/software/redaxscript/modules-tutorial-part-3 cache:http://garya.org.uk/software/redaxscript/modules-tutorial-part-4
Thanks Henry, I've studied Gary's tutorials and they're excellent, so I can create modules now and that's all fine. However, I have a project that requires the article to be manipulated prior to display, and in a more complex way than can be achieved by data insertion using <function>...</function>. So my module needs access to the article output prior to display. In MediaWiki I'd use a hook such as "ParserAfterTidy" which provides direct access to the $text variable containing the article's HTML. So anything changed in $text will be displayed. Is something possible in Redaxscript? It looks like the equivalent to MediaWiki's $text in Redaxscript is $output in "contents.php" but I can't see how to hook into it to manipulate it from within a module.
you cannot manipulate the output rendering with the old codebase, but maby we provide $content->getContent() in 2.3.0
Thanks Henry, $content->getContent() would be very useful, ideally referencing the parsed article ready for rendering. In the meantime I think I can hack what I need to do by adding a function call to contents.php line 121 after hook('article_end'). But could you just explain the purpose of the statement ".hook('article_end')" on line 120? ...as this is where I'd expect the call to an article_end function to include some data, perhaps $output. But I'm used to using MediaWiki where hooks include the data to be manipulated, and the term 'hook' may mean something completely different in Redaxscript? ...hope I'm making sense!
hooks in redaxscript include function calls and not data :-)
Thanks Henry, much appreciated. I had to set the publish state to 'unpublished' to get this to work, but I guess that makes sense as its now specifically called via the template rather than through the extras mechanism. I'm happy with that, and learnt a lot about RS in the process! ...however, I still think it would be logical, via the admin console, to be able to show an extra for all articles in a specific category. Or even include categories in the extras->customize->articles dropdown so multiple pages can share the same extra. For example, all news articles could have an extra to join a mailing list or link to an archive, all easily configured in admin rather than php. Anyone else have a view on this?
The big question is... what is the behaviour most people like to have. It's not a big task to change the codebase to meet your needs.
I'd certainly find that behaviour useful. Can I suggest adding a new extras->customize option called "Articles in category" with a dropdown with all the categories? ...but only if others would find this useful too - any takers out there?
we are on feature freeze because of codebase refactoring, we can only change the behaviour atm.