lines of codes prevent access to dashboard

Try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

If that does not resolve the issue, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue (theme functions can interfere like plugins).

hi, thanks.
I deactivate the plugins via phpMyAdmin but no major changes occurred (except the lay out of the blog du to missing plug in).

I also changed the name of the active theme. But then the all blog was gone and only the lines of codes were remaining. I loged in but as before no dashboard, only code.

Others ideas of what I can do?

Manually install a copy of Twenty Fifteen via FTP https://www.ads-software.com/themes/twentyfifteen/ and try the theme reset again (renaming the directory of your currently active theme), then never delete the default theme again. ??

the default theme has not been deleted.
if the theme reset works with Twenty Fifteen, will I be able to use again my previous theme?

At the moment, this is just to determine if your theme was the cause. If it is, it can probably be fixed.

Does your site work under Twenty Fifteen?

Turn off display_errors in your PHP.INI file.

i’ve uploaded Twenty Fifteen and renamed the active theme as well as the 3 others that were in the theme folder. But no the site is not working.
https://www.soizicstokvis.net/

@macmanx : That site is running WordPress 2.7. Basic debugging with Twenty Fifteen is unlikely to work. ??

@amlie:

Step 1: Make a backup of everything. Everything. Database, files, the lot.

Step 2: Attempt to update the site to a more modern version of WordPress. Fortunately, WordPress is very backwards compatible, so you should be able to manually upgrade it to 4.3 with no issues. Just follow the manual upgrade instructions.

Step 3: Now you can debug the problems with it. Trying modern solutions on a piece of software released 7 years ago is likely to lead you to frustration.

The long and the short of it is that you’re not going to “fix” it as much as you are going to “rebuild it from scratch”. The database will likely work fine, WordPress will update it for you and keep the content. But the theme, the plugins, the site look as a whole, that’s probably all going to disappear in the rebuilding process.

where I can find this PHP.INI file? I looked but did not find it.

ok, thanks!

Forget the PHP.INI file. I noticed that you’re running 2.7 afterwards. Go back up a couple of posts and read that instead.

Upgrade was since months on my to-do list, now is the time!

Thanks for catching that, Otto!

Hi,
Backup is done. I have understood that I need to do a manuel upgrade (replacing wp files).
I can not update directly to 4.3, do I?
From 2.7 I have to update 2.9, then 3.1 etc?
Thanks
a

That is correct, you’ll need to follow this plan: https://codex.www.ads-software.com/Upgrading_WordPress_Extended#Upgrading_Across_Multiple_Versions