Facebook group

Our facebook group facebook.com/groups/redaxscript is the right place for questions, remarks and suggestions.

Keep in mind to use the Github issue tracker to submit bugs.

Balázs Szilágyi

Balázs Szilágyi

Hello! I found redaxscript about a week ago, and i love it. Currently i am trying to make openid login work (yes i wrote an email few days ago). I have the button, i set up everything, but i have a little problem: when i click the login button i placed (form action="/?login") it loads site.com/?login%2522 page. It should redirect the user to the given service openID login page, but it doesn't. How could i handle the get request? (I include my php code in index.php and place it every page by placing it via template. (I put the php code /includes))
Comments
Henry Ruhs

Henry Ruhs

Woah :D Great that you not afraid to make your hands dirty! That's fantastic. You should not touch the core of Redaxscript or put complex things like that into templates, because this might cause massive update issues. We provide modules with a so called hook system. Take a look into these tutorials: http://garya.org.uk/redaxscript/modules-tutorial-part-1 http://garya.org.uk/redaxscript/modules-tutorial-part-2 http://garya.org.uk/redaxscript/modules-tutorial-part-3 http://garya.org.uk/redaxscript/modules-tutorial-part-4 1. Write a module with a formular 2. Use the center break hook to redirect incoming POST 3. Learn from other modules how it works 4. Feel free to ask me here
Balázs Szilágyi

Balázs Szilágyi

For some reason i found it easier to place 2 php files in /include and write a few extra lines to the core, than creating a module^^. Tomorrow i'll try again. (i had to google what do you mean by formular :D) yeah a placed a form using $output = form_element(.... etc. And yes! I used hook(__FUNCTION__ . '_start'); (and end) For a few days i just read other modules code, it was quite clear how should i make this work. But i will definitely write it into a module, it will be easier at future updates, you are right. // I selected this cms because it is clear at the first sight (almost) how it's works, really lightweight, not using any framework (zend, laravel,...) so it's easier for me to understand how this cms is working. BTW i won't use it as a blog engine, i will use it for something completely different...^^
Balázs Szilágyi

Balázs Szilágyi

Oh I almost forget: thanks for the reply :)
Henry Ruhs

Henry Ruhs

Are you planing something like a portal or community driven thing?
Henry Ruhs

Henry Ruhs

What’s new in PHPStorm 8? Did you know? Redaxscript is part of their Open Source program, developers and contributors can request a free license for PHPStorm.
Nerbiz Dijkstra

Nerbiz Dijkstra

Hi Henry, A while ago we discussed how I could contribute to Redaxscript, and some other good talks :) however, I've been extremely busy lately and it looks like it's going to stay that way. So just to clear things up, that you know why.
Comments
Henry Ruhs

Henry Ruhs

No problem Nerbiz, maby you can contribute in another way if you like this project. Share it with other people: tweet on Twitter, star Redaxscript on Github, invite people to the Facebook group... there are many ways to give something back
Azeez Abass

Azeez Abass

I am working on a module to include a full width slider. Im not sure how to create a setting page for it. Any help? Thanks in advance
Comments
Azeez Abass

Azeez Abass

i think there should be a better tutorial for making modules, i dont understand what the startup.js does --------------edit---------- never mind i found it
Henry Ruhs

Henry Ruhs

you are right, documentation is not the best... would you like to contribute one? :-)
Azeez Abass

Azeez Abass

i am working on a slider module, would u like to look at it and help me, its guaranteed to have bug or 2. I send it as soon as im done
Henry Ruhs

Henry Ruhs

No problem. Simply post some Github repository or gist...
Henry Ruhs

Henry Ruhs

Codename - Redaxpress You may call me crazy but the goal of milestone 2.3.0 is to load a Wordpress theme into Redaxscript with the help of a module. The upcoming release 2.2.0 is finished (still needs testing), lets take a look what we plan for 2.3.0. Basicly it is about refactoring the codebase for templating (navigation, content, comment, search etc.) and writing our own template syntax. Roadmap for 2.3.0: https://github.com/redaxmedia/redaxscript/milestones/2.3.0
Comments
Henry Ruhs

Henry Ruhs

If you ever thought about a donation - now is the time :-)
Nerbiz Dijkstra

Nerbiz Dijkstra

I think you're crazy :P but seriously, this seems like a nice thing! And very much possible
Jörg Steinhauer

Jörg Steinhauer

like this idea!
Nigel Moore

Nigel Moore

I rarely find a client who's willing to have a generic template, so generally end up creating from scratch or modify an existing one, and Redaxscript is a great platform on which to do this :-) However, I suspect the popularity of Wordpress is based on the massive amount of templates and modules which can create boring and same-looking websites very quickly. For those users, this feature could be very useful and dramatically increase the uptake of Redaxscript sites. However, as Redaxscript is "aimed at geeks", would the community be able to handle the increased support enquiries from novice developers who might have got on fine with Wordpress? It could create an unwanted support burden? Just a thought!
Nigel Moore

Nigel Moore

Just wondering what the official line is within Redaxscript developers on undeclared/undefined PHP variables, constants and indexes, as there appear to be a lot of references to these within the Redaxscript codebase? Although PHP permits them, general consensus seems that it's not the best thing to have. Ref: http://stackoverflow.com/questions/4261133/php-notice-undefined-variable-and-notice-undefined-index My own concern is that, when debugging, I could easily suppress them, but that may mask something in my own code that I should know about, such as other undeclared variables, which I was taught to avoid if possible. Thanks.
Comments
Henry Ruhs

