Hanno

Hi Karina,

thanks for your response.
The button in question is most probably default WordPress (it is called “Bulk select”), you might want to check out this article: https://wordpress.com/forums/topic/bulk-select-in-media/
Regarding a translation proposal, I will send you a separate email.

Same thing happened to me, too. Kind of weird, though …

If you run an Apache server, and you have access to the config files, you should use the RemoteIPHeader directive:
RemoteIPHeader X-Forwarded-For
Look here for more details on how to use this directive correctly:
https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html
I found that, with this directive in place, the plugin works well without any modification – as long as you do not use an Ajax modal login.

It works.
Thank you for the quick reply, appreciated.
– Hanno

Thank you very much for your help, it works!

-Hanno

Just realized that this seems to be a fairly old issue (cf. GitHub in the “Images not listed in Admin panel” thread).
Is this plugin still maintained at all? According to the plugin details, the last fully supported WordPress version is 5.5.5. Meanwhile it’s 5.7.2, and nothing has happened in the meantime?

Same problem here, but I don’t have an events calendar installed. Reason for not showing must be different.

Update to 13.0.5 is still buggy. Did you have a close look to the error log I posted (pls. look above)? What else do you need to locate the problem?
Just read the line which starts with “PHP Fatal error” to the end, and afterwards try to locate the file which your code tries to use. Does it exist? NO!!!
OMG, you amateurs!

I tried 13.0.5, still faulty (link leads to another thread)

I *did* test 13.0.5. The fatal PHP error still exists. I posted the PHP error log in some other thread, but you (software developers) probably do not read those messages thoroughly enough.
If you did so, you would have known the reason for the issue, and could have reacted properly. You can’t just purge a complete folder structure with all the classes needed, place them somewhere else, but have a call inside your update procedure which tries to use files in that deleted folder structure.
This is an issue which I would have expected from some bloody amateurs, who publish software without testing.
For everyone that comes across the issue: After updating the plugin, you will not be able to access the admin dashboard (because meanwhile there has been that fatal PHP error which has not been caught properly). Instead, start the frontend of your site (which will definitely continue working), and afterwards login as usual. That should work.

• This reply was modified 4 years, 2 months ago by Hanno.

Offering users a free plugin instead of trying hard to get rid of the problems which obviously still exist to a certain extent, is not the right way IMO.
Today I tried to update a test site from v12 to 13.0.4 which, in your opinion, should work smooothly. Maybe you would want to take a look at the error log (domain name is anonymized):

[Mon Dec 21 10:49:18.608429 2020] [php7:error] [pid 8487] [client 90.187.31.177:52208] 
PHP Fatal error:  Uncaught Error: Class 'WP_Statistics_Updates' not found in /data/web/www.xyz.tld/wp-content/plugins/wp-statistics/includes/classes/class-wp-statistics-welcome.php:78
Stack trace:
#0 /data/web/www.xyz.tld/wp-includes/class-wp-hook.php(287): WP_Statistics_Welcome::do_welcome()
#1 /data/web/www.xyz.tld/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#2 /data/web/www.xyz.tld/wp-includes/plugin.php(484): WP_Hook->do_action()
#3 /data/web/www.xyz.tld/wp-admin/includes/class-plugin-upgrader.php(371): do_action()
#4 /data/web/www.xyz.tld/wp-admin/includes/ajax-actions.php(4452): Plugin_Upgrader->bulk_upgrade()
#5 /data/web/www.xyz.tld/wp-includes/class-wp-hook.php(287): wp_ajax_update_plugin()
#6 /data/web/www.xyz.tld/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#7 /data/web/www.xyz.tld/wp-includes/plugin.php(484): WP_Hook->do_action()
#8 /data/web/www.xyz.tld/wp-admin/admin-ajax.php(184): do_action()
#9 {main}
thrown in /data/web/www.xyz.tld/wp-content/plugins/wp-statistics/includes/classes/class-wp-statistics-welcome.php on line 78, referer: https://www.xyz.tld/wp-admin/plugins.php

The only way to save this plugin is to completely withdraw all updates 13.x and to develop it again from the scratch.
Asking users to install an apparently not fully tested plugin into a running system and asking them to report if it worked is a complete no-go.
What kind of professionals are you guys? You can be happy that probably most people here only use the free version and therefore have no liability claims against you.
And how on earth can you dare to describe this problem solved?

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

The current version of WP Statistics requires the installation of php7-bcmath, which was not mandatory until now. Most likely, the webhoster will have to respond to this.
[Update] But even after installing the php module there is still an error message and the backend does not answer (nevertheless the frontend still works). The backend is ok after you restart the browser completely.
This is not what I would call a smooth transition. I would have expected that updates are thoroughly tested before publishing?

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

Thank you for the quick reply. It works.

Hi all,

@silviaetnonautas: If you need a quick solution there is no choice but switching to a different map solution. I decided to use “WP Google Maps” which interacts perfectly with the Complianz plugin. Besides, compared to the simple divi module, I was surprised to see all the additional features the plugin offers.
As Elegant Themes do not use the Consent API, and switching to that API would probably mean a major code change, I suppose we will not see any compatible module in the near future.

@aahulsebos: There is still that ugly ?Ich stimme zu? in the German po file, which could be fixed very easily (and I would not have to edit the po file every time there is a new update from you).
Here is the correct snippet from the po file:

#: integrations/plugins/wp-google-maps.php:23
msgid "To enable Google Maps cookies, please click \"I Agree\""
msgstr "Um Google Maps-Cookies zu aktivieren, bitte auf \"Ich stimme zu\" klicken"

I would highly appreciate if you could include this tiny change in your next update.
Tx Hanno (@bsoftde)