julescopeland

Hi Jonradio,

Thanks for your input (your reply came in whilst I was still typing my previous reply).

I now seem to have the logs coming in to wp-content, and there was a line regarding the apparently quite common ‘headers already sent’ issue, and I realised that I’d actually somehow missed off the '?>' from the end of the file (there weren’t any redundant newlines).

But after fixing that, nothing seems to have changed.

Thanks for the info re. root level urls. I haven’t read them in detail, but will it manage to deal with the old urls peppered around the internet that still have the /wordpress/ in them? Ideally it should 301 them and we can eventually retire them altogether.

Good idea – I’ll see if they do auto backups (I fear that they don’t though).

Can you expand on what you mean about the url & htaccess being messed up? I did try loading everything before putting the revised .htaccess file in place, but it was the same problem.

I’d love to be able to check the logs, and I have had the debug reporting switched on, but I can’t find the output anywhere… (I’m with 123-reg for hosting, and their systems don’t seem to have been updated since the late 90’s) – I don’t even know where to look. They do have a log system via CPanel, but it only shows requests and the error log file is empty.

I tried switching on the debug option where it supposedly saves the logs into wp-content somewhere, but I couldn’t see anything. I find WP exceedingly opaque when it comes to error reporting.

And thanks for your speedy reply!