Henry Ruhs

The old codebase does include hundret of warning and stuff like that, we know about this. Touching untested code like this is not a good idea, it may cause bugs and finally there is no reason to put time into this. For that reason we decided to refactor everything instead of cleaning up the mess. Is this a proper answer for you?
Nigel Moore

Nigel Moore

Good answer! ...now I realise the importance of refactoring! Thanks Henry.
Henry Ruhs

Henry Ruhs

And the good part of refactoring - we have tested code all over the place that cannot break. https://coveralls.io/r/redaxmedia/redaxscript
Henry Ruhs

Henry Ruhs

Redaxscript now on Bountysource... "Bountysource is the funding platform for open-source software. Users can improve the open-source projects they love by creating/collecting bounties and pledging to fundraisers." https://www.bountysource.com/trackers/351960-redaxmedia-redaxscript https://github.com/redaxmedia/redaxscript/labels/bounty
Comments
Henry Ruhs

Henry Ruhs

In short words: if you want a feature you can put some money on it to get it done ... btw: I will not earn that money, the person who does the job will get everything!
Nigel Moore

Nigel Moore

Nice move!
Nigel Moore

Nigel Moore

Henry, I have 2.2.0 running from github master. Can you guide me toward the new "jump" to feature please? ...as I don't see any difference when saving an article at the moment.
Comments
Henry Ruhs

Henry Ruhs

Well, once you edit and save the article - you now have the article list URL but with an #alias jump...
Nigel Moore

Nigel Moore

See it now... works well. Great improvement!! :-) It would still be even better to return to the article if that's where the edit was invoked from (which is what I was hoping for), but in the meantime, this is a good workaround. Much appreciated!
Henry Ruhs

Henry Ruhs

Glad you like it... I know it is not the very best solution, but an improvement :-)
Henry Ruhs

Henry Ruhs

There are only little frontend improvements but one is the automatic keyword generation from h1 - h3 and strong tags... give it a try
Nigel Moore

Nigel Moore

Ok. ...but currently seem to be unable to create an article if the alias contains a hyphen? Get an "alias is incorrect" error when saving.
Henry Ruhs

Henry Ruhs

Today there was an update on my side project about CSS naming conventions. Take a deeper look at http://ncss.redaxmedia.com if you teamwork with other frontend developers...
Comments
Nigel Moore

Nigel Moore

AFAIK the only reason to use '-' (hyphen) as opposed to '_' (underscore) or 'A' (camelcase) for CSS id and class attributes is to support CSS attribute selectors. The best example is from http://www.w3.org/TR/CSS21/selector.html#attribute-selectors relating to languages such that "The following rule will match for values of the "lang" attribute that begin with "en", including "en", "en-US", and "en-cockney": *[lang|="en"] { color : red } Ok, so that's not an id or class attribute, but to have that styling functionality available for id and class attributes could be very useful. So I think it's not essential for Redaxscript to change from '_' to '-' but would certainly bring it into line with current trends and enable attribute selectors functionality.
Henry Ruhs

Henry Ruhs

Correct, it is not essential for Redaxscript during the 2.x.x releases but I started to use (hyphen) inside the new OOP classes and currently give them an "className" option to provide the old classes. No doubt, it is clever to follow the global trendings but refactoring all classnames is a massive amount of work :-)
Nigel Moore

Nigel Moore

Yep... lots of work, minimal benefits. Personally, if there's development resource available I'd prefer to see a solution to my post of 20 July (annoying behaviour #1), and I'm sure this would benefit all users, not just a small minority. For me, usability far outweighs neat code, and every major usability improvement would encourage me to make another $$$donation (as I'm a crap programmer). Redaxscript is Great already, but can be greater!!
Henry Ruhs

Henry Ruhs

First try the 2.2.0 release with the "jump" to feature :-)
Nigel Moore

Nigel Moore

...but back to the topic in question: your NCSS document raises interesting debate. Some say that instead of .form-content we should use form.content, but I suspect the former will be less expensive as CSS reads selectors from right to left. Same with div.advert where .box-advert would probably win in the performance stakes and is more readable. I've also seen .feedback-list-header_count which is horrid! Certainly, for performance and readability, avoiding child selectors is paramount, so your NCSS doc makes absolute sense. Nice read.
Nigel Moore

Nigel Moore

Is there a way to set 'Headline' to 'disabled' by default on all new articles and extras? Thanks.
Comments
Henry Ruhs

Henry Ruhs

Nope, there are no global settings for things like that... sorry You could write a simple module using Javascript to automatical switch the select fields to the value you want...
Nigel Moore

Nigel Moore

Thanks Henry, I'll go with your suggestion, very helpful.
Henry Ruhs

Henry Ruhs

Yeah and if you are smart enough, the module can learn from your past and present setting choices and you store them inside a web storage :-) http://www.w3schools.com/html/html5_webstorage.asp Would be a very nice module for many people here...
Nigel Moore

Nigel Moore

For the project I'm working on, this needs to be a global setting for all users on all devices so no need to remember choices. This is the jQuery that solved my issue: if( r.constants.ADMIN_PARAMETER == 'new' ) { $('select#headline>option:eq(1)').prop('selected', true); }
Henry Ruhs

Henry Ruhs

well done - you can do it that way
Powered by Redaxscript 2.1.0  •  Design and realization by Jörg Steinhauer & Henry Ruhs