1
I just found out about XOOPS as of 2.0.6, and it is great. However this update is not very friendly at all.
1. First of all, the permissions in the file are root.root read write execute for *all*. That isn't really something I want to untar into my public directories.
2. So, after going through and fixing all the permissions, I try and load and get a message "Script execution not allowed". It took a while to figure out that was coming from XOOPS and not apache / php. My normal and SSL directories are different, but link to the same directory for Xoops. So the new test in common.php kills that. I changed my version, but it would be nice if the error message was more helpful.
3. Now the "Random Picture" and "New Images" blocks from xoops-gallery are broken. I realize this is a separate project, but to me a minor version point release should not be making such large changes that things are breaking (unless XOOPS gallery is abusing the interface somehow and shouldn't have been working in the first place)..
1. First of all, the permissions in the file are root.root read write execute for *all*. That isn't really something I want to untar into my public directories.
2. So, after going through and fixing all the permissions, I try and load and get a message "Script execution not allowed". It took a while to figure out that was coming from XOOPS and not apache / php. My normal and SSL directories are different, but link to the same directory for Xoops. So the new test in common.php kills that. I changed my version, but it would be nice if the error message was more helpful.
3. Now the "Random Picture" and "New Images" blocks from xoops-gallery are broken. I realize this is a separate project, but to me a minor version point release should not be making such large changes that things are breaking (unless XOOPS gallery is abusing the interface somehow and shouldn't have been working in the first place)..
