Ronaldt

Well it is not resolved yet.

I didn’t respond because you said you’ll take it up with the devs. So I’ve been patiently waiting.

Okay. Thanks for checking.

It has been 3 months. Three months. And still no update. Three months for a bug fix.

I would expect *way* different support when I visit your website:
https://premium.wpmudev.org/get-support/

Can you explain the difference between the PRO and the FREE version of this plugin? Do bugs get fixed and looked over by a different team or something?

Maybe time to open up the plugin and make it open-source so other developers can work on it too? I mean, the plugin absolutely has potential! If it works, it works great.

—

Apparently WordPress did not show me a notification and no new content after page reload so I expected that nothing was saved. Apparently it was. Sorry for the spam.

• This reply was modified 4 years, 5 months ago by Ronaldt.

Why can’t I reply to this topic anymore?

How are things moving along?

If it is in testing, can you maybe send the patch for this issue so we can apply it manually until the next update is released?
Or if we can get a pre-release build, send that?

We don’t need a full new version with a set of new features, we need a patch that fixes broken functionality.

It has been over two months and I have multiple clients that are really unhappy with us a company. We as a result are VERY unhappy with the way we’re being stringed along by you (as a company).

Bugs are not always straight forward and if they’re low in the virtual card house it can have bigger consequences than we can see on the outside. I get that, we’re developers too. But with the time it takes WPMU DEV to work out a bug makes me feel it is very low on the priority list.

I’m free to choose to either use your free-to-use product or not, I get that too. Many companies publish plugins for free to get the trust of their users so they eventually become paying customers. Not sure if this is something WPMU DEV is all about, but it does not feel like it from this side of the fence.
We’re an agency that manages 200+ websites where many have scattered plugins like GravityForms and Yoast (SEO) and were hoping to eventually migrate them all over to many of the WPMU DEV plugins to have more of a singular style.

At first we were very enthusiastic about what we saw and were about to become a WPMU DEV member. But as you can imagine we don’t want to take the risk that if one of your plugins has a bug, we a company will suffer for months and potentially lose face with our own clients because of something we have apparently zero control over (except for migrating away from WPMU DEV plugins).

I hope you understand where we (as clients) are coming from and truly hope for bug fix soon.

I did not see an update for the plugin @wpmudev-support9, had it been fixed?

Same problem here:

Deprecated: Unparenthesizeda ? b : c ? d : eis deprecated. Use either(a ? b : c) ? d : eora ? b : (c ? d : e)in /Users/ronaldt/Sites/debugging.test/wp-content/plugins/groups/lib/wp/class-groups-wordpress.php on line 81

and

Deprecated: Unparenthesizeda ? b : c ? d : eis deprecated. Use either(a ? b : c) ? d : eora ? b : (c ? d : e)in /Users/ronaldt/Sites/debugging.test/wp-content/plugins/groups/lib/access/class-groups-access-meta-boxes.php on line 295

The fix is quite easy @proaktion, like @evdheuvel mentioned:

Change groups/lib/access/class-groups-access-meta-boxes.php on line 295 to:
$post_id = !empty( $postarr['ID'] ) ? $postarr['ID'] : (!empty( $postarr['post_ID'] ) ? $postarr['post_ID'] : null);

And change groups/lib/wp/class-groups-wordpress.php on line 81 to:
$user_id = isset( $user->ID ) ? $user->ID : (isset( $args[1] ) ? $args[1] : 0);

There might be more occurrences throughout the plugin though.

• This reply was modified 4 years, 6 months ago by Ronaldt.

Hi @wpmudev-support7

What is the ETA on this?
Is there anything we can do to speed up the process?

Because of this bug our client is doing a lot of manual work, they’re getting restless and I completely understand that.

I hope to get a clear answer.
Thanks!

Why is this ticket marked as resolved? We’re up-to-date with the plugin and we have the same problem.
“Name” and “email” are quite the common fields to use in a form, I would say.

https://res.cloudinary.com/comsi-rtv/image/upload/v1586848026/Forminator/dom-duplicate-id-form.png

https://res.cloudinary.com/comsi-rtv/image/upload/v1586848027/Forminator/dom-duplicate-id.png

Hi @khaxan,

Thanks a lot, it was actually a CPT plugin that used a filter to modify the permalinks and did not add the trailing /. We now add it and both the sitemap and canonical links are working as expected.

Thanks again,
Ronald

Zelfde probleem hier.

Ik neem per e-mail contact op via het mailadres dat @postnl aangeeft, hoop dat zij de correcte API rechten kunnen koppelen (neem aan dat dit het probleem is).

Misschien een tip voor de plugin om de foutmelding duidelijker te maken, óf de foutmelding ergens te documenteren? Dit is erg onduidelijk.

Groeten,
Ronald

Hi @aweissinpsyde

That’s new for me. Should I export the language there as .po and .mo, then manually rename them to mollie-payments-for-woocommerce-nl_NL.<mo|po> and place them in /wp-content/languages?
If I place them in the plugin /i18n/languages/ directory that will be overwritten with each plugin update…

Or is there some automated process I’m missing?

Yes, works as expected now. Thanks!

I was wondering if some progress was made?