PHP v7.4 Deprecated function

Thank you for the bug report. We added it to our list.
We’ve been extremely busy and haven’t had the time to attempt to fix the SVN issues. I’m so sorry. It’s bothering us that we’re unable to upload it but being too busy is causing this delay.

Anyone needing any update to a free plugin can contact us on our website in the meantime.

Thanks for counting in the issue.

For me the SVN issues have obviously more priorities than for you. This is because the old version deployed via wp.org DOES NOT WORK ANYMORE! So what you deploy is a waste of time for new people trying to evaluate the plugin on one hand and on the other they will clearly never turn into your customers. Have you given up to attract more customers? What can make you so extremly busy that you push potential customers away? Not to forget: it raises even for existing customers a red flag seeing that you treat things like that.

The best,
Frank

• This reply was modified 4 years, 1 month ago by Frank.

We’re only replying as we know this can affect how we’re viewed.

Quick points:
– Paid plugins are still updated. Free plugins as well but unable to be launched via SVN for the moment.
– We definitely care and still update our plugins.
– As a developer of ours told us, we have some issues with SVN and launching the new updates. Unsure why yet but it’s definitely bothering us, as mentioned above.

We always suggest for everyone to “put themselves in other people’s shoes” and not to come to conclusions. If you were a Tribulant staff, you’d understand how busy we are with Tribulant work, and where priorities should be, especially when understaffed.

Have a great day ahead.

I don’t want to be bothersome. The opposite. I am interested in a working plugin. But what you deploy on wp.org, as said, is broken.

See how wp.org advertises your plugin:

• “Last updated: 1 year ago”
• “This plugin hasn’t been tested with the latest 3 major releases of WordPress.”

Those are NOT my warnings.

Good luck with the strategy.

Deprecated message still appears. Is it fixed meanwhile in a version not submitted on wp.org and that needs to be requested here?

Thanks for the efforts!