Stephan Kockmann

Works fine again. Just a comment: The uninstall script did not delete the entries, the plugin writes to the database. In my case this was fine, so after reinstalling the plugin, the individual header images appeared as before. But if I wanted to uninstall the plugin permanently it would be nice to have the optional possibility to delete all database entries of the plugin, too. Maybe you could provide this optional feature in the future?

• This reply was modified 1 year, 2 months ago by Stephan Kockmann.

I deleted the plugin via FTP. Are there any DB-entries remaining, which I should clean up?

Thank you for your quick reply. Just let me know, when you have a potential fix, so I can test it.

Thank you for your quick answer! I deactivated “Permissions Policy” for now. I don’t dare to edit the wp-config.php at the moment. So I will wait for the next update, which hopefully will make the error message disappear. ??

Moin Finn!

Ich schicke dir die Infos per E-Mail an die in deinem Website-Impressum genannte E-Mail-Adresse. Hoffentlich helfen dir die Infos weiter.

Viele Grü?e,
Stephan

Sieht gut aus, Finn! Scheint alles wieder zu funktionieren, wie es soll. Danke!

Moin und danke für den Zwischenbericht, Finn! Gutes Gelingen und ich freue mich auf die Version 1.3.8!

Sehe gerade: Es gibt jetzt Version 1.3.7, da ist die fehlende Datei enthalten und der fatale Fehler tritt nicht mehr auf. Allerdings liefert mir das Widget jetzt keine Inhalte mehr, obwohl Statify genügend Daten liefern sollte.

Das Problem scheint aktuell auch auf dem Blog des Entwicklers zu bestehen. Wir sind also nicht allein und werden hoffentlich bald noch eine neue Version bekommen, die dann wieder wie gewohnt fehlerfrei funktioniert. Ich drücke die Daumen und lasse das Plugin bis zum n?chsten Update deaktiviert.

• This reply was modified 1 year, 10 months ago by Stephan Kockmann.

Das Problem kann ich best?tigen. Auch ich musste das Plugin wegen des Fehlers deaktivieren. – Kann es sein, dass beim Update eine Datei vergessen wurde? In Zeile 12 wird ja eine Datei eingebunden, die im Plugin-Verzeichnis nicht vorhanden ist.

Unfortanetly there still seems to be a problem with v1.0.8 – as @pat5d above said.

At the first look everything seems to be fine. But if you look at the HTML-Code of the page, there is some code inserted after the closing html-tag at the end. The footer is replaced, but the code at the end of the page looks like this:

</html>
		Stolz pr?sentiert von WordPress	</a>

or this:

</html>
		Powered by WordPress	</a>

With v1.0.6 everything works fine.

Unfortanetly there still seems to be a problem with v1.0.8. At the first look everything seems to be fine. But if you look at the HTML-Code of the page, there is some code inserted after the closing html-tag at the end. The footer is replaced, but the code at the end of the page looks like this:

</html>
		Stolz pr?sentiert von WordPress	</a>

or this:

</html>
		Powered by WordPress	</a>

With v1.0.6 everything works fine.

Unfortanetly there still seems to be a problem with v1.0.8. At the first look everything seems to be fine. But if you look at the HTML-Code of the page, there is some code inserted after the closing html-tag at the end. The footer is replaced, but the code at the end of the page looks like this:

</html>
		Stolz pr?sentiert von WordPress	</a>

or this:

</html>
		Powered by WordPress	</a>

With v1.0.6 everything works fine.

I have to correct myself: Unfortanetly there still seems to be a problem with v1.0.8. At the first look everything seems to be fine. But if you look at the HTML-Code of the page, there is some code inserted after the closing html-tag at the end. The footer is replaced, but the code at the end of the page looks like this:

</html>
		Stolz pr?sentiert von WordPress	</a>

or this:

</html>
		Powered by WordPress	</a>

With v1.0.6 everything works fine.

• This reply was modified 3 years, 4 months ago by Stephan Kockmann.

v1.0.8 works fine. Thank you. Important: Everyone who used v1.0.7 and had problems replacing the footer shoud clean up the code to replace (remove the backslashes) or start with a fresh code to replace. Otherwise it will not work as expected.

v1.0.8 works fine. Thank you. Important: Everyone who used v1.0.7 and had problems replacing the footer shoud clean up the code to replace (remove the backslashes) or start with a fresh code to replace. Otherwise it will not work as expected.