doffine

Hello @robert681,

thank you for letting us know. I’ve just rated the well deserved 5 stars. Have a nice weekend!

Greetings,
-doffine

Hi @robert681,

thank you for your quick and positive response and again for your good work! I mark this thread as resolved then.

Greetings,
-doffine

@7thcircle, exactly this is the case. You put it into one sentence where I needed a whole story ;-).

So the question would be how to natively switch that badge off. We don’t want to do it via backend CSS display:none or sth. like this.

Greetings,
-doffine

Hi @zealopensource,

thanks for coming back to us. We already had noticed that this option is currently not available.

That’s why we contacted you this way to ask if it would be possible that you realize this feature request in an upcoming release of your plugin. It seems not to be very obvious and user friendly that you can place CF7 form content into the resulting PDF’s body, but not in the PDF’s footer. So will you implement this option?

Thanks for your good work,
-doffine

Done.

Thanks again for your good work,
-doffine

Hello @addonpro,

we updated it and the problem is solved. Thanks a lot for the quick solution.

Greetings,
-doffine

We have the same problem here. We already had it at least with 8.9.3 and hoped to get it away with the next 9.x release. But it simply isn’t dismissible.

-doffine

Hi @firelightwp,

thank you for letting us know. We just updated and can confirm: The issue is resolved here, too.
Thanks a lot for the quick fix.

Greetings,
-doffine

Hi @rednumber,

may I ask you again to keep the changelog updated? Else updating your plugin always is kind of a blind flight.

Thank you again for your good work,
-doffine

Hi Alan,

first of all let me say a big thank you for your instant reaction and update. I just wrote a review for your plugin.

I think the solution you describe above would be most user friendly and doesn’t completely forget your own needs. It would be a very good solution.

To be honest I ask myself in numerous cases how it can pay off for plugin developers in the WordPress ecosystem to invest all their work to develop a free plugin and keep it running. Often it must be more a hobby than a business that pays someones bills. Or someone who uses WordPress himself wants to give something back to the WordPress community idealistically.

Because of the risk that a free plugin gets abandoned we as an agency prefer to use premium plugins and themes in crucial parts of our installations because the money paid should increase the chance for the component to be as long-lasting as possible.

So I think the widespread model to offer basic functions for free while having a premium version with costs that has advanced features is a good way to keep everything realistic.

Thank you again for all your work and this exemplary reaction,
-doffine

Hi Alan,

I understand. Of course it would be great if you’d just remove those messages. For us this would be the best thing. On the other side I understand the wish for reviews.

What ever you do, please keep agencies as ours in mind. It’s always a pain if single plugins that we use in hundrets of WPs suddenly need a click or interaction in every installation, or sth. like that, because for us that means one hour of brainless mass-clicking in every single installation.

What is great in your plugin was, that it was enough just to install it to stop user enumeration. No configuration needed. So we just could install it automatically with our WP management console into every single installation and that was it. No individual clicking in every single installation needed – that truely was great! ??

Many greetings again,
-doffine

Hi Alan,

that sounds great. So we’ll just wait for an update.

Thanks for your work and have a nice day,
-doffine

Hi 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,
-doffine

Hi @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,
-doffine

Hey @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,
-doffine