Hello simotux,
To find source of the problem we need to do some troubleshooting first. Let’s start with enabling debug.log. To enable it, open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to:
define('WP_DEBUG', true);
In order to enable the error logging to a file on the server you need to add yet one more similar line:
define( 'WP_DEBUG_LOG', true );
In this case the errors will be saved to a debug.log log file inside the /wp-content/directory.
Depending on whether you want your errors to be only logged or also displayed on the screen you should also have this line there, immediately after the line mentioned above:
define( 'WP_DEBUG_DISPLAY', false );
The wp-config.php is located in your WordPress root directory. It’s the same file where the database configuration settings are. You will have to access it by FTP or SFTP in order to edit it. I would need then to see content of the debug.log file – so please paste it to pastebin.com and give us a link.
Also I noticed that you asked that question on stackoverflow – did you tried that suggestion http://wordpress.stackexchange.com/questions/231004/w3-total-cache-cloudflare-ec2-instance-settings-do-not-persist#comment343116_231004 ?
kind regards,
Kasia
Hello Kasia,
I turned on WP_DEBUG and WP_DEBUG_LOG and I can see log errors on frontend but WP doesn’t save *.log on wp-content. May I have to wait some minutes?
I didn’t see that comment but actually my configuration already has separate RSD istance.
Thank you,
simotux
Hello simotoux,
You also need to add
define( 'WP_DEBUG_DISPLAY', false );
Can you log to your site and see then if there was debug log created? Also you will need to perform switching to new istance to generate right error.
BTW I don’t know if you know but you can export your settings and if they are lost again then you can import them quickly in General settings of the plugin.
kind regards,
Kasia
Hello Kasia,
It was just a random error. Here the log:
http://pastebin.com/PUiZbaQK
Yes, I do about import/export settings. Really appreciate this function.
Today I needed to create another node on Elastic Cache and I try to change node’s name on W3 Total Cache settings, but It not take my settings.
I guess there are some problems with file permission or something else about it. I tried to change chmod to 777 (temporarily) for w3tc folders but the problem persists.
Thank you,
simotux
Are you load balancing over multiple EC2’s? The W3 config settings write to a file. So if you have multiple EC2’s changing the settings won’t save the file on every EC2. Also, if you are load balancing whenever a new EC2 spins up it’s going to use whatever settings are in the deploy package. We are also on Amazon and we just have the config file set as part of the repo. So when we want to change settings we update the config file in the repo and then deploy to AWS.
Hello tomcat90,
I load balancing over multiple EC2’s only when CPU utilization > 60 and for the rest of time i only have one istance. I save W3 settings only in that case. I have two environments: preview and production that I align with same informations. The only differences between them is the final database.
Thank you.
