SG Optimizer – not working for site with WP files in sub folder

  • Resolved n1ck0

    (@n1ck0)


    4 years, 3 months ago

    Hello,

    We have recently migrated a WordPress website to SiteGround and were hoping to use their SG Optimizer plugin as it sounds promising.

    Our WordPress files are located in a sub folder (wp) with:
    * WordPress Address (URL) – https://domain.com/wp
    * Site Address (URL) – https://domain.com/

    We were unable to turn on / toggle any of the settings in the plugin and contacted Site Ground support. They looked into it but advised due to the custom setup (eg WordPress in a sub folder), SG Optimizer would not work. I find this surprising given pretty well every plugin I have ever used over the years works with WordPress files in sub folders and Site Ground are renowned as WordPress experts.

    Just wondering if anyone has managed to get SG Optimizer working when the WordPress files are located in a sub folder? If so, how did you do it?

    Thanks.

    • This topic was modified 4 years, 3 months ago by n1ck0.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Stanimir Stoyanov

    (@sstoqnov)

    SiteGround Representative

    Hey @n1ck0

    Our plugin works with sites with a custom WP folder.

    Would it be possible to provide your site URL, and we will check the issue?

    Regards,
    Stanimir

    Thread Starter n1ck0

    (@n1ck0)

    Hi Stanimir,

    Thanks so much for getting back to me and for the positive news.

    Three support staff at Site Ground think otherwise – they all told me SG Optimizer wouldn’t work with WordPress in sub folder so you’d best let them know :). In one instance I gave backend WP access and two suport staff still couldn’t get it working for us.

    Anyway, yesterday afternoon I had a little break through after I found a discrepancy in General > Settings due to another issue: the backend WordPress Address (URL) was non www and the frontend Site Address (URL) was www. This was changed during migration using the Site Ground migrator plugin. Once I picked up on this discrepancy and made both www, I reinstalled the SG Optimizer plugin and it started working. So that’s great news :).

    Not all settings in SG Optimizer are setup for working in a WordPress sub folder install though because it pre-populates / hard codes the sub folder address from the backend WordPress Address (URL) (eg https://www.domain.com/wp) rather than the frontend Site Address (URL) (eg https://www.domain.com/). The pre-populated / hard coded backend WordPress Address (URL) is greyed out and cannot be changed. The frontend website on the Site Address (URL) is what we want to cache so hard coding the backend WordPress Address (URL) makes no sense for a sub folder setup.

    This affects these 3 x SG Optimizer options for:
    * Supercacher Settings > Excluding URLs (so we’re unable to exclude front end urls)
    * Supercacher Settings > Test URLs for Cache Status (so we’re unable to test front end urls)
    * Speed Test > Score Test (so we’re unable to speed test front end pages)

    Would love to see these 3 items resolved in an update – then a sub folder setup will work flawlessly in the SG Optimizer plugin.

    Thank you kindly and keep up the great work.

    • This reply was modified 4 years, 3 months ago by n1ck0.
    Plugin Author Stanimir Stoyanov

    (@sstoqnov)

    SiteGround Representative

    Hey @n1ck0

    Would it be possible to provide your ticket IDs?

    We will check your case, once we know your site URL.

    Regards,
    Stanimir

    Plugin Author Stanimir Stoyanov

    (@sstoqnov)

    SiteGround Representative

    Hey @n1ck0

    I’ve tested the plugin and it works with custom wp dir.

    We use siteurl for the settings you have mentioned, not the home_url.

    I’m marking this as resolved because, without your site URL, we are unable to reproduce the issue.

    Feel free to reopen the ticket if you need further assistance.

    Regards,
    Stanimir

    Thread Starter n1ck0

    (@n1ck0)

    Hi Stanimir,

    You’re a bit eager to close this, it is not resolved for those 3 settings as reported.

    Would it be possible to provide your ticket IDs?

    Sure…
    Here is a chat ID related to one enquiry: Chat 6709122.
    Here is the follow up advanced email tech support: Ticket 3865496.
    These 2 support contacts were prior to finding there was a www and a non www in the WordPress URLs as reported above (which your team didn’t pick up on).

    I’ve tested the plugin and it works with custom wp dir.

    Yes, I confirmed that in this thread.
    What isn’t working for us are those 3 settings as reported because the backend address with /wp in the url is pre-populated / hardcoded.

    Screencaps below…

    WordPress General Settings:

    View post on imgur.com

    SG Optimizer showing the pre-populated wp in the url so we can;t use those settings:

    View post on imgur.com

    How do we get rid of the pre-populated wp in the url for those 3 settings?

    Thanks.

    Thread Starter n1ck0

    (@n1ck0)

    Confirming for other interested WordPress users.

    Still no luck with those 4 (including Cloudflare tab) pre populated fields in SG Optimizer.

    The terminology SiteGround is using is different to WordPress in the Settings > General section…
    * SiteGround is referencing “siteurl” as what WordPress calls WordPress Address (URL) – which is the backend
    * SiteGround is referencing “home URL” as what WordPress calls Site Address (URL) – which is the frontend
    This is a bit confusing, to me anyway.

    Regardless, if SiteGround uses their “siteurl” / WordPress’s backend “WordPress Address (URL)” for those prepopulated 4 x fields, it’s always going to output “wp” (or whatever the sub folder is called) in a sub folder setup.

    So to me I don’t think you can say at this point in time with version SG Optimizer 5.7.12 that it fully supports a sub folder setup. Shame.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘SG Optimizer – not working for site with WP files in sub folder’ is closed to new replies.