So... Its been FOREVER since youve released 2.1.0, and there is still no real support on the US site for it.  There is no 2.1.x forum, and noone seems to be talking about it, so here I am.

I was looking at the code, trying to figure out if it is worth converting my site to 2.1.x, and I'm a little confused about something.  The way you are sanitizing variables now... here is an example..

If I look around at your code, sometimes you are using 'request', sometimes 'REQUEST', sometimes '_REQUEST', which is it suppose to be?  With or without the '_'?  Also, it seems like you are using request for everything, shouldn't you also be using '_get' and '_post' , ect...?  The above $op example, in the old code that is a _GET....

Thanx,
SLiCK_303  

 

Ok, so I look in includes/classes/class.variables... and in function _validLocation, it basically says it doesn't matter if you use the _ or not.  But what about always using 'request', shouldn't a person be using post, get, etc as well?


Thanx,
SLiCK_303

p.s. nice job on rev2028 btw.....  

 

Ok, so I guess maybe I should have looked into it before I bothered posting...  If I look up what $_REQUEST is, it means, An associative array that by default contains the contents of $_GET, $_POST and $_COOKIE. So I guess its just a way of saying use any of the 3....

So, onto my next question....  You are no longer using $prefix in your database calls.  Is your code backward compatable so a person can still do it the old way?

What I'm trying to figure out is how much of a pain in the butt it will be to try and convert to 2.1.x from my old 2.0.5+ site.  I have a boat load of modules, blocks, and themes, and forum mods.


Thanx,
SLiCK_303  

 

ok - first of all I would suggest to wait for the new installer which is ready but needs to be tested before release. The new installer is needed to run an upgrade from 2.0.x to 2.1.0 smooth and without any problems. In the mean time you can start to do all needed changes in your modules and blocks.
Our goal with EVO-CMS was to improve security, multi language capability and performance. Compatibility to Nuke Evolution and/or PHP Nuke was not the main focus. Therefore old modules will not run with EVO-CMS. As you have mentioned in your posting above, you found the most important change of the core files $_GETVAR
Another big improvement is the XHTML compliance and the PHP5 compatibility. To be honest, it would be a huge amount of work to convert a website which runs lot of modules and mods to be 100% compliant with EVO-CMS programming standards. The good news is: If you have managed the $_GETVAR changes, most of the work is done to get a module to work with EVO-CMS. You can still make use of $prefix, but it is recommended for the core database tables to make use of the constants. For forums mods you have to make sure that the mods are running with the category hirarchie mod which is part of EVO-CMS
If you have managed to get a module, block or mod work with EVO-CMS, please let us know. Would be nice to have some more downloads at evo-mods.com  

 

I pm'd you a block.....