sholaytech

Thanks @isaumya I have applied the changes and I now see those user buttons back, so I am not sure if the problem was entirely down to me having previously included the “https://” to the domain name while creating the cache rules or not, because as soon as I took them off and used the new 3rd cache rule they started showing again.

I still have a concern though and wondered if it is something to worry about or not. When I used the Google chrome inspect tool to check the pages whilst I am logged in I noticed that the cf-cache-status is DYNAMIC on all the pages on the site even when in the wp-admin pages. Should this be so as I also observed your plugin showing as x-wp-cf-super-cache: no-cache ?

See the details received for this below:

• alt-svc: h3=”:443″; ma=86400, h3-29=”:443″; ma=86400
• cache-control: no-store, no-cache, must-revalidate, max-age=0
• cf-cache-status: DYNAMIC
• cf-ray: 7834924b6942743b-LHR
• content-encoding: br
• content-type: text/html; charset=UTF-8
• date: Mon, 02 Jan 2023 15:36:41 GMT
• expires: Mon, 02 Jan 2023 15:36:41 GMT
• nel: {“success_fraction”:0,”report_to”:”cf-nel”,”max_age”:604800}
• pragma: no-cache
• report-to: {“endpoints”:[{“url”:”https:\/\/a.nel.cloudflare.com\/report\/v3?s=yYMl9Nw4b4AQTUuGN8rEyZMfPIB9s%2FGFu7cqNAZipzRy269f8lcy7WaraJtzliTIzyrfvl3SJVyFO%2FeSZ04LVZ6Hsti1vfJHm4geBtC%2BUUOExwlB5kkwbhdwGcjZN7D2″}],”group”:”cf-nel”,”max_age”:604800}
• server: cloudflare
• set-cookie: dokan_pro_vendor_verify_b58cf00a3b09d42f81aad723759b6b98=4852238454ad210caab17441aad2b033%7C%7C1672674101%7C%7C1a9f4e4c9db8625776172be2e51b10c4%7C%7Ca%3A0%3A%7B%7D; expires=Mon, 02-Jan-2023 15:41:41 GMT; Max-Age=300; path=/; secure; HttpOnly
• vary: Accept-Encoding
• x-wp-cf-super-cache: no-cache
• x-wp-cf-super-cache-cache-control: no-store, no-cache, must-revalidate, max-age=0

When I am logged out, the cf-cache-status is still DYNAMIC and your plugin shows as : x-wp-cf-super-cache-active: 1

See details

• alt-svc: h3=”:443″; ma=86400, h3-29=”:443″; ma=86400
• cache-control: s-maxage=31536000, max-age=60
• cf-cache-status: DYNAMIC
• cf-ray: 783494eb8bac72af-LHR
• content-encoding: br
• content-type: text/html; charset=UTF-8
• date: Mon, 02 Jan 2023 15:38:28 GMT
• nel: {“success_fraction”:0,”report_to”:”cf-nel”,”max_age”:604800}
• report-to: {“endpoints”:[{“url”:”https:\/\/a.nel.cloudflare.com\/report\/v3?s=pVry54dDqHNbF8Q0NSupdl6mxTDPtAmRpKvndbKRkwLWgaMQfiCJQjWdsWgtCcuW%2BZsSwI0Rug8Ha6YExRCwye5g85v5pDB064DeorgEhLGEFB4y28Xv1za4Vp2UO5YX”}],”group”:”cf-nel”,”max_age”:604800}
• server: cloudflare
• vary: Accept-Encoding
• x-wp-cf-super-cache: cache
• x-wp-cf-super-cache-active: 1
• x-wp-cf-super-cache-cache-control: s-maxage=31536000, max-age=60
• x-wp-cf-super-cache-cookies-bypass: swfpc-feature-not-enabled
• Is this how it is supposed to behave? I noticed on your plugin you said that it should be “HIT” for the cf-cache-status
• You can check for yourself if you do not mind.

Thanks a bunch for your help.

@isaumya I don’t know how wordpress managed to change what typed to https://alacada.co.uk” but what I meant to type is

“is it just “alacada.co.uk” or “https://alacada.co.uk” because all along I have used the latter (https://alacada.co.uk) to setup the cache rule for the site.

Thanks”

@isaumya is it just “alacada.co.uk” or “https://alacada.co.uk”, because all along I have used the latter (https://alacada.co.uk) to setup the cache rule for the site.

Thanks

Hi @isaumya

https://safenote.co/r/63b2db30a391a1@32800208

Thanks

Hi @isaumya I have tried to recreate the problem in the video on the link below.

Looking forward to your response.

thanks

Dear @isaumya Happy New Year and thank you for your response.

I have followed your above instructions again to remove the 4th cache rule and re-enabled the “Remove Cache Buster Query String”. However, the problem is still there, and now when I even click on a button that should take me to the user’s profile on the frontend, it takes me back to the login page to re-enter credentials and does the same thing over again.

I am not using any other cache plugin except for the Perfmatters as recommended by you. You can also create a dummy account to see this issue for yourself.

Thanks for your help.