Kevin Pfeifer
Forum Replies Created
-
Forum: Plugins
In reply to: [Events Manager - OpenStreetMaps] PHP Warnings in WP BackendYes you are right.
I didn’t see the “plugin” directory in my theme after installing the plugin.
My current setup overwrites the whole theme folder every time i change something in SASS, JS or other source files.
That was the reason why i got these warnings.
Forum: Plugins
In reply to: [Events Manager - OpenStreetMaps] PHP Warnings in WP BackendReloading the page didn’t fix the problem for me. Event after a few minutes.
Debugging Mode is also disabled on my page.
But now they aren’t present for me so i will wait a few days if they reappear.
Thanks for the quick response!
Hello Patrick!
You have created a very nice plugin!
Just installed it and works like charm. Thanks ??
Forum: Plugins
In reply to: [The Events Calendar] Single Event Page – GMap trippled controllsYeah, im so sorry.
Have to post it in Events Manager, not Events Calendar…
As i don’t use your plugin any more i cant tell if it is fixed now.
I can only tell you that the “PseudoRandomStringGeneratorFactory” has a function to detect which is the best way to “detectDefaultPseudoRandomStringGenerator”. It implements the new “random_bytes” function, which doesn’t generate this warning.
OK, new information.
In the official Facebook PHP SDK Github Repo there is a closed issue with the mcrypt_create_iv() problem.
See here: https://github.com/facebook/php-graph-sdk/issues/850Seems like you should use the “PseudoRandomStringGeneratorFactory” instead of the “McryptPseudoRandomStringGenerator”.
But this is missing in your Plugins library folder because your current Facebook PHP SDK version is 5.0.0. The most current version on Github is 5.6.1.
Please check that @muffuss
@muffuss
You can use this Plugin with at least PHP 7.1. With PHP 7.2 this function will be removed from PHP and therefore a PHP Error will occur and your site (or the part of the Plugin, which uses this function) wont work any more.
It just generates a “PHP Deprecation” warning in the debug.log of WordPress, because it uses an outdated function.
See link here: https://php.net/manual/de/function.mcrypt-create-iv.phpThe Plugin still functions as normal with PHP 7.1, but any future PHP Versions will break your website (or the part of the Plugin, which uses this function) because of the deprecated function.
But as mentioned from @heateor the part of the programm, which uses this deprecated function, is part of the Facebook SDK, which will be updated in the next release.
But as of right now, i have the Version 7.11.13 installed and this problem is “still” not resolved.
But probably the plugin developers cant do anything, because the SDK is provided by Facebook. So if Facebook doesn’t update their SDK to work with PHP 7.2 or higher, there will be more trouble to come.
- This reply was modified 6 years, 9 months ago by Kevin Pfeifer.
- This reply was modified 6 years, 9 months ago by Kevin Pfeifer.
- This reply was modified 6 years, 9 months ago by Kevin Pfeifer.
- This reply was modified 6 years, 9 months ago by Kevin Pfeifer.
Forum: Plugins
In reply to: [EU Cookie Law for GDPR/CCPA] IE11 JS Error in v3.0Hello @milmor,
yes the 3.0.1 version fixed the Problem in IE11.
Thanks for the quick response and fast fix.
Forum: Plugins
In reply to: [EU Cookie Law for GDPR/CCPA] IE11 JS Error in v3.0I don’t know how this plugin works exactly or in other words, im not the programmer of this plugin.
I just reported the problem with as good as possible error messages.
The link to mozilla with the default parameters is just a tip for the developer(s) what the actual problem is and how to solve it.
Probably there are more JS functions with default parameters in it that should be refactored.
- This reply was modified 6 years, 9 months ago by Kevin Pfeifer.
Dear John Godley,
thanks for the fast reply.
I have managed to revalidate the problem. Here is the new description:
If the plugin is not installed/activated, the redirection between “7-things-i-want-to-show-you” and “Seven things i want to show you” works without a problem in both directions.
If the plugin is activated, neither directions are redirected properly to the new URL and the 404 page is shown.
So this functionality is implemented in the WordPress core.
Can you reproduce this problem?