Hanno

To call a problem solved by saying that you can’t test the theme because it’s not free is simply cheeky. Divi is not that rare on the market, is it? I’d rather find another solution for guest posts. Thanks for nothing.

How come … thanks for the hint

Yes, feel free to do so. As I wrote, I had to deinstall the plugin in order to have the site working ok. I will try and reproduce the problem on a different (test) site, but I will need some time to get back to you.

Thank you for your patience.

My experience: If the web server shows “500” errors, don’t immediately blame the developer, but perhaps have a look at the server log files. A directive was missing, which is why read access to the directory with the webp files failed. After the server-side problem was fixed, the plugin works like clockwork, with noticeable effects on performance. And the support was great and stress-free. Thank you!

• This reply was modified 7 months, 1 week ago by Hanno.

Thank you for caring. It’s a website that’s already online, so I’m not relying on help coming anytime soon (if ever); I’ve seen too many times (regarding other plugins) that it doesn’t happen at all. So please understand my reaction, you simply loose confidence.
I will try once more to get the plugin to work, but this time with only a single file that is not displayed on the fly, instead of the bulk option. I would get back to you afterwards.

I would definitely like to complete the setup in places that may still be missing. But you would need to know what that is. And as long as your server returns a 500 error, unfortunately no help is available at all. Instead, there are messages such as “License Check Failed” and “Verification not possible” – none of this really helps without further explanation.

Would be even better if there was no autocomplete at all …

Thank you very much for your reply.

I must admit, this was a rather weird situation that I am neither able nor willing to reproduce because it has to do with a server misconfiguration. Let me try to explain:

It’s all about a directory on a Linux server that was connected to another local server via CIFS. So, the directory had initially been created empty, and then redirected (mount -t cifs). As long as the remote server was in its place, everything was ok. But then that server was replaced by another machine, and the CIFS connection was no longer needed. As the remote machine had changed, that connection became invalid. However, the empty directory was still in its place. If you did an ‘ls’ command on a higher directory level to show the dir structure, it would show up. If you would try to get any details on that specific dir from the command line, it would simply appear as empty. However, the routine SplFileInfo::getSize() that is being used by your software, seems to behave somewhat differently, and it brings forward an error (sorry for the German error messages):

[19-Jul-2024 02:02:55] Komprimiere Dateien als TarGz. Bitte habe einen Moment Geduld.
[19-Jul-2024 02:03:36] FEHLER: SplFileInfo::getSize(): stat failed for /data/web/www.xyz.de/vi
[19-Jul-2024 02:03:36] 2. Versuche, Backup-Archiv zu erstellen …
[19-Jul-2024 02:04:17] FEHLER: SplFileInfo::getSize(): stat failed for /data/web/www.xyz.de/vi
[19-Jul-2024 02:04:17] 3. Versuche, Backup-Archiv zu erstellen …
[19-Jul-2024 02:04:58] FEHLER: SplFileInfo::getSize(): stat failed for /data/web/www.xyz.de/vi
[19-Jul-2024 02:04:58] FEHLER: Schritt abgebrochen: zu viele Versuche!

But this is not the point. I was wondering why your software tries to collect information *at all* on directories which it is configured not to take care of. If it tries to get the size of such a directory, how can I be sure that it does not collect other (more sensitive) data?

Thank you for your quick reply.
I had already created an additional role, the cause of the “problem” initially was that I had hidden the selection between all and own events because the planning of responsibilities was different at that time, so editing the others’ events was not needed then. In the end I had simply forgotten about this – sorry, my mistake.
Afterwards, the display worked, but whenever I tried to narrow down the search using the search field, the selection “all events” (admin_mode) automatically changed to “own events” again.
I have now found out that the reason for this is a missing hidden field “admin_mode” in templates/tables/events.php (see lines 41 ff.).
The missing code that would have to be added should somehow look like this:
<?php if( !empty($_REQUEST[‘admin_mode’]) ): ?>
<input type=“hidden” name=“admin_mode” value=”<?php echo esc_attr($_REQUEST[‘admin_mode’]); ?>” />
<?php endif; ?>
With this additional code everything works fine. Maybe you would want to fix this bug in a future version.

Thanks again for your work, this is really a great plugin.

Now that I have found the cause of the reported problem (sorry, my mistake), I would like to know how I could somehow permanently activate the GET parameter “admin_mode” in the frontend. When I click on “All events” and then enter a search term for filtering, the software switches back to “My events” and I get no results for that user (because he/she didn’t generate any). I hope I have described the behaviour clearly enough … Thanks.

Just gave it another try, now it works. Wonder what went wrong before …
Thanks anyway …

No it isn’t. If I add a <br> tag, this is just deleted, and the second line is positioned right after the first line.
Do I just have to insert <br>, or any additional things like % or so as well?

Problem has first been reported for 3.2.16, still the same in 3.2.17 …
Hello – anybody at home ???

Just found out the reason for this misbehavior was the .htaccess file that comes with the update. When deactivated (eg. change file name to 0.htaccess), everything is ok.

Well, somehow it made sense that your plugin didn’t work. Because after I had changed the setup of ImageMagick as required by your plugin to work, WordPress suddenly created the thumbnails itself with on-board tools. So why install this crap plugin at all? Totally superfluous. Oh yeah, I’ve already uninstalled it. And I will pay more attention to the author of other plugins.