Antipole

@jkhongusc – thank you for responding.
I have copies your lines straight out of your email and put them near the top and removed the earlier mg30 stuff at the bottom.
But still no effect – no redirection. I have checked that the .htaccess file has indeed been updated.
Any further help would be much appreciated – I am not competent in .htaccess language. I include below the updated file.
thanks

# BEGIN All In One WP Security
#AIOWPS_BLOCK_SPAMBOTS_START
<IfModule mod_rewrite.c>
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{HTTP_HOST} ^mg30\.antipole\.co\.uk$ [OR]
RewriteCond %{HTTP_HOST} ^www\.mg30\.antipole\.co\.uk$
RewriteRule ^.*$ &quot;http\:\/\/mg30\.org\.uk\/$1&quot; [R=301,L]
RewriteCond %{REQUEST_URI} ^(.*)?wp-comments-post\.php(.*)$
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule .* https://127.0.0.1 [L]
</IfModule>
#AIOWPS_BLOCK_SPAMBOTS_END
# END All In One WP Security

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
# RewriteRule  ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
# RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]

Thanks Marius

Tried simple-post-status-notifications but it did not work for me.

However, found Pending Submission Notifications and this worked as expected and meets my needs.

I am seeing the euro at line 343 and also frequent errors at line 406. Let’s hope it gets some attention.

PHP Warning: in_array() expects parameter 2 to be array, string given in [snip]/wp-content/plugins/bp-forum-notifier/includes/notifier.php on line 406

This issue seems to have been fixed in v2.0.0.

Thank you!

Hold on – it is working now – not sure why not before. I am in business!!

(And I do need the Fix Site URLs ticked, so my menus work.)

Thanks for your perseverance. I look forward to putting SitePush to work.

Re DB name – yes you are correct – same pre-fix in both databases.

Big progress – almost there!

I tried moving a fresh copy of the database from my live site to the test site, using WordPress Move’s migration assistant, which is how I got my test site working while SitePush has not been. Same problem.

So I then set up a completely fresh test site from scratch with just SitePush installed. That error went away and I got others that helped me sort out my SitePush config file, now:

wp_dir =
wp_content_dir = /wp-content

Whereupon, it started to work and I have been able to push my live site to my new test site… except that:
I have inserted into the wp-config.php file on my test site only:

// Need these to make this site work with SitePush
define( ‘WP_SITEURL’, ‘https://testsite.<domain>&#8217; );
define( ‘WP_HOME’, ‘https://testsite.<domain>&#8217; );

Having done that I can log in to the admin panel on my test site and everything seems to be there. In Settings>General the WordPress Address and Site Address are both set to the test site and greyed out (which seems correct).
But as soon as I visit the site itself, I end up back on the live site.

I have tried re-pushing the database and content with and without the Fix site URLs ticked. I think I do not need it ticked? – I want to see when I am on the test site.

So almost there – what am I still missing?

A further test: I removed just the [dev] section. The error message complained that Database dev in config for site Dev Site is not defined in database config file.

This proves that the file is being read OK and the stuff before that point is not causing the error.

The error message about not being able to be read the file must be generated after it has been read OK and in the subsequent processing.

I have done an experiment: I temporarily replaced the contents of my dbs config file with just the word “rubbish”. Upon SitePush options save, it complained about no databases defined, no live site defined and no dev site defined.

This proves that the dbs config file is being read OK and that the error message “DB config file present, but it cannot be read.” is erroronius. The file is being read OK but something else is causing the error message, which is the wrong message.

Could you please have a look at how this message might be triggered even when the file can be read OK?

My dbs confg file contains (with some details edited for security here):

; <?php die('Forbidden'); ?> -*- conf -*-
; Do not remove the above line, it is all that prevents this file from being downloaded

[all]
prefix = oo_

[live]
name = xxxxxxxxx
user = xxxxxxxxx
pw = ************

[dev]
name = yyyyyyyyy
user = yyyyyyyyy
pw = ************

I have now copies the file contents into a simple text app to check there are no extraneous characters and then copies that back into TexWrangler, in which I edit text files on my server and have copies that back and checked the date has been updated.

Still no luck. Ah well. Thanks very much for trying.

You ar not annoying me – just trying to help.

The permissions are correct. I deliberately changed the name of the database config file by appending a ‘2’ to it. The plugin then complained it could not find it. So it must be looking in the right place and able to access the containing folder. I put the proper name back and gave it permissions of 777 but no luck. Then I have the enclosing folder 777 as you suggest – no luck. I have now restored permissions a they should be.

I have been through the contents of the file and double-checked the settings, db name, pre-fix, user and password etc. by comparing with the wp-config.php file and cannot find anything amiss.

It would be good to discover what is going on here. But meanwhile I have got my test site copied over and working otherwise. So I am not stuck.

One host with different folders. My two sites are in sibling folders both within the folder
/home/<mydomain>/public_html

My live site is in
/home/<mydomain>/public_html/<site>

as shown in the original post. So I have set the two parameters without trailing / to
wp_dir=/home/<mydomain>/public_html/<site>
wp_dir_content=/home/<mydomain>/public_html/<site>/wp-content

I hope I have understood you right.

No difference in the error message.

thanks for your perseverance.

Thanks for responding. Please can you clarify further. The same configuration files are used by both live and push sites, I believe. So which site (live or test) should the wp_dir and wp_content_dir point to? It cannot be both.

On the live site I have the config paths set to
/home/<mydomain>/sitepush/<site>-sites-config.php
/home/<mydomain>/sitepush/<site>-dbs-config.php
and don’t see how the dbs one is wrong since the two files are in the same directory. In any event, before I got the path right it complained it could not find it. Now it says
DB config file present, but it cannot be read.

Any further help would be appreciated.

Thanks for your fixes – great.

You got a mention on the Attitude theme site.

Problem seems to have gone away.

Maybe a deactivation/reactivation did clear something.

thanks

I am getting this too. Pity it has not been dealt with.

[Jun 28, 09:53:10] bla=
[Jun 28, 09:53:10] bla=false
[Jun 28, 09:53:10] bla=false
[Jun 28, 09:53:10] bla=true
[Jun 28, 09:53:20] bla=