-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caching does not seem to work properly on safari? #1625
Comments
I just updated to 4.4.0 from 4.3.1, and it seems to have fixed it? I will watch this for a couple of days and come back here to close if there are no issues. Thanks. |
I spoke too soon the problem is still happening. Comment posting and caching is not working properly. Any suggestions? |
Well for now I followed the instructions here to disable redis for this site. Awaiting a response to decide what I should do next, if this is a bug or just a misconfiguration. |
Any advice at all on what to do here? Do post comments in a safari browser (or mobile safari) on a redis cached site work for everyone else? |
Nothing at all? Am I the only one having this problem? Has no one else had any problems with ee redis caching of comments? No one? Any guidance at all here would be very appreciated. Thanks. |
Hey @ssuess, we have not faced such an issue as of now. |
ok I will try to rebuild the site from scratch I guess and see if that makes any difference. |
Do you have a recommended redis plugin or plugins that I should be using? Do they matter at all? |
It is important that you use rtCamp's Nginx-Helper plugin. Which will be there by default if you use |
And that is the only needed plugin? It seemed to also install a redis plugin, no? |
Yes, this plugin is also installed: |
Hi I have searched the docs and discussions and haven't found mention of this. My newly setup cache enabled wordpress site does not properly deal with comment postings on Safari web browsers (mobile or desktop), but DOES deal with them properly on FF and Chrome.
System Information
The text was updated successfully, but these errors were encountered: