Remco Tolsma

The changelog should now also be automatically included in the www.ads-software.com readme.txt file with every release.

Pronamic (KVK-number: 01108446) is a small WordPress development agency from the Netherlands and works with a team of ~ 5 people.

Is there any way I can help to get this topic resolved? Is it useful to open an issue on GitHub? Or is development not done via https://github.com/wp-media/backwpup? Or should we also hide the admin notices with CSS as @milouze mentioned? If we can get an update on what users can expect here, that would be nice.

As several users have indicated in this topic and other topics, this update unfortunately did not solve the problem for me either. Perhaps the transient use should be looked at again, as @eusebiuoprinoiu previously mentioned in a deleted comment:

I have the same issue, and it’s very annoying.Transients are not a good place to store the visibility status for notices. Transients are removed all the time, sometimes on a schedule (daily, weekly, etc), after every server restart for websites that use Redis or Memcached, etc.If you want the notice to disappear for all users once the Dismiss button is clicked, you should save the visibility status as an option.If you want the notice to be dismissed by each user, you should display the notice conditionally, for administrators only, and save the visibility status in the user meta.

and:

As long as the dismiss status is saved in a transient, the problem will not go away.Transients are volatile in nature and can be removed before they expire in many situations.Even if they are set to expire one year later, there is no guarantee the transient won’t be removed 5 seconds after it was created, for any number of reasons.The only way to fix this to save the dismiss status either as an option, or in the user meta.

I personally thought these were valuable additions. I didn’t realize yet that a server restart with Redis or Memcached could also have this effect. Perhaps based on this feedback it can be looked at again? Thank you in advance.

I am currently busy with other work and cannot provide further details. However, there are several users reporting the same problem, so hopefully you will find a cause. I do have my doubts about the transients, you have no guarantee that the transients will be stored for 90 days. If the transients functionality works differently due to the caching and optimization plugins, this may result in users seeing the notice much earlier again. That causes frustration, it seems to me that you want to avoid that, and so the Transient API is not a good choice for this feature.

Transients might disappear one second after you set them, or 24 hours, but they will never be around after the expiration time.

Source:?https://developer.www.ads-software.com/apis/transients/

PS the Transient API also works with options, by default it stores 2 ‘real’ options for each transient ('_transient_timeout_' . $transient and '_transient_' . $transient): https://github.com/WordPress/wordpress-develop/blob/6.5/src/wp-includes/option.php#L1272-L1372.

• This reply was modified 8 months, 2 weeks ago by Remco Tolsma.

Dear Restrict Content developers, do you expect to resolve this deprecated message?

No problem, I think that’s what these community support forums are for. Because you mentioned the Stripe plugin from Woo, I would like to say that I am not satisfied with the support handling of Woo (or WooCommerce). I have been waiting since October 27, 2023 for the handling of a support ticket (7213916) related to https://woocommerce.com/products/eu-vat-number/ (also from Woo, even an annual paid product). That is not relevant to this topic, but it is something to take into account when using products such as https://woocommerce.com/products/stripe/. I don’t expect the support on the Stripe plugin to be much better, that may be something to take into account. Stripe is probably not ideal for everyone, fortunately there are also other good payment providers for the Dutch iDEAL.

In addition to the WooCommerce plugin, you probably also have a plugin active for integration with EMS. Can you also find the exact title of this plugin in the WordPress admin dashboard under “Plugins”? And can you also see who is the author of this EMS plugin? If you use the “EMS Online” plugin from “Ginger Payments” then I don’t think any changes are necessary. If you are not yet using this plugin, you may consider switching to this plugin (https://github.com/emspay/ems-online-woocommerce). I must say that I have not had very good experiences with EMS myself. In that respect, a switch to Pay.nl, Buckaroo or Mollie may also be worthwhile. You can then also consider using the Pronamic Pay plugin. This is a plugin with support for all popular Dutch iDEAL (2.0) providers. A Dutch company is behind this with an excellent support department, no ‘kastje naar de muur‘ scenes with them.

I don’t know how exactly this helps me. The error message comes from this plugin and is also quite easy to solve by the programmers of this plugin. So the question is whether a programmer of this plugin wants to solve this?

Have there been any developments for this issue?

@daniellaivanova It’s a bit annoying that you don’t have an ETA yet. This issue continues to cause problems for us and possible other customers. Some websites become completely inaccessible due to this issue. Perhaps you do not realize this sufficiently and this issue is therefore not given sufficient priority? Could you make this more of a priority and issue an ETA?

I came across this error message in version 1.7.2:

Deprecated: Creation of dynamic property P2P_Side_User::$query_vars is deprecated in /var/www/html/wp-content/plugins/posts-to-posts/vendor/scribu/lib-posts-to-posts/side-user.php on line 8 

I have created a new topic for this:
https://www.ads-software.com/support/topic/php-8-2-%E2%86%92-deprecated-creation-of-dynamic-property-p2p_side_userquery_vars/

Je kunt ook overwegen om gebruik te maken van een andere formulieren plugin voor WordPress. Voor veel populaire WordPress formulieren plugins zoals Gravity Forms, Ninja Forms, Formidable Forms, Contact Form 7, etc. zijn ook wel koppelingen met Mollie beschikbaar. Zelf ben ik groot fan van de formulieren plugin Gravity Forms, die zit goed in elkaar en heeft veel mogelijkheden. Het is wel een betaalde plugin, maar het is zeker de moeite waard. Met de gratis https://www.ads-software.com/plugins/pronamic-pay-with-mollie-for-gravity-forms/ plugin/add-on koppel je deze eenvoudig aan Mollie. Mocht je liever werken met één van de andere genoemde formulieren plugins dan is dat ook mogelijk met Pronamic Pay. Ook handig als je klant bijvoorbeeld overstapt van Mollie naar Buckaroo, Pay.nl, MultiSafepay, Rabo Smart Pay, etc..

I noticed the same issue, could be related to the following topics:

• https://www.ads-software.com/support/topic/bug-thats-breaking-scripts-defer-render-blocking-causes-scripts-to-404/
• https://www.ads-software.com/support/topic/js-optimization-causing-scripts-to-404/

@samovaari If this is issue is not resolved for you, you could mark this topic as not resolved.

We see the same problem, opened a new topic following the forum rules:
https://www.ads-software.com/support/topic/js-optimization-causing-scripts-to-404/

@mediavine @plamenm Can you mark this topic as not resolved? Thanks.

• This reply was modified 1 year, 3 months ago by Remco Tolsma.