Hanno

If you think answers like “Ask someone else” or “There must be some difference between the two platforms, try to find out the differences yourself” (I read this in another support request) are something that could be called “support”, and if you furthermore *dare* to call those issues solved, then I’ll take it without accepting it.
If you had paid just a little attention to the causes of at least my problem, you would have known that it is obviously about a security feature in ImageMagick, and that there is a possibility that security holes can arise when settings are made to that tool, as they are apparently necessary for your plugin.
After you didn’t even give the slightest hint of a possible cause, I found it surprisingly quickly with the help of Google, and I also saw that this problem is widespread on the one hand side, and that most obviously there are ways for the programmer to circumvent it on the other.
It’s up to each host to decide whether they want to cause themselves problems by changing the ImageMagick settings or whether they generally refuse to make these changes to the setup – I can certainly understand that.
Fortunately, I host my sites myself, and I know everyone else who uses my servers. So I don’t mind changing the ImageMagick setup because I think I can assess the risk. But if large providers don’t want to get involved, that’s understandable. Unfortunately, in this case, your app is completely unusable.

• This reply was modified 1 year ago by Hanno.
• This reply was modified 1 year ago by Hanno.
• This reply was modified 1 year ago by Hanno.

Well, it *is* a problem with the plugin, as long as you do not emphasize that a separate SMTP plugin is definitely needed to meet all the antispam regulations of email providers.
In fact, there are plugins around that include a HELO/EHLO command by default (which is not very difficult). I thought you were able to do so, too.
Anyway, I downloaded one of the SMTP plugins around, and I hope this will work.

You are absolutely right, and I have to apologize.
I now found out that the reason for the plugin’s misbehavior was a different plugin called ‘Frontend Post Submission Manager Lite’.
I believe that two JS libraries were not compatible with each other. However, I fairly quickly found another plugin (‘User Submitted Posts’) that apparently does its job without causing any problems to PDB, so the problem is solved for me.

” If you’ve defined a dropdown field, and have configured that field to be included in a list display (this is done on the Manage List Columns page) then for each record, the value of that field will be displayed in the list. “

Sorry to say you are wrong:
Dropdown fields do not show up on the Manage List Columns page at all, so they cannot be included in the list display.

I found that the error message will be displayed again and again (even if the error no longer exists), as long as it is not explicitly deleted from the screen. In fact, if the error persists, there is an additional error message, and on and on. I finally started wondering when there were four of those messages. So, actually there is no problem for the plugin to find the path, if it really exists.
I then had a closer look at the source code, and I am pretty sure that the function which creates the upload directory (“_make_uploads_dir”) is not called during install at all. There is a special error message in there which I should have seen if anything went wrong. (But I didn’t.)
Afterwards I tested the debug mode because I found that same function is part of the PDb_Debug class. It IS called immediately after saving the debug mode setting, and the directory was created without any hassle. For people that encounter the same problem and do not have direct access to the server’s file system this could be a workaround.
As for me, this thread can be closed, although I would not really call it resolved right now. Thank you, anyway, for your quick feedback, which has helped me a lot with troubleshooting.

After updating to 2.5.5 deinstall works fine. I deinstalled the old version completely, and afterwards installed 2.5.5 from the scratch. Still, the install routine does not create any subdir below the uploads folder, and still, the error message because of wrong permissions is there later on:
The configured uploads directory “/data/web/joh.bsoft.de/wp-content/uploads/participants-database/” for Participants Database is not writable.”
That message shows, although in the meantime I manually created a directory at exactly that location, with the appropriate settings (0775). So what?

Just tried to deinstall the plugin in order to prepare a clean install.
This is not possible at all. Here is the error log from the Apache server:

[Fri Nov 10 23:26:36.297943 2023] [php7:error] [pid 31728] [client 90.187.31.177:0] PHP Fatal error: Uncaught Error: Undefined class constant ‘attribute_store’ in /data/web/joh.bsoft.de/wp-content/plugins/participants-database/classes/PDb_Init.php:344\nStack trace:\n#0 /data/web/joh.bsoft.de/wp-content/plugins/participants-database/classes/PDb_Init.php(53): PDb_Init->_uninstall()\n#1 /data/web/joh.bsoft.de/wp-content/plugins/participants-database/classes/PDb_Init.php(95): PDb_Init->__construct()\n#2 /data/web/joh.bsoft.de/wp-includes/class-wp-hook.php(324): PDb_Init::on_uninstall()\n#3 /data/web/joh.bsoft.de/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()\n#4 /data/web/joh.bsoft.de/wp-includes/plugin.php(517): WP_Hook->do_action()\n#5 /data/web/joh.bsoft.de/wp-admin/includes/plugin.php(1269): do_action()\n#6 /data/web/joh.bsoft.de/wp-admin/includes/plugin.php(960): uninstall_plugin()\n#7 /data/web/joh.bsoft.de/wp-admin/includes/ajax-actions.php(4748): delete_plugins()\n#8 /data/web/joh.bsoft.de/wp-includes/class-wp-hook.php(324): wp_ajax_delete_plugin()\n#9 /data/web/joh.bsoft.de/wp-includes/class-wp-hook. in /data/web/joh.bsoft.de/wp-content/plugins/participants-database/classes/PDb_Init.php on line 344, referer: https://joh.bsoft.de/wp-admin/plugins.php?plugin_status=all&paged=1&s

Hope this helps

Well, I would really like to start testing the plugin, but I think you will agree, as long as there is an install issue, and probably some more issues arising from that (e.g. some image file that is referenced in your setup not being installed), I’d rather wait for a clean install.
I am now waiting for you to tell me the error has been found, install it again or whatever, and then I would continue testing. And if the plugin works properly, I would also offer you a complete German translation for free.

Microsoft Edge seems to work as expected, Mozilla Firefox doesn’t.

Just found out that Firefox works if you hold the mouse key down, then drag the mouse into the categories field and release the mouse key there. But that is not the way it should work, shouldn’t it?

• This reply was modified 1 year, 4 months ago by Hanno.

It works. Thanks so much.

Oh I see! Thanks anyway.

If there is an error it doesn’t create the event, that’s right. However, the title field below the error message now contains the misformatted text. If I correct the errors, and leave the other things that have already been provided as they are, all data are now stored in the database, including the misformatted title.
And no, I do not use a GDPR plugin. This is a setting of your own plugin: Privacy > Consent > Remembering consent

Thank you for your quick response.
I now installed the plugin on a different (“empty”) site, for testing. I found out that the problem only occurs if the plugin generates an error message before saving the event to the database.
Eg.: A new user does not check the agreement box at the bottom.
Or: You forget to provide an event date.
Consequently, an error message is generated, and the field contents that have already been provided by the user are then re-displayed. If the text contains characters that would have to be escaped, you will see the additional escape character.
Hope that helps.

Ok, I will try to find out and get back to you later.

Thanks for now!

I use the Divi Builder, the checker is included in their menu. But their support told me: “And that issue isn’t related to the Divi theme, it’s related to the WordPress syntax checker that needs to be updated in the WordPress itself.”

So who is in charge? Is it Divi or WordPress??