Beiträge von rredd

    Was für ein unfassbarer Schwachsinn spielt sich mit WP eigentlich ab?
    Also: der Tipp mit der aktivierung von MD5 hat mich endlich wieder auf mein Dashboard zurückgebracht - Dank an b3317133
    Alle PlugIns und WP konnte ich wieder auf den neuesten Stand bringen - wundervoll!
    Danach habe ich mich ausgeloggt und kurze Zeit später wollte ich zurück, nur war WP wieder mal nicht zufrieden und zwar so unzufrieden, dass es mich nicht mehr auf mein Dashboard liess. Stattdessen kam WIEDERMAL eine Fehlermeldung und nicht die Möglichkeit sich als Admin einzuloggen. Wer denkt sich nur so eine Scheiße aus - sorry aber das kann man nicht mehr anders bezeichnen!
    Fehlermeldung:
    Warning: The magic method Gallery_Img::__wakeup() must have public visibility in /mnt/web104/d1/41/57686741/htdocs/WordPress_06/wp-content/plugins/gallery-images/gallery-images.php on line 97
    Und wie soll man eine Änderung gestalten. wenn man nicht ins Dashboard kommt?

    Die Mail kam von anderer Stelle. Generiert WP aber eine Mail zwecks Passwortrückstellung kommt dies zum tragen:
    Emailed passwords are not being received
    Description:
    When users try to register with your blog or change their passwords by entering their username and/or email, WordPress indicates that their password has been emailed to them, but it is never received.
    Reason and Solutions: WordPress uses the standard PHP mail() function, which uses sendmail. No account information is needed. This is not generally a problem if you are using a hosting service, but if you are using your own box and do not have an SMTP server, the mail will never send.

    Ich werde noch bis heute Abend warten (24Std. Frist) dann bekomme ich einen neuen Wiederherstellungslink und kann das Passwort ändern. Per FTP oder Neueintrag in der wp_user funzt das leider nicht.

    In diesem Text muss wohl die Lösung stecken und um die zu finden muss ich zunächst Informatik studieren...
    Danke für eure Hilfe.

    [size=18]Emailed passwords are not being received[/SIZE]
    Description: When users try to register with your blog or change their passwords by entering their username and/or email, WordPress indicates that their password has been emailed to them, but it is never received.

    Reason and Solutions: WordPress uses the standard PHP mail() function, which uses sendmail. No account information is needed. This is not generally a problem if you are using a hosting service, but if you are using your own box and do not have an SMTP server, the mail will never send. If you are using a *NIX box, you should have either postfix or sendmail on your machine; you will just need to set them up (search the Internet for how-to’s). If you do not want to go through setting up a complete mail server on your *NIX box you may find msmtp useful — it provides “A secure, effective and simple way of getting mail off a system to your mail hub”. On a Windows machine, try a sendmail emulator like Glob SendMail.

    More help can be found on this thread of the WordPress Support Forums: https://wordpress.org/support/topic.php?id=24981.

    Windows Host Server Specific: Check your “Relay” settings on the SMTP Virtual Server. Grant access to 127.0.0.1 . Then in your php.inifile, set the SMTP setting to the same IP address. Also set smtp_port to 25.

    Ensure Proper Return Address is Used: By default, the WordPress mailer fills in the From: field with wordpress@yourdomain.com and the From: name as WordPress.

    This is fine if this is a valid e-mail address. For example, if your real e-mail is wordpress@yourdomain.com, your host should pass the email on for delivery. It will probably send your mail as long as yourdomain.com is setup to send and receive mail, even if wordpress is not a valid mail box. But if you set you real email as the From: address and it’s something like wpgod@gmail.com, the mail may not send because gmail.com is not a domain handled by the mail server.

    Treated as Spam: Your email message may have been routed to a spam folder or even worse, simply discarded as malicious. There are a couple measures you can use to convince recipient’s mail servers that your message is legitimate and should be delivered as addressed.

    SPF: (Sender Policy Framework) This is the most common anti-spam measure used. If you are on a hosted system, there is a good chance your host has set this up for the mail server you are using. Have WordPress email you and check the message headers for evidence that the message passed the SPF check. You can get a message sent by following the Forgot Password link on the login page. To keep your old password, do not follow the link in the message.
    If your system email failed the SPF check, you can set up the credentials if you have access to your DNS records and your mail server’s domain belongs to you. Check the return path of the email your system sent. If the mail server listed there has your domain name, you can set up SPF credentials. There are several how-tos on the Internet.

    DKIM: (Domain Key Identified Mail) This system is also used. You can use both SPF and DKIM in the same message. Again, just as with SPF, you can check if your receiving mailserver verified your host’s domain key by examining the mail header. There is a fair chance no signature key was provided, indicating your host chose to not use this protocol. Also as with SPF, if you can edit your DNS records and the mail server belongs to your domain, you can set up DKIM credentials yourself. Some how-tos exist if you search the Internet.

    Du hattest recht, also nun tatsächlich auf Erstzustand gebracht.
    YAY Fehlermeldung ist weg...
    Umpf neuer Shit:
    "Es gab einen kritischen Fehler auf deiner Website. Bitte überprüfe den Posteingang deiner Website-Administrator-E-Mail-Adresse für weitere Anweisungen."
    Womit ich wieder am Anfang meines Problems stehe: ich bekomme keine Mails gesendet.

    Ja, per FTP. Auf der verlinkten Seite liest man folgendes:

    There is also an easy way to reset your password via FTP, if you’re using the admin user.

    1. Login to your site via FTP and download your active theme’s functions.php file.
    2. Edit the file and add this code to it, right at the beginning, after the first <?php


    wp_set_password( 'my_new_password', 1 );

    In the above code, replace the text my_new_password with your own new password for the main admin user. The number 1 above refers to the user ID number in the wp_users database table. Since we wanted the user ID of the main admin user, we just keep the number as 1, which is typically the user ID of the main admin user.

    1. Upload the modified file back to your site.
    2. Once you are able to login, make sure to go back and remove that code. It will reset your password on every page load until you do so.


    In lesbarer Form - na ja, so habe ich es bekommen und leider weiß ich nicht wie man das in eine lesbare Form bekommt - sorry.

    Vielen Dank für die Tipps. Spam-Ordner hatte ich natürlich schon gecheckt - leer.
    In den obigen Link habe ich reingeschaut und per FTP das Passwort geändert, was dann beim Erstversuch nicht funktionierte. Dann habe den Browsercach komplett geleert um die WP-Cookies loszuwerden. Danach bekam ich eine Meldung mit der ich als Laie leider nichts anfangen kann - vielleicht aber jemand von Euch(?).
    Dies ist die Fehlermeldung:
    Fatal error: Uncaught Error: Call to undefined function wp_set_password() in /mnt/web104/d1/41/57686741/htdocs/WordPress_06/wp-includes/functions.php:2 Stack trace: #0 /mnt/web104/d1/41/57686741/htdocs/WordPress_06/wp-settings.php(111): require() #1 /mnt/web104/d1/41/57686741/htdocs/WordPress_06/wp-config.php(89): require_once('/mnt/web104/d1/...') #2 /mnt/web104/d1/41/57686741/htdocs/WordPress_06/wp-load.php(37): require_once('/mnt/web104/d1/...') #3 /mnt/web104/d1/41/57686741/htdocs/WordPress_06/wp-blog-header.php(13): require_once('/mnt/web104/d1/...') #4 /mnt/web104/d1/41/57686741/htdocs/WordPress_06/index.php(17): require('/mnt/web104/d1/...') #5 {main} thrown in /mnt/web104/d1/41/57686741/htdocs/WordPress_06/wp-includes/functions.php on line 2