suvie
Forum Replies Created
-
Ahh, yet another plugin. I feel like I’m drowning in them :’D Thank you so much for your help though! I recognise it might cause some issues that would need to keep an eye on!
Forum: Fixing WordPress
In reply to: Wp-content missing after moving from subdomain to rootI actually got some friends of friends to look at it and I don’t know what they did but it’s now back to normal.
Shame though, as normally you would like to be able to post a solution here so that others could follow it if they ended up in the same mess :/
- This reply was modified 4 years, 3 months ago by suvie.
Forum: Fixing WordPress
In reply to: Wp-content missing after moving from subdomain to rootOkay so I have replaced all of the old subdomain with the new, but it did not help, in fact it made it worse.
I think I will have to undo all changes. Luckily I can restore the db and I have not deleted files from the old domain yet, so that might be easier to reverse. Will see.
I guess I will just have to try this later in a different way.
Obviously if you have any good suggestions, please do let me know.
Forum: Fixing WordPress
In reply to: Wp-content missing after moving from subdomain to rootHello abletec,
Thanks so much for your help! So the index.php file currently only has this:
<?php /** * Front to the WordPress application. This file doesn't do anything, but loads * wp-blog-header.php which does and tells WordPress to load the theme. * * @package WordPress */ /** * Tells WordPress to load the WordPress theme and output it. * * @var bool */ define( 'WP_USE_THEMES', true ); /** Loads the WordPress Environment and Template */ require __DIR__ . '/wp-blog-header.php';
I tried changing that to
require __DIR__ . ‘https://thecontrastclub.com’;
but that just kills the whole external site. Admin is still fine.The htaccess file is in the root as it should (i.e. the /www/ folder) and I think the base is correct, this is the end of the file:
# 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 RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress
I know the url’s are a bit of a mess, I have not had a chance to change them yet, and now I can’t really access anything. For example the account page is part of Woocommerce and I can’t see the plugins or extensions at all on the admin side, it is like it’s just a skeleton of the real site.
Do you think I need to do the replacement in the DB then? That does sounds like an awful end result of this “easy move” :’D I did take a backup already of the site before starting any of this luckily.