Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • There are many errors with that file. You can test CSS with a linter, an online tool can be found here https://csslint.net/.

    Ask the plugin author to use a linter on their CSS. It would pick up the issues instantly.

    I recommend https://stylelint.io/ but they can also use https://github.com/CSSLint/csslint.

    Tell them to incorporate it into their build process before releasing updates to prevent issues in future.

    Here are the 3 critical errors.

    line: 1198, column: 105
    Parsing Errors Expected RBRACE at line 1198, col 105.

    .tourmaster-tour-category-grid.tourmaster-with-thumbnail .tourmaster-tour-category-overlay{ opacity: 0; alpha(opacity=0);

    line: 1226, column: 107

    Parsing Errors Expected RBRACE at line 1226, col 107.

    .tourmaster-tour-category-grid-2.tourmaster-with-thumbnail .tourmaster-tour-category-overlay{ opacity: 0; alpha(opacity=0);

    line: 1253, column: 107
    Parsing Errors Expected RBRACE at line 1253, col 107.

    .tourmaster-tour-category-grid-3.tourmaster-with-thumbnail .tourmaster-tour-category-overlay{ opacity: 0; alpha(opacity=0);

    The issue is that alpha(opacity=0); is not valid CSS, it should be filter: alpha(opacity=0);.

    No problem.

    You could add the CSS file URL in question to the blacklist which won’t load that file async but will load all other CSS files async.

    I would be interested to see what the underlying issue is though. It’s could be important if the bug causes issues with many sites using litespeed-cache unbeknown to us.

    If you would like me to look deeper into the issue join the LiteSpeed Slack channel https://www.litespeedtech.com/slack and let me know your username and I’ll message you on there to get to the bottom of the problem.

    It’s blank because of the following CSS which sets the content to invisible.

    .et_pb_blog_grid .et_pb_salvattore_content[data-columns] .et_pb_post {
        opacity: 0;
    }

    found in https://cdn-5e63a9d9f911c80ca0fd76f4.closte.com/wp-content/litespeed/cssjs/06d49.css

    Disable minify + combine CSS and find the file that the above CSS is in.

    There’s either missing CSS that meant to set the opacity to 1 or something else causing the issue.

    It’s could be that the theme or plugin that generates the page tries to lazyload the articles which is broken so never sets the articles back to visible.

    You are using Windows, and that function is not implemented in PHP for windows. See https://www.php.net/manual/en/function.sys-getloadavg.php

    Is this a development or production environment?

    A lot of the time with plugin generated CSS issues they arise from configurable options, where there are empty inputs.

    Check to see if it’s not as simple as filling them empty input boxes with a valid colour value to resolve the errors.

    If this is an issue with the table plugin https://www.ultimatebeaver.com/modules/table, you should report it to the author, and they can then push a fix to resolve this for you and all the rest of their customers.

    The error message Failed to post via WordPress: Too many frequent errors happens when the CCSS fails to often, you are rate limited for a period of time to prevent your site from requesting CCSS again and again when it keeps failing.

    I can see that your site homepage CCSS is generated, which shows it’s working now after fixing the CSS error. You just had to wait a short period of time for your site to be allowed to send more CCSS requests to the API.

    ————

    Checking your page https://exclusiveweb.co.za/web-hosting/, I can see /*CssSyntaxError: /min/aa7bf.css:1:138747: Unknown word*/, again running https://exclusiveweb.co.za/min/aa7bf.css through a CSS linter picks up a lot of errors.

    I will list a few below:
    line: 4800

    .fl-node-5d1d91338fd14 .pp-pricing-table .pp-pricing-table-col.pp-pricing-table-highlight .pp-pricing-table-column .pp-pricing-featured-title {
        background-color: #ccc;
        color: #
    }

    line: 4838

    .fl-node-5d1d91338fd14 .pp-pricing-table .pp-pricing-table-column .pp-pricing-table-duration {
        font-size: 12px;
        color: #
    }

    line: 4845

    .fl-node-5d1d91338fd14 .pp-pricing-table .pp-pricing-table-column .pp-pricing-table-features {
        font-family: "Raleway", sans-serif;
        font-weight: 400;
        font-size: 14px;
        color: #;
        text-transform: none;
        text-align: center;
        min-height: 0px
    }

    There’s many more if you search that file for color: #; you will find around 182 errors.

    You can use https://wp.api.litespeedtech.com/ips for the list of IPs used.

    Quickly passing your CSS file https://exclusiveweb.co.za/min/8c000.css through a CSS linter reveals you have an error on line 6752.

    @media only screen and (max-width:768px) {
        .fl-builder-content .fl-module-content-slider .fl-slide-0 {
            background-color: #fc44444 !important
        }
    }

    The error is with the background-color code #fc44444, which is not valid. HEX should be six, and not seven characters in length.

    If you fix that error and purge CCSS then process CCSS again, it should work.

    How many plugins do you have installed?

    TTFB it very slow, you need to investigate what’s causing the delay. Are you able to install https://en-gb.www.ads-software.com/plugins/query-monitor/ and share the results? Please hide any information that may be private.

    You also have 154 requests, it’s best to combine CSS and JS files. I can see one of your JS files is 464.9KB, that’s pretty large. You must have a lot of plugins bloating your page.

    To really optimise your site, you might have to move away from WordPress.com.

    WordPress.com or WordPress VIP?

    Because they are hosting you, you are limited on the plugins you can install and access to the hosting platform.

    Your site should already be statically cached via your hosting provider.

    What caching features are you looking to use?

    What type of hosting are you using?

    Not via WordPress plugin, but the control panel supplied by your hosting provider.

    Are you using cPanel or any other control panel?

    1. It looks like you have another caching or optimisation plugin installed and enabled.
    2. You need to add write access to the .htaccess via permissions on your control panel file manager or by manually adding the contents of the text area to your .htaccess.
    3. The main caching features requires you to use a web host that uses LiteSpeed server.

    This issue has been reported by one of our customers too. I’ll provide you with some technical information regarding my findings.

    The site uses WooCommerce, and on page load a query parameter is added to the URL, for example, visiting domain.tld/ this redirects to domain.tld/?v=79cba1185463. This hash is linked to users IP because I’ve tested this on multiple devices and it stays the same.

    My investigation found that this is due to the WooCommerce Geolocate feature located at WooCommerce -> Settings -> General -> Default Customer Location which is currently set to Geolocate (with page caching support). I disabled this because our customer doesn’t require this feature.

    The only place I’ve seen LiteSpeed talk about this features is in the comments on this page https://blog.litespeedtech.com/2017/05/31/wpw-fixing-lscachewoocommerce-conflicts/. I’m not sure if the normal Geolocate setting uses cookies instead of a hash in the URL, then the cache vary would be possible.

    We’ve also seen this happen recently.

    You can see that the check is not following the redirect “301 Moved Permanently”.

    This hash error happens when the user changes the WordPress installation URL from HTTP to HTTPS and adds an HTTPS redirect in the .htaccess.

    rewriteCond %{HTTPS} !on
    rewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]

    The Reset IAPI Key request is not working for this issue.

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