Bernhard Kau

With version 1.6.0 it should work again with Gutenberg (tested in WordPress 5.9).

Hi @kbbkk,

it used to work with Gutenberg as well. I haven’t checked it with the latest version of WordPress/Gutenberg, but I will do Sunday evening.

I can confirm the error. In PHP 7.3+ a trailing comma in a function call is valid, in PHP versions below that it will throw a syntax error.

As the plugin states that it works with PHP 5.2 and higher, I had the issue that on a site with PHP 7.2 only it got updated but then broke the site.

Hi @appgom,

we just released version 2.0.0 a week ago introducing a new feature to bulk download attachments from multiple entries using the bulk action. For this new version we had to rewrite the functions that would create the zip files. This might cause the issue for you.

Would it be possible for you to explain a bit more, how your firm looks like. Or maybe even provide an export of the form (just the definition, not the entries), so we can try to find the issue?

Bernhard

Hello Roberto,

we have just released a new version of the plugin. This handles an issue when upload fields where not used causing the ZIP file to be broken. Maybe this will also solve your issue.

Hallo Bernd,

es scheint nun zu funktionieren!

65 von 67 Beitr?gen und Seiten wurden erfolgreich migriert

Leider k?nnen die anderen beiden nicht migriert werden. Wie kann ich das am besten manuell tun bzw. wie kann ich rausfinden, woran es liegt?

Hallo Bernd,

kein Problem und vielen Dank schon einmal für die erste schnelle Rückmeldung.

Vermutlich muss in Zeile 128 das $this mit wp_worthy::singleton () ersetzt werden. Aber ich wei? nicht, ob noch mehr fehlt.

Da ich gerade Urlaub habe und daher Zeit, die Migration zu machen eilt es bei mir nicht.

Noch ein Hinweis: Die Seite l?uft unter PHP 7.4.16

Hallo Bernd,

ich hatte gesehen, dass erst kurz zuvor ein Update ver?ffentlicht wurde.

Der beschriebene Fehler ist nun behoben, starte ich allerdings den Import, kommt nun dieser Fehler :/

Fatal error: Uncaught Error: Using $this when not in object context
in .../wp-content/plugins/wp-worthy/class-wp-worthy-pixel.php on line 128

Call stack:

wp_worthy_pixel::getPixelPublicFromURL()
wp-content/plugins/wp-worthy/class-wp-worthy-migration.php:273
wp_worthy_migration::migrateByMeta()
wp-content/plugins/wp-worthy/wp-worthy.php:6064
wp_worthy::migrateByMeta()
wp-content/plugins/wp-worthy/wp-worthy.php:5874
wp_worthy::migratePosts()
wp-includes/class-wp-hook.php:292
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:316
WP_Hook::do_action()
wp-includes/plugin.php:484
do_action()
wp-admin/admin-post.php:70

The plugin works with PHP 8.0 and is not using any function that has been deprecated or removed.

Hi @tiffr,

you can find a toggle at “Settings -> Antispam Bee -> Advanced -> Spam-Notification by email”. Uncheck this box and save the settings.

Hi Pete,

unfortunately I can’t tell from the error message, what the issue might be. As you are also using a lot of plugins, it’s hard to tell which one might be in conflict.

I can only suggest to try out the plugin this plugin, which is similar to mine: https://de.www.ads-software.com/plugins/preferred-languages/

Thanks for your PR! I have just merged it, tested it locally and released a new version with your fix.

There are too many front end editing plugins out there to potentially integrate into this plugin. I will focus on the two backend editors.

As the check is being made by an AJAX request, you could extend it yourself by writing some JavaScript to check the title from that frontend editor.

As posts/pages can be saved and published in many different ways, this plugin could not guarantee that there would be no published post with the same title.

There are also many valid reasons for having posts/pages with a duplicate title.

This plugin is only meant to be a tool informing an editor that a post/page with the same title exists.

Therefore I will not implement something into this plugin preventing an editor from saving or publishing a post/page with a duplicate title.