doffine
Forum Replies Created
-
Forum: Plugins
In reply to: [Stop User Enumeration] 5-star rating message isn’t dismissibleHi Alan,
that sounds great. So we’ll just wait for an update.
Thanks for your work and have a nice day,
-doffineForum: Plugins
In reply to: [Stop User Enumeration] 5-star rating message isn’t dismissibleHi Alan,
thanks for coming back to us so quickly. In the browser JS console we don’t see any notices before or after we try to dismiss nor do we see any other JS errors there. We are using PHP version 8.1.28.
The plugin also doesn’t return a 500 in the network tab of the console. But we see an error as follows:
Status: – / Method: POST / Host: <host> / File: admin-ajax.php / Initiator: xhr / Type: – / Transfer: NS_BINDING_ABORTED
But: We also see this error in cases, when the dismiss did work.
Another interesting thing: It seems to be a Firefox (at least 125.0.3 (64-Bit)) thing. In current Chrome dismissing always works. In Firefox it is like described in this thread. And even in cases where we can click in Firefox 20 times without successfully dismissing, we just have to use Chrome on the same Win 11 machine and the same message is gone after one single click. After this, on reload it is gone in Firefox, too.
Additional information: We are hosting the 250+ WP installations on four different servers in different data centers and see this behaviour in Firefox everywhere.
Many greetings,
-doffineHi @jaimeimagely,
ok then. We tried setting both WP_DEBUG and WP_DEBUG_DISPLAY to false (first was false before, second didn’t exist so far) but that didn’t change anything. Only thing that helped was setting display_errors = 0 in php.ini. Perhaps that is of importance for you.
We know that production websites always should be set not to display php errors. But not everyone sticks to that. So plugins should take care at least on public/frontend sites (including sitemap pages) that there are no warnings/errors/etc. All of the >100 different plugins we are using in many WP installations comply with that or at least fix frontend warnings as soon as possible.
Nonetheless have many thanks for your great plugin and your work!
Greetings,
-doffineHey @jaimeimagely,
thank you very much for coming back to us. Yes of course, we wouldn’t see those warnings if we switch them off. But switching them off doesn’t mean that there is no problem. We then would only close our eyes in front of them.
So we wanted to let you know about this “Undefined property” in your nextgen-gallery/src/Legacy/lib/sitemap.php on line 81 and think you will want to fix this, since it potentially breaks sitemaps. Will you?Greetings,
-doffineHey @mduodoj, with the current version 5.9.2 of CF7 that got released today the problem is gone in our installations.
Greetings,
-doffineWe also did a rollback in one of our websites with an unhappy customer and it worked. Now we ask ourselves how long to wait for the fix. Depending on that we perhaps could wait or we would have to do much work to rollback it in dozens of websites more.
Greetings,
-doffineForum: Plugins
In reply to: [Contact Form 7] Checkbox emptyWe also have this problem in dozens of websites and ask ourselves when the fix can be expected approximately – just to plan our next steps.
If the fix will be there in the next very few days we would tend to wait. If it will take another week or more we would have to consider a rollback in many, many websites which will result in much work.
Thanks so much for the work and this great plugin,
-doffineHello again @angelo_nwl,
Divi’s support just responded: “Seems that the method was called before the content was loaded.” Perhaps this helps you.
Greetings,
-doffineHello @angelo_nwl,
thank you very much for coming back to us. We use the current version of Divi (4.24.2). Since Divi is a premium theme there unfortunately is no open download link available.
Greetings,
-doffineHi @shehabulislam,
yeah, you are right: In your current version 2.5.27 we cannot find the problem anymore :). In the previous version 2.5.26 this problem definitely still was there, no matter if we downloaded the ZIP freshly here from the repository.
Anyway: Now this problem is resolved, too, no more 404 errors. Thanks a lot!
Greetings,
-doffineHello @shehabulislam,
we checked it in tastewp.com and indeed there we don’t see the 404. So we looked into it. We use the most current version of your plugin in our installations, too.
The problem seems to be in your file html5-video-player/inc/Field/VideoPlayer.php in line 211:
‘picker’ => ‘< img src=”‘.plugin_dir_url(_ _ FILE_ _ ).’./../img/aws.png”/> Choose From AWS S3 Storage’,
(I added the blanks between the < and the img tag and the double underscores because else the display here gets wrong)
Anyway, this line produces an HTML output as follows:
< img src=”https://www.DOMAIN.TLD/wp-content/plugins/html5-video-player/inc/Field/./../img/aws.png”/> Choose From AWS S3 Storage
This produces the 404 request to https://www.DOMAIN.TLD/wp-content/plugins/html5-video-player/inc/img/aws.png that is shown in our browser console.
I don’t know why “‘.plugin_dir_url(_ _ FILE_ _ ).’./../img/aws.png” resolves in all of our installations on different servers to “/wp-content/plugins/html5-video-player/inc/Field/./../img/aws.png” in the HTML source code (especially where the “Field/” component in this path comes from) but I guess you will know why.
Greetings,
-doffineHi @shehabulislam,
we just updated your plugin to the latest version and have to state that the 404 bug is still there on the WP backend page that opens when you edit an existing video entry. We checked it in two different WordPress installations and both still have this 404. The error message is exactly the same as described in the initial posting above.
Since we don’t use any caching and did reload the page multiple times with STRG+F5 on different browsers for us it is clear: This bug hasn’t been fixed so far.
Therefore I marked this thread as “not resolved” again. Will you have another look on this problem?
Greetings,
-doffineHey @mdashikul,
we just checked it and can confirm the bug has been fixed. Thanks a lot for your work!
Greetings,
-doffineForum: Plugins
In reply to: [Ultimate Maps by Supsystic] Map cannot be savedHey @supsysticcom,
thank you for letting us know. We just updated and can confirm that this bug is fixed now and everything works fine. Great! 🙂
Thank you a lot for your work,
-doffine
