Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter talie02

    (@talie02)

    Thanks, cyrfer for your suggestions.

    Changing the primary domain/subdomain is definitely not an option.

    So it seems like individual WP installations for each subsite might be the way to go. There’s already one working, non-WP website sitting in a subdirectory of the top-level WP installation – what’s a few more…

    The main and subsites can then stay at the original URLs – even if the main website is no longer in WP. Though may need to set up some rules in the htaccess file. It will depend on how the other developers install the new website.

    And as none of the subsites allow user sign-ups, keeping a user logged in across multiple sites is not an issue.

    The only issue I can foresee is if the other developers have reused the same directory names as the existing subsites on the primary site! (I wouldn’t put it past them since – I’ve not been asked to provide any input to the new site and I don’t know how vigilant they are about checking *sorry, rant over*.)

    I have a local development copy of the setup to play with – although it will never be as good as the production server.

    Thread Starter talie02

    (@talie02)

    Hi @wfpeter

    In the wordfence-waf.php file, the only difference between your code and mine – the WFWAF_STORAGE_ENGINE line was not present in my file. I added the line but my website freaked out and showed a 500 error on the frontend. So I’ve removed the line again.

    Have just now sent the ‘Send Report by Email’.

    Thanks, Natalie.

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