(blocks/items_spot.php line 20 AND 119)
$sel_items = explode(',', $options[3]);
$sel_items = is_array($options[3]) ? $options[3] : explode(',', $options[3]);
Cusix Software
$sel_items = explode(',', $options[3]);
$sel_items = is_array($options[3]) ? $options[3] : explode(',', $options[3]);
In 2.0.x, I beleive that each option within the $options array was check to know if it was itself an array. If so, then the option was implode and transformed into a string. So the actual $options saved in the database was a serialized version of :
So, a single code core install of XOOPS supporting multiple sites with their own, dedicated, databases. Single point to patch. Possible?
Yes i can explain it easily
in Preferences --> General setting --> set USE CUSTOM SESSION to "YES"
then groups_users_link table will be emptied.
DirectoryIndex index.html index.htm
DirectoryIndex index.html index.htm index.php
davidl2 wrote:
Quote:
kapeman wrote:
Since module compatability varies greatly by XOOPS version, I would like to see the modules categorized by version compatability at a high level and then by category.
For example:
2.2.3 Modules
Admin tools, Community etc.
2.0.13.2 Modules
Admin tools, Community etc.
Splitting up the modules by compatible versions would be a good idea...