Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter titianus

    (@titianus)

    It’s solved now. For everyone who might have the same problem:

    We moved our website to another server. After testing the exact installation of WordPress local the error doesn’t come up. So I guess it was a server-configuration mistake. Another WP Website on the same server had the same problems with some pages.

    Thread Starter titianus

    (@titianus)

    Hello Tara,

    Most likely this is a server permissions/ownership issue, so ask your host what’s going on

    I recently checked which files and directories have which permissions. As far as I remember wp-admin, -include and -content has got 755, the normal files in the root do have 644. It didn’t changed since it worked nicely two or three weeks ago.

    check your .htaccess files for anything strange.

    In the htaccess file everything was normal. I even created a new one by deleting the old and resaving the permalinks.

    make sure your server settings are not overriding the .htaccess file

    If the server would overwrite the htaccess, would I notice it? Would it change the content in the htaccess or would it be a server-htaccess file I don’t even see?

    try a full Manual Upgrade, to make sure all the WordPress files are there and correct..

    This would be the last option I guess. I’m not used in making a backup and restore it – especially cause the site is live and if I break something I may damage our agency. Shall I delete every file and directory except the wp-content?

    The thing is I didn’t found any threads that describe our problem. Mostly the wp-admin gets a loop. But our problem is only at our two pages /work/ and /agb/ and the 403 at the front page.

    Today I tried to delet all the plugins again. Every plugin is at the newest version – but nothing helped. So I guess it’s server-side or something with the core.
    Furthermore I activated wp_debug to see if I can get something out of this. Beside some register_sidebar warnings I got this message (I translated it to English):

    More information: Debugging in WordPress (en) (This message was added in version 4.2.0.) in /var/www/virtual/domain.com/htdocs/wp-includes/functions.php on line 3792 Notice: The used construct-method for WP_Widget is deprecated since version 4.3.0! Use
    __construct() instead

    Is it relative to the theme? We’re using Salient with a child theme. The parent theme is stuck on version 5.0 (http://themenectar.com/changelogs/salient.html). Could it be possible that this cause the error?

    Maybe we shall contact the provider again or the person who built our website.

    Best regards

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