| Re: Moving xoops from local machine to Sourceforge.net |
| by Scionwest on 2007/1/10 3:20:41 I posted a reply on sunday night on this topic but somehow it's missing. I don't know what happened. Anyway, I did as you suggested and it still didn't fix the problem. What I wound up doing was placing XOOPS on a different host server and then I will just have my index page re-direct the users from tbgengine-suite.sourceforge.net to the new host server. I get the feeling XOOPS just isn't compatible with sourceforge. It works great on the new host so I just need to start configuring it now. Thanks alot for the help! To bad we couldn't get it running on sourceforge. It's nice to know that XOOPS has a great community that is willing to help out. Regards, Scionwest |
| Re: Moving xoops from local machine to Sourceforge.net |
| by wodnick on 2007/1/7 22:14:01 Hi Scionwest. Bad news... https://sourceforge.net/docs/E07/en/#permissions "All content on the project web servers that needs to be written by the project web servers must be world-writeable and be placed under the /tmp/persistent directory (create a subdirectory for use by your project files)." "Place the data in the /tmp/persistent directory, accessible from and shared between the project shell and web servers. Projects should create their own subdirectory in /tmp/persistent and make frequent backups of the data. We strongly discourage the use of file-writing applications with our services, due to the security implications of our shared web environment. Users of applications in the project web services that require file-writing are strongly encouraged to look for alternatives that can use a MySQL database for data storage instead." Make directory templates_c inside insecure directory mentioned above, then change settings in common.php file from: define("XOOPS_COMPILE_PATH", XOOPS_ROOT_PATH."/templates_c"); to: define("XOOPS_COMPILE_PATH", "/tmp/persistent/templates_c"); Do the same with /upload and /cache directory. define("XOOPS_UPLOAD_PATH", XOOPS_ROOT_PATH."/uploads"); define("XOOPS_CACHE_PATH", XOOPS_ROOT_PATH."/cache"); For security reason, insert something between /tmp/persistent and directory like templates_c, b.e. /tmp/persistent/mysecretdirectory/templates_c/ regards, wodnick ![]() ps. I'm going to sleep now, but early morning this page must work!!! ;) |
| Re: Moving xoops from local machine to Sourceforge.net |
| by Scionwest on 2007/1/7 21:50:54 I also just noticed that my XOOPS appears to be running V1.8, so maybe if I installed the 2.0.16 it would fix this problem? If you recommend that do I just copy all the files over the existing ones and modify mainfile.php again? Thanks Scionwest |
| Re: Moving xoops from local machine to Sourceforge.net |
| by Scionwest on 2007/1/7 21:36:05 Thanks for the reply, I just did what you said and set the templates_c directory to 777, but I am still recieving all of those errors. The templates_c directory is empty, and I turned off debug to check if the page will load and it is still a blank page. I noticed that if I placed the files back into the templates_c directory that I removed the errors are reduced to very few. Quote:
Any other thoughts? Thanks, Scionwest |
| Re: Moving xoops from local machine to Sourceforge.net |
| by wodnick on 2007/1/7 20:03:51 Hi Scionwest! Set templates_c folder permision to 777 (write to all). http://winscp.net/eng/docs/task_properties http://winscp.net/eng/docs/ui_properties Tick all RWX 9 checkboxes. Voila ;) regards, wodnick
|