Support » Plugin: LiteSpeed Cache » Does not work when WP installed in subfolder / subdirectory

Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    in v3.x , there is option to set .htaccess path , have you tried that ?

    https://i.imgur.com/yfYEgre.png

    Best regards,

    • This reply was modified 1 year, 10 months ago by qtwrk.
    • This reply was modified 1 year, 10 months ago by qtwrk.
    Thread Starter mazunga

    (@mazunga)

    No, I have not. I will investigate and report back.

    Thread Starter mazunga

    (@mazunga)

    I received a copy of your unedited post, qtwrk, in which you showed a variety of scenarios:

    https://imgur.com/a/g4uJvzZ

    But it looks like you have not quite understood, because in each case you have the backend and frontends in the same folder.

    What typically happens is that there will be one htaccess in the wordpress subfolder, and another one in the root folder (public_html)

    So:
    home/example/public_html/.htaccess
    home/example/public_html/wordpress/.htaccess

    The error, which is still occurring with the latest release of your plugin, is that it only updates the htaccess in the wordpress folder. It cannot work out, by itself, to update the root htaccess.

    • This reply was modified 1 year, 10 months ago by mazunga.
    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Yes, I misunderstand in the first place, then I edit the my post

    home/example/public_html/.htaccess
    home/example/public_html/wordpress/.htaccess

    this set up still not working ?

    Best regards,

    Thread Starter mazunga

    (@mazunga)

    I will test and update, thank you.

    Plugin Support qtwrk

    (@qtwrk)

    I mean

    for example your set up is :

    / empty , only .htaccess to redirect/rewrite to /wordpress/ , where all the WP files are stored

    then set frontend .htaccess to /.htaccess, and backend .htaccess to /wordpress/.htaccess

    and see how it goes.

    Thread Starter mazunga

    (@mazunga)

    When I try to save the new paths I get error

    403
    Forbidden
    Access to this resource on the server is denied!

    Plugin Support qtwrk

    (@qtwrk)

    check mod_security , probably denied request due to sensitive word like .htaccess in it

    Thread Starter mazunga

    (@mazunga)

    Disabled ModSecurity, but I still get 403 error.

    Could this be the reason:
    https://coolestguidesontheplanet.com/403-forbidden-error-wordpress-htaccess/

    Plugin Support qtwrk

    (@qtwrk)

    I don’t know your server set up , but you could try that , though I think that is not the reason.

    you may need to check server log for that 403

    Thread Starter mazunga

    (@mazunga)

    I do not have access to the server’s log. I will have to ask the host.

    I was able to edit the .htaccess file from the “Tools” tab to insert “Options +FollowSymLinks” at the top, and successfully saved it. However, when I tried to edit the path again, the 403 error happened again.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    server log should tell the reason for 403 , please contact your hosting provider

    Best regards,

    Thread Starter mazunga

    (@mazunga)

    Without seeing the log (host away, weekend), I was looking at this page
    https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:understanding_403

    It mentions that the presence of a rewriterule can cause a 403. I do have such a rule:

    
    ### marker CACHE RESOURCE start ###
    RewriteRule cms/wp-content/.*/[^/]*(responsive|css|js|dynamic|loader|fonts)\.php - [E=cache-control:max-age=3600]
    ### marker CACHE RESOURCE end ###
    Plugin Support qtwrk

    (@qtwrk)

    not exactly , in that example

    RewriteCond (SOMECONDITION)
    RewriteRule ^(.*)$ – [F,L]

    that [F] stands for forbid , so gives 403 , but you don’t have F flag in your rule.

    Thread Starter mazunga

    (@mazunga)

    I see that now. I will have to ask the host for help

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Does not work when WP installed in subfolder / subdirectory’ is closed to new replies.