Skip to content
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

Open
4 tasks done
ssuess opened this issue Nov 5, 2021 · 11 comments
Open
4 tasks done

Caching does not seem to work properly on safari? #1625

ssuess opened this issue Nov 5, 2021 · 11 comments

Comments

@ssuess
Copy link

ssuess commented Nov 5, 2021

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.

  • If a known or unknown user posts a comment using a FF or Chrome browser, comments work as expected
  • if a known or unknown user posts a comment using Safari (desktop or mobile) their comment will not show up for them, it seems to disappear. The page does not have its cache cleared for safari users the same way it does for others, and they will only be able to see their comment (which did in fact post to the backend at least) once there has been a full purge cache initiated from the wordpress admin.

System Information

  • ee cli info:
| OS                | Linux 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:50:10 UTC 2021 x86_64 |
| Shell             | /bin/bash                                                                  |
| PHP binary        | /usr/bin/php7.4                                                            |
| PHP version       | 7.4.3                                                                      |
| php.ini used      | /etc/php/7.4/cli/php.ini                                                   |
| EE root dir       | phar://ee.phar                                                             |
| EE vendor dir     | phar://ee.phar/vendor                                                      |
| EE phar path      | /root                                                                      |
| EE packages dir   |                                                                            |
| EE global config  | /opt/easyengine/config/config.yml                                          |
| EE project config |                                                                            |
| EE version        | 4.3.1                                                                      |
  • lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.3 LTS
Release:	20.04
Codename:	focal
  • docker version
Client: Docker Engine - Community
 Version:           20.10.9
 API version:       1.41
 Go version:        go1.16.8
 Git commit:        c2ea9bc
 Built:             Mon Oct  4 16:08:29 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.9
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.8
  Git commit:       79ea9d3
  Built:            Mon Oct  4 16:06:37 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.11
  GitCommit:        5b46e404f6b9f661a205e28d59c982d3634148f8
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
  • docker-compose version
docker-compose version 1.25.0, build unknown
docker-py version: 4.1.0
CPython version: 3.8.10
OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020
@ssuess
Copy link
Author

ssuess commented Nov 6, 2021

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.

@ssuess
Copy link
Author

ssuess commented Nov 7, 2021

I spoke too soon the problem is still happening. Comment posting and caching is not working properly. Any suggestions?

@ssuess
Copy link
Author

ssuess commented Nov 7, 2021

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.

@ssuess
Copy link
Author

ssuess commented Nov 12, 2021

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?

@ssuess
Copy link
Author

ssuess commented Nov 16, 2021

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.

@dhsathiya
Copy link
Member

Hey @ssuess, we have not faced such an issue as of now.

@ssuess
Copy link
Author

ssuess commented Nov 16, 2021

ok I will try to rebuild the site from scratch I guess and see if that makes any difference.

@ssuess
Copy link
Author

ssuess commented Nov 16, 2021

Do you have a recommended redis plugin or plugins that I should be using? Do they matter at all?

@dhsathiya
Copy link
Member

dhsathiya commented Nov 23, 2021

It is important that you use rtCamp's Nginx-Helper plugin. Which will be there by default if you use --cache flag.

@ssuess
Copy link
Author

ssuess commented Nov 23, 2021

And that is the only needed plugin? It seemed to also install a redis plugin, no?

@joebailey26
Copy link

Yes, this plugin is also installed:
https://wordpress.org/plugins/wp-redis/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants