• I setup a simple WP site for a friend back in March / April..

    She noticed that over the summer – prob August the site was down – and just came up with a blank page with top left hand corner ACCESS DENIED

    I logged in to 1and1 and cant figure it out – I spoke to them and they advised that something had updated and corrupted it – im assuming it was a WP update, she said possibly a bug

    so ive been looking in etc WP forums – loads of people have had the same problem at some point – ive dont want is advices – ie downloaded the latest wordpress and replaced all the files in the FTP apart from the ‘content’, and the config.php – which seems to have worked for others – but it didnt help? im thinking it could be permissions, it wont let me duplicate the folders from the FTp (using fectch) it copes so far then comes up with permission errors – so I clicked on the main folder and put read / write for all permissions, now i just get the default 1&1 ‘this url has been bought holding page.. GRRR could it be the path?

    can anyone help – but please note – a lot of the help pages within this site i really dont understand, at all, its all like another language to me

    please can someone help??

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    What is the error you see?

    Errors like this are logged. Check the error log on your server. If you can’t find the log, please contact your host.

    Meantime, enable wp_debug and wp_debug_log and after an error, look at wp-content/debug.log to see if anything gets logged there. https://codex.wordpress.org/Debugging_in_WordPress

    Looks like you or the owner need to call 1 and 1 back and work with them to get this resolved.

    From what I can see the site isn’t even working at all right now… getting a ‘parked page’ instead.

    When you get it back you need to rename your plugins directory to see if a plugin caused the original problem then you can proceed from there to fix that issue or else start looking at a theme issue.

    If you have a good backup from before the problem started you might want to just restore that and go from there.

    Thread Starter wearegravity

    (@wearegravity)

    Problem is i think it was an automatic wordpress update that may have done it – so 1and1 are basically saying you need to do it yourself!

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

The topic ‘Warning: require_once’ is closed to new replies.