November 17, 2013 at 3:49 pm #20752pacifiersincMember
We are getting this error:
Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/portugal/public_html/wp-includes/general-template.php:2168) in /home/portugal/public_html/wp-content/plugins/wp-affiliate-platform/wp_affiliate_platform1.php on line 8
Can you help?November 17, 2013 at 10:42 pm #20753
This error started when you added the cache plugin? I am trying to understand the relationship with caching and your issue. That error usually happens when another plugin or theme is outputting code after the header is already sent. Have you recently added any plugin to your site?June 2, 2014 at 4:13 pm #20754benyoungMember
Hi, I am getting the error “security check failed on login” which is on a completely blank pages (apart from that message). It occurs when entering an incorrect user details but the usual validation doesn’t fire.
It was suggested elsewhere in the forum that the culprit might be W3 Total Cache however I have implemented the tips at the beginning of this thread, and the error is still happening – any ideas?
Thanks for this great plugin!June 2, 2014 at 4:22 pm #20755
Please empty your cache then try DISABLING the cache, simply to prove or disprove the problem is cache related.August 15, 2014 at 3:54 pm #20756ValMember
These instructions don’t apply anymore to the latest version of WP Total Cache. Please advise because I’m seeing a warning in my dashboard. “You have the W3 Total Cache plugin active. Please make sure to follow these instructions to make it work with the WP eStore plugin.”
Is there some change necessary to make my shopping cart work? Please advise. Thank you.August 15, 2014 at 11:36 pm #20757
The latest W3 Total Cache version is 0.9.4 (as of now). This instruction is definitely working for that version. So maybe go over the instruction one more time to see where you made a mistake.October 9, 2014 at 3:08 pm #20758lightpublicationsMember
I’m using W3 9.4 — I don’t see where to put the fix in…October 9, 2014 at 10:30 pm #20759
Go to the “Page Cache” menu From the left hand side admin dashboard menu of the cache plugin. In this page look for a field called “Rejected Cookies”. Do you see that field?October 22, 2014 at 10:08 pm #20760thehipgurusguideSpectator
I added the 3 lines in the “Rejected Cookies” field under the “Page Cache” – but before and after there is this other error listed
W3 Total Cache Error: Files and directories could not be automatically created to complete the installation.
Following their directions I added some lines to .htaccess but the error remains.October 22, 2014 at 10:12 pm #20761
The issue is not related to our plugins:
[https://wordpress.org/support/topic/w3-total-cache-error-files-and-directories-could-not-be-automatically-created-t]December 3, 2014 at 10:13 am #20762WandriskaMember
I have just installed w3Cache and have followed the instructions in https://support.tipsandtricks-hq.com/forums/topic/using-the-plugins-with-w3-total-cache-plugin
however I am still having problems
AN item bought generates a new shopping cart with that item after each product.
What do you suggest?
AndrewDecember 3, 2014 at 2:04 pm #20763
Could you please describe in detail, the problem, with links and steps that were followed to recreate the problem?March 16, 2016 at 11:10 pm #20764royhenigMember
i dont see rejected cookies area nor advanced…March 17, 2016 at 3:47 am #20765
Check the following screenshot which shows you exactly where this field is in the W3 Total Cache plugin:July 25, 2017 at 9:05 pm #20766Maximillion6Member
Hey all – had some problems with file downloads.
I’m using the store plugin to sell multiple PDF books packaged in a single RAR for easy download.
Have W3 Total Cache installed and did all the steps listed here (added exceptions and turned off the gzip compression).
Still have a problem with file downloads. Basically every file is turning into a 1k download and the RARs are corrupted. Not sure why this is happening and could use some advice. Clearly one of the two (caching or store) are causing problems.
Quick note – turning off caching eliminates the problem as you might guess
- You must be logged in to reply to this topic.