Paul

For what its worth I just imported a .htaccess file using this plugin as I am transferring everything over to WordPress from a static html site.

To be on the safe side I removed every other line of code from the file that wasnt anything to do with redirects before uploading it.

The only redirect lines I left in it were like the following:

Redirect 301 /DirectoryName/index.html https://www.MySite.com/SomeURL.html

There were two hundred redirects in the file I imported and all work perfectly now, so you should be able to do the same with all your types of redirects.

Ha! Well I’ll be damned! You fixed it Jason!

I never thought it would be that easy to fix this longstanding problem with my WordPress, so I was preparing to study several different “WP_ALTERNATE_CRON” articles that looked very complicated, but as an afterthought I did add define (‘ALTERNATE_WP_CRON’, true); to my wp-config.php file as you suggested.

I set a time to run the scheduled backup and carried on looking around some other sites and forgot about it. When I returned to my blog to check on it I noticed the following code appended to the end of all my URL’s:

?doing_wp_cron=1363271049.9576210975646972656250

I thought this must be another error, but when I checked on the online backup I could see that “A backup is currently running”

The only thing I had to do was go to my online backup settings and logout and then login again as you had suggested in some other support threads, and it resulted in this working perfectly. Everything is great again now and my automatic backups are transmitted to the server just as they were a very long time ago.

I think a lot of others will benefit from reading your post.
This is one thread that’s well and truly resolved!

Thank you!

Regards,
Paul.

Hi Jason.
Thanks for that explanation, it really did provide some interesting reading, and yes I did read it.
(Although I had to Google TLDR to find out it meant too long, didn’t read!)
I will read up on some the guides you mentioned as I think it might be something I will need to do, as even though I do get traffic to the blog throughout the month, the scheduled backup always has a status reading of “Due to start any minute” and never actually does start (even if months go by).
I also think others will benefit from seeing this detailed post, and I am glad you provided such detail.
Regards,
Paul.

That was actually pretty amazing how quickly you got that next update working. I am pleased to let everyone that is using 123-reg as their hosts know that this plugin now works perfectly, and I will be posting the same on my blog as I know that there will be many people out there looking for a way to backup their wordpress blogs.

Thanks,
Paul.

My manual download backups are fine, but the following error was returned after attempting a manual online backup.

“An online request failed: The server responded with status code 500 and error code 4103: The blog URL of your WordPress installation does not appear to be valid. Please note that this plugin will only work on public websites, and not within an intranet or home network. If you believe your blog URL is correct, please contact support.”

This is probably due to the wordpress installation being in its own directory, rather than the root, and because of the way that 123-reg (my host) has the setup of wordpress installations from their free 123 apps so that they end up like “WHATEVER.com:/BLOG” rather than “WHATEVER.com/BLOG” if you are doing an installation in a directory instead of the root.

Does anyone know what can be done about this, or is the answer to find another plugin (or possibly go for an earlier version of the same plugin)?

Thanks,
Paul.