Fer_SD
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] LSCache is not supportedThe point is that I don’t wan to use the CDN feature on QUIC.cloud, just the cache. What I need is to rollback the CDN/DNS QUIC.cloud.configuration in order to get rid of any CDN setup (as a fresh installation). Seems like the only thing I can do is to go ahead until I complete all the details of the CDN configuration.
I also tried the “Reset CDN Setup” option on the plugin, but it only resets all LiteSpeed Cache plugin settings related to CDN setup back to their initial state, and disables the CDN. However, this action doesn’t perform anything special and can also be done manually by disabling the relevant options.Forum: Plugins
In reply to: [LiteSpeed Cache] LSCache is not supported- Turn off the CDN -> Done
- Make sure you have the domain key requested and set -> Done
- Make sure the Cache is ON -> Done
- Make sure your header should contain something like: x-qc-cache: hit/miss -> there is no x-qc-cache header, just x-litespeed-tag:
HTTP/1.1 200 OK
Date: Tue, 04 Feb 2025 16:40:55 GMT
Server: Apache
Link: <https://www.lascasasdeandrea.com/wp-json/>; rel="https://api.w.org/", <https://www.lascasasdeandrea.com/wp-json/wp/v2/pages/774>; rel="alternate"; title="JSON"; type="application/json", <https://www.lascasasdeandrea.com/>; rel=shortlink
X-LiteSpeed-Tag: db2_HTTP.200,db2_front,db2_URL.6666cd76f96956469e7be39d750cc7d9,db2_F,db2_Po.774,db2_PGS,db2_,db2_CCSS.1950226e9ae3de157bfaac07f0367a47
Upgrade: h2
Connection: Upgrade, Keep-Alive
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 32149
Keep-Alive: timeout=5, max=100
Content-Type: text/html; charset=UTF-8Forum: Plugins
In reply to: [LiteSpeed Cache] LSCache is not supportedForget my last reply. I have left the QUIC.cloud CDN toggle “ON”
Forum: Plugins
In reply to: [LiteSpeed Cache] LSCache is not supportedI found a way on the CDN tab of the plugin to reset the QUIC.cloud setup. Fortunately, the warning message “LSCache caching functions on this page are currently unavailable!” has dissapeared, but my site is still not supported. The HTTP Header also changed:
HTTP Header
HTTP/1.1 200 OK
Date: Tue, 04 Feb 2025 07:09:59 GMT
Server: Apache
X-DNS-Prefetch-Control: on
X-LiteSpeed-Cache-Control: public,max-age=604800
X-LiteSpeed-Tag: db2_HTTP.200,db2_front,db2_URL.6666cd76f96956469e7be39d750cc7d9,db2_F,db2_Po.774,db2_PGS,db2_guest,db2_,db2_CCSS.e7c535581eb52cf9c2ea8f13abcf5394,db2_UCSS.4d0a989f30b2c5269a1a856db614f40d,db2_MIN.4409008f693da4fe85542a178c1ede61.css,db2_MIN.445c6c4959fa17fc2113adddcc4d26b4.js
Upgrade: h2
Connection: Upgrade, Keep-Alive
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 46373
Keep-Alive: timeout=5, max=100
Content-Type: text/html; charset=UTF-8Forum: Plugins
In reply to: [LiteSpeed Cache] LSCache is not supportedThanks for your quick reply. We are using QUIC.cloud. The CDN setup in QUIC.cloud. was a failed attempt and it is now unfinished, however, I am not able to undo the proccess. Is there a way to delete my setup? Seems like there is no way to rollback and the issue is there.
Thanks in advance.
- This reply was modified 1 year, 1 month ago by Fer_SD.
Forum: Plugins
In reply to: [Simple Calendar - Google Calendar Plugin] Next month arrow with no eventsThanks John for your quick reply. This workaround seems to be slightly inefficient as I should add an event to the last month of the 2 year period periodically (to be specific, once a month). Hope you take into account this issue in forthcoming updates.
Anyway, thanks again for your help.
Forum: Plugins
In reply to: [Simple Calendar - Google Calendar Plugin] Next month arrow with no events- Calendar Start: today
- Earliest Event: the same as the starting date
Thanks for your support.
Forum: Plugins
In reply to: [Simple Calendar - Google Calendar Plugin] Next month arrow with no eventsThanks for replying. However, the “Latest Event” field is currently set to 2 years after the start date.
Update: the issue is back. In my case, upgrading Simple Calendar from v 3.1.31 to 3.1.33, I’m getting an AJAX ERROR on the email sending test page (Post SMTP). Besides, SMTP test on ports 25,465 and 587 was failed.
Regards.
Figured it out. Searching on this forum I found this recent post . As said in the hread, I disabled plugin “Simple Calendar” and the message disappeared. It doesn’t seem to be the best workaround, though.
In any case, I’m experiencing a huge delay on sending the test email. This email indeed arrives, but it takes more than 45 seconds. I believe there should be a problem related to the API, somehow.
Regards,