Forum Replies Created

Viewing 15 replies - 16 through 30 (of 145 total)
  • Thanks @alraen
    This article also helped: https://fullsiteediting.com/lessons/how-to-remove-default-block-styles/

    I hadn’t used WP in 6 months. The amount of garbage they dump in, out of the box, into a page is outrageous. I’ve spent an hour just undoing all the unjust they’ve caused. However, I never know if it’s really needed down the road.

    Using Sage disables a bunch with remove theme support, but there’s still emojis, gutenberg block css, and now this crap with adding .wp-container-# and its inline styles all over the place. Everytime they update WP, it’s always for the worse.

    Thread Starter polyfade

    (@polyfade)

    Nevermind, it looks like it might be a plugin conflict

    Just wanted to note, having the same problem when updating from 5.8.x to 5.9

    Thread Starter polyfade

    (@polyfade)

    Nevermind, you have to prefix with wp-json.

    https://mysite.com/wp-json/menus/v1/menus/<<menu-slug>>

    Thread Starter polyfade

    (@polyfade)

    Thanks a bunch Victor. That fixed it.

    Thread Starter polyfade

    (@polyfade)

    Victor, Yes I have used the Classic Editor in the past.
    Even though I removed all events that were once created by the classic editor, the issue persists.

    Any way around that?

    Thread Starter polyfade

    (@polyfade)

    When I try to create a new event, I get the error.

    BTW, I deleted all of my pre-existing events and venues.

    I’m using Gutenberg instead of the classic editor, and have the checkbox ticked in the Events Calendar settings to “Enable the Gutenberg block editor interface for creating events”

    I disabled, “Enable WordPress Custom Fields on events in the classic editor.” However, I never used custom fields.

    Under Display tab settings, I am using the Default Events Template with Tribe Event styles. Although, I tried with Skeleton styles too.

    I have “Enable updated designs for all calendar views” enabled.

    If I revert back to classic and all classic-related settings, I don’t have the issue.

    Using WP 5.8 and The Events Calendar 5.8.1. Although, I discovered the issue in WP 5.7.2

    • This reply was modified 4 years, 9 months ago by polyfade.
    Thread Starter polyfade

    (@polyfade)

    Much appreciated @qtwrk. That seemed to work following the OLS docs.

    I see here, https://docs.litespeedtech.com/lscache/lscwp/cache/#browser-tab
    the Browser Cache Settings within the plugin are for full-page cache, not for browser caching static assets such as images.

    To quote the docs:

    While it handles dynamically-generated content well, it only handles dynamically-generated content. Static content such as images, video, or fonts is not included in any full-page cache.

    • This reply was modified 4 years, 9 months ago by polyfade.
    Thread Starter polyfade

    (@polyfade)

    Oh, just saw your response about Header being ignore too

    Thread Starter polyfade

    (@polyfade)

    @qtwrk
    This will be ignored too?

    <filesMatch ".(css|jpg|jpeg|png|gif|js|ico|webp)$">
    Header set Cache-Control max-age=31536000, public
    </filesMatch>
    Thread Starter polyfade

    (@polyfade)

    ### Rewrite Rules Added by CyberPanel Rewrite Rule Generator
    
    RewriteEngine On
    RewriteCond %{HTTPS}  !=on
    RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]
    
    ### End CyberPanel Generated Rules.
    
    ### Rewrite Rules Added by CyberPanel Rewrite Rule Generator
    
    RewriteEngine On
    RewriteCond %{HTTPS}  !=on
    RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]
    
    ### End CyberPanel Generated Rules.
    
    # BEGIN LSCACHE
    ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
    <IfModule LiteSpeed>
    RewriteEngine on
    CacheLookup on
    RewriteRule .* - [E=Cache-Control:no-autoflush]
    RewriteRule \.litespeed_conf\.dat - [F,L]
    
    ### marker CACHE RESOURCE start ###
    RewriteRule wp-content/.*/[^/]*(responsive|css|js|dynamic|loader|fonts)\.php - [E=cache-control:max-age=3600]
    ### marker CACHE RESOURCE end ###
    
    ### marker LOGIN COOKIE start ###
    RewriteRule .? - [E="Cache-Vary:,wp-postpass_8cb83f8ac912f90f466f97029503fc74"]
    ### marker LOGIN COOKIE end ###
    
    ### marker FAVICON start ###
    RewriteRule favicon\.ico$ - [E=cache-control:max-age=86400]
    ### marker FAVICON end ###
    
    ### marker DROPQS start ###
    CacheKeyModify -qs:fbclid
    CacheKeyModify -qs:gclid
    CacheKeyModify -qs:utm*
    CacheKeyModify -qs:_ga
    ### marker DROPQS end ###
    
    </IfModule>
    ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
    # END LSCACHE
    # BEGIN NON_LSCACHE
    ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
    ### marker BROWSER CACHE start ###
    <IfModule mod_expires.c>
    ExpiresActive on
    ExpiresByType application/pdf A31536000
    ExpiresByType image/x-icon A31536000
    ExpiresByType image/vnd.microsoft.icon A31536000
    ExpiresByType image/svg+xml A31536000
    
    ExpiresByType image/jpg A31536000
    ExpiresByType image/jpeg A31536000
    ExpiresByType image/png A31536000
    ExpiresByType image/gif A31536000
    ExpiresByType image/webp A31536000
    
    ExpiresByType video/ogg A31536000
    ExpiresByType audio/ogg A31536000
    ExpiresByType video/mp4 A31536000
    ExpiresByType video/webm A31536000
    
    ExpiresByType text/css A31536000
    ExpiresByType text/javascript A31536000
    ExpiresByType application/javascript A31536000
    ExpiresByType application/x-javascript A31536000
    
    ExpiresByType application/x-font-ttf A31536000
    ExpiresByType application/x-font-woff A31536000
    ExpiresByType application/font-woff A31536000
    ExpiresByType application/font-woff2 A31536000
    ExpiresByType application/vnd.ms-fontobject A31536000
    ExpiresByType font/ttf A31536000
    ExpiresByType font/otf A31536000
    ExpiresByType font/woff A31536000
    ExpiresByType font/woff2 A31536000
    
    </IfModule>
    ### marker BROWSER CACHE end ###
    
    ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
    # END NON_LSCACHE
    ### Rewrite Rules Added by CyberPanel Rewrite Rule Generator
    
    RewriteEngine On
    RewriteCond %{HTTPS}  !=on
    RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]
    
    ### End CyberPanel Generated Rules.
    
    cat: /home/spinlinedesign.com/public_html/.htaccess: No such file or directory
    
    # BEGIN WordPress
    # The directives (lines) between "BEGIN WordPress" and "END WordPress" are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress
    
    <filesMatch ".(css|jpg|jpeg|png|gif|js|ico|webp)$">
    Header set Cache-Control max-age=31536000, public
    </filesMatch>
    Thread Starter polyfade

    (@polyfade)

    Thanks for responding @qtwrk. There’s currently no custom headers set up under Virtual Hosts > Context. But, shouldn’t the server just “obey” what has been added to my htaccess file already? These rules are listed at the very end of the file, too. Why should I need to set them up again in the OpenLiteSpeed control panel when I’ve set them in the LiteSpeed plugin settings and manually added them to the htaccess file myself?
    Why should I have to be redundant 3 times? That seems a little crazy, but will try it anyway.

    Thread Starter polyfade

    (@polyfade)

    Do I need to change something in the OpenLiteSpeed panel? (https://mydomain.com:7080)

    This is a bit confusing when there is 3 different documentations for WP LiteSpeed Cache plugin, OpenLiteSpeed control panel and CyberPanel. I don’t know which to follow.

    Thread Starter polyfade

    (@polyfade)

    I think my issue has to do with my theme or plugin conflict because it works on a fresh WP install.

    However, what about the js/frontend-gtag.min.js 9.3 KiB script? This is still render-blocking. BTW, I’m not logged in and viewing as an Incognito session.

Viewing 15 replies - 16 through 30 (of 145 total)