I load the demo into rw, and then publish. The result: the pages load up, click on ‘admin’, change a text and click save - the green ticks appear. Then return to the ‘content’ page and get nothing but ‘Unable to load cms file with the id …’ for all the content.
Have contacted jw support but no solutions found yet.
OK, found your issues, we have a nice tool that Joe created to help in situations like this, and here is what it says:
TotalCMS Debug Info
You do not have the PHP gd extension enabled
curl extension is not enabled on this server.
Failed to create TotalCMS directory: /total-cms
PHP version: 5.6.11-1ubuntu3.1
HTTP_HOST: learningopportunities.co.za
SERVER_NAME: learningopportunities.co.za
So looks like you will need to contact your host and ask them to turn on the PHP gd extension and enable curl.
I believe you need to have the place where the content is trying to be made, and that is not it. Since it is on your root, that is the folder you need to check
where is that? as far as i understand the stack does not try to access anything that is not in the public web folder - your support guys told me to look at the folder (as shown in the path on the image). if you have another place, you need to tell me where it is.
NB: This is NOT a site i have created, it is your unmodified demo that is not working.
Since our support guys are me and Joe, and I know I did not tell you to check permissions on that folder, it must have been Joe, but I do not think he did either. Can you show me a screenshot of the root of your server? See mine as an example.
Robert Ziebol, Dec 3, 22:26:
Hey Chris,
There are a couple of issues on your server that is causing this.
First, curl extension is not enabled on this server. You need to contact your host and ask them to turn that on.
Second, the TotalCMS lib directory is not writable. Please fix the permissions on the directory: /var/www/html/easycms/rw_common/plugins/stacks/total-cms
To fix this, read this FAQ
Try adding group write permissions to that folder. That would make it 775. If that does not work, try 777. The permissions vary based on your web server configuration. What is happening is that the web server does not have permission to create the /cms-data folder that the CMS needs to save all of the data.
is easycms going to create a cms-data subfolder in every folder that contains cms content or is there ONE folder for the whole site?
What i am trying to determine is which folders must have the dreaded and non-advisable 777 permission for easycms to work? I can’t use this system if it means my whole web root has to have 777 permissions (which i have just set and finally managed to get easycms to work)…
knowing how easycms manages folders and data files will certainly help to make working with it clearer.
/cms-data is a centralized folder that is created at the root of your website.
I agree that 777 is not ideal. If 775 or 755 does not work, then you will need to modify your web server setup so that Apache runs as your user or as a user that is apart of a group that has permissions that create files/folders. This is not an uncommon thing to have web servers have access to create files.
