londonnut

Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter londonnut

    (@londonnut)

    Hi Tyler,

    The issue didn’t go away, however the good news is – my hosting and Litespeed were able to get to the bottom of the underlying cause. Litespeed is not caching PrettyLinks because the HTML code sent from PrettyLinks begins with a <meta tag instead of <!DOCTYPE html> – which is a requirement for Litespeed to detect and cache it.

    The fix would require a small code re-adjustment from Litespeed please.


    Details as received, below:

    Regarding the Pretty Links plugin’s redirections not being cached by the LiteSpeed Cache plugin (and so causing high CPU usage when the website is being heavily visited),
    LiteSpeed’s support have finally identified that the Pretty Link plugin is the underlying cause.

    When a web page is redirected, the Pretty Link plugin sends HTML code that starts as follows:

    <meta http-equiv="refresh" content="10;URL='https://starfreebies.co.uk/'" />

<!doctype html>
<html lang="en-GB">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <link rel="profile" >
        <meta name="th

    But LiteSpeed says:

    per guideline , all HTML page should start with <!DOCTYPE html> , but the output from that plugin is <meta …
    ref: https://html.spec.whatwg.org/multipage/syntax.html#the-doctype

    In other words, the Pretty Links plugin is incorrectly writing <meta http-equiv="refresh" ... before <!doctype html>, and this stops LiteSpeed from being able to detect that it should cache it.

    Could you please assist with this modification?

    Many thanks!

    Thread Starter londonnut

    (@londonnut)

    Thanks for getting back to me, I’ve been and to resolve this now (hopefully permanently now) by upgrading my hosting to a plan with greater resources!

    thanks again for your assistance!

    Thread Starter londonnut

    (@londonnut)

    I’m having the same issues at the moment (cached pages are fine and quick but any prettylinks are very slow to resolve). (My back end is also slow FYI).

    I don’t think the plugin is getting de-activated as it does work, but just slow to resolve links as though they’re not cached and a database lookup is needed each time…any idea if the fault could lie with Cloudflare or Litespeed. Or if you have any other suggestions please let me know.

    londonnut

    (@londonnut)

    +1 This would be so useful!

    If there was a way to add this to the Litespeed WordPress plugin where you could choose to ‘Manually cache this page’ from the toolbar, that would be amazing.

    Thread Starter londonnut

    (@londonnut)

    Thank you for the information, useful to know!

    The speed is a lot better today so it looks like the issue has been resolved. (The website is StarFreebies.co.uk)
    I’m not sure what was causing the issues before, I ended up having quite a few critical PHP errors and the site crashed with critical errors. It was resolved by resetting PHP versions. I wasn’t able to get to the bottom of the cause just yet.
    It could just have been issues around Litespeed cache?

    The only pretty links error I noticed quite a few times was this one:

    Cron reschedule event error for hook: prli_cleanup_visitor_locks_worker, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”prli_cleanup_visitor_locks_interval”,”args”:[],”interval”:3600}

    Thanks again for getting back to me!

    Thread Starter londonnut

    (@londonnut)

    Update: Huarray, I’ve managed to get it working!
    The issue was a conflict with OneSignal manual integration. – I was previously initiating the OneSignal Javascript manually (due to custom usage). If I stop doing this – i.e. comment out the code below, then this plugin works.

    <script src="https://cdn.onesignal.com/sdks/OneSignalSDK.js" async=""></script>

    The plugin does not conflict with the OneSignal plugin but only manual implementation of OneSignal.

    Thanks!

    Thread Starter londonnut

    (@londonnut)

    I’ve still not been able to get this working. Would love to be able to use this plugin. Any help would be much appreciated!

    Thread Starter londonnut

    (@londonnut)

    I’ve cleared all the caches but unfortunately still have the same problem.
    I do not get the add to home banner appearing. Also the ‘Add To Home On Element Click’ (which is the main functionality that I want to get from this plugin) doesn’t work for me.

    Lighthouse gives the error messages:
    Web app manifest or service worker do not meet the installability requirements – No matching service worker detected
    Does not register a service worker that controls page and start_url

    Thanks

    Thread Starter londonnut

    (@londonnut)

    Thank you @magazine3 for raising and resolving issue #663 – the latest update (v1.7.40) has resolved the error message regarding the ‘unexpected if’.

    Unfortunately, I still cannot get this plugin working on my site. – I do not get the add to home banner appearing. Also the ‘Add To Home On Element Click’ (which is the main functionality that I want to get from this plugin) doesn’t work for me.

    Lighthouse doesn’t give me too much to work with…I get the error messages:
    Web app manifest or service worker do not meet the installability requirements
    Does not register a service worker that controls page and start_url

    I appreciate your help!

    Thread Starter londonnut

    (@londonnut)

    I noticed there’s an ‘unexpected if’ in admin-ajax.php

    The line which starts if(closedTime):

    var closedTime = PWAforwpreadCookie("pwaforwp_prompt_close") if(closedTime){ var today = new Date(); ....

    Is this due to a missing semi-colon; just before the if statement?

Viewing 10 replies - 1 through 10 (of 10 total)