• Resolved Because Name Already Exists

    (@because-name-already-exists)


    After upgraded to version 5.3.9, now I cant access Site & Option tab on plugins page. The page continue loading animation without resolved

    However the others function is working well, and plugins status indicator all have Good result.

    When i check networks logs, it seems error 403 only on this wp json url:
    /wp-json/redirection/v1/setting/
    the rest is fine, eg;
    /wp-json/redirection/v1/
    not having problem

    not have problem.

    After plugins update I have clear cache and even i tried to re-save permalink, but have no luck.

    This is my htaccess, maybe there’s something that i missed:

    # 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 FAVICON start ###
    RewriteRule favicon\.ico$ - [E=cache-control:max-age=86400]
    ### marker FAVICON end ###
    
    ### marker WEBP start ###
    RewriteCond %{HTTP_ACCEPT} "image/webp"
    RewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
    RewriteCond %{HTTP_USER_AGENT} iPhone.*Version/(\d{2}).*Safari
    RewriteCond %1 >13
    RewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
    ### marker WEBP 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 A2592000
    ExpiresByType image/x-icon A2592000
    ExpiresByType image/vnd.microsoft.icon A2592000
    ExpiresByType image/svg+xml A2592000
    
    ExpiresByType image/jpg A2592000
    ExpiresByType image/jpeg A2592000
    ExpiresByType image/png A2592000
    ExpiresByType image/gif A2592000
    ExpiresByType image/webp A2592000
    
    ExpiresByType video/ogg A2592000
    ExpiresByType audio/ogg A2592000
    ExpiresByType video/mp4 A2592000
    ExpiresByType video/webm A2592000
    
    ExpiresByType text/css A2592000
    ExpiresByType text/javascript A2592000
    ExpiresByType application/javascript A2592000
    ExpiresByType application/x-javascript A2592000
    
    ExpiresByType application/x-font-ttf A2592000
    ExpiresByType application/x-font-woff A2592000
    ExpiresByType application/font-woff A2592000
    ExpiresByType application/font-woff2 A2592000
    ExpiresByType application/vnd.ms-fontobject A2592000
    ExpiresByType font/ttf A2592000
    ExpiresByType font/otf A2592000
    ExpiresByType font/woff A2592000
    ExpiresByType font/woff2 A2592000
    
    </IfModule>
    ### marker BROWSER CACHE end ###
    
    ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
    # END NON_LSCACHE
    # BEGIN WordPress
    # Arahan (baris) antara "BEGIN WordPress" dan "END WordPress"
    # dihasilkan secara dinamis, dan hanya dapat dimodifikasi melalui filter WordPress.
    # Setiap perubahan pada arahan di antara penanda berikut akan ditimpa.
    <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
    # BEGIN LiteSpeed
    <IfModule Litespeed>
    SetEnv noabort 1
    </IfModule>
    # END LiteSpeed

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author John Godley

    (@johnny5)

    A 403 indicates your site is refusing the request. This isn’t something caused by the plugin and so you’ll need to look elsewhere on your site for reasons why this might happen. It could be a security plugin or something like that.

    i am also having 403 issue. i removed wordfence and securi plugins and i am still having the 403 issue. any other ideas of why this is happening? thanks!

    Plugin Author John Godley

    (@johnny5)

    Try clearing your caches too.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Unable To Access Option And Site’ is closed to new replies.