Oh, how cool. I’d be happy to do that. Just so there are no misunderstandings, the error occurs locally when using https://localwp.com/. File permissions should therefore exist across the board. The plugin works perfectly on the staging server.
Environment:
web server: nginx
PHP 8.2.27
WordPress: 6.8.2
all caches cleared
Attached is the content of the log file. I am available for any questions.
Thank you for your prompt response. Oh, you are correct. I apologize; it is functioning on the staging site. Nevertheless, please find the debug log below, in case it is of interest.
[08-Aug-2025 14:43:20 UTC] PHP Fatal error: Uncaught Error: Class "Secure_Passkeys\Core\Secure_Passkeys_Application" not found in C:\Users\[]\Local Sites\clean-install\app\public\wp-content\plugins\secure-passkeys\bootstrap.php:9 Stack trace: #0 C:\Users\[]\Local Sites\clean-install\app\public\wp-content\plugins\secure-passkeys\secure-passkeys.php(45): require() #1 C:\Users\[]\Local Sites\clean-install\app\public\wp-admin\includes\plugin.php(2387): include_once('C:\\Users\\[]\\...') #2 C:\Users\[]\Local Sites\clean-install\app\public\wp-admin\includes\plugin.php(673): plugin_sandbox_scrape('secure-passkeys...') #3 C:\Users\[]\Local Sites\clean-install\app\public\wp-admin\plugins.php(60): activate_plugin('secure-passkeys...', 'http://clean-in...', false) #4 {main} thrown in C:\Users\[]\Local Sites\clean-install\app\public\wp-content\plugins\secure-passkeys\bootstrap.php on line 9
I have the same problem. It only works with 6 slides, but not with just 4 or 5. Instead of running through a loop, the slides suddenly swap order, it can’t be slid any further and the pagination doesn’t work either.
It would be great if you could solve this.
Best regards
This reply was modified 1 year, 7 months ago by kiandept.
thanks for the quick help! Thanks for the precise instructions! I have implemented so far (screenshot 1). The placeholder is displayed with OpenStreetMap and also shows the consent option. On the gdpr settings page OpenStreetMap is displayed as a service, but the field to give consent is missing (screenshot 2).
I will try to solve the problem with the map markers afterwards. I am already in contact with the colleagues from Geo My Wp. They are very interested in an implementation.
About help I would be very happy.
Kind regards, Kian
This reply was modified 2 years, 9 months ago by kiandept.
thanks for your fast reply!!! It works so far, thx! But I don`t use Google Maps – is it possible to integrate OpenStreetMap as a clickable single service? I’ve replaced “google-maps” with “openstreetmaps”. While OpenStreetMap is recognized in the Complianz settings, it does not appear as a standalone service on the GDPR settings page. Could this be because OSM uses cookies? Would it be necessary for me to install the Leaflet or OSM plugin?
In addition, despite agreeing to the cookies, the code is blocked so that the info window on the map is no longer displayed when clicking on the map marker. Otherwise the Ajax form works as it should. Only when the manual implementation of Geo My WP KB is deactivated (as shown in screenshot 1), do the info windows on the map become available again (as demonstrated in screenshot 2).
About help I would be very happy.
Kind regards, Kian
This reply was modified 2 years, 9 months ago by kiandept.
Thank you very much! I had cleared the cache yesterday and the complete banner disappeared. Therefore I thought that the function refers to the complete banner. Just tried again. Now it works. Thanks for the very fast support.
Sorry, it got lost on me. So the error occurs through BuddyX in connection with the BuddyBoss Platform. When using the integrated form to register, the MailPoet settings page incorrectly shows that the newsletter is subscribed.
Wow, thank you so much for the quick feedback and explanation! Let’s hope for a quick solution, because the current version of BuddyBoss is absolutely not privacy compliant in the EU.
I just realized that the error is not reproducible within a blank installation. I’ll get back to you next week with info on which plugin is causing the error.
