retrovertigo

Hi @aqibkhan9,

Sorry that I missed your previous message. I tested a few things again, but could not replicate the warning either any more. When I saw it, I thought that due to file name and line number it would be something very simple, so I didn’t include any more details.

I will close this ticket. In case I do come across that message again, I will let you know and add details and steps to replicate.

Best,
Albert

@aqibkhan9 appologise, I mistyped. The WP version is 6.7.1 not 4.x

• This reply was modified 3 months, 2 weeks ago by retrovertigo.

Thanks for sharing @mbrsolution!

Same here, but I wouldn’t hold my breath waiting for a reply from the developers. It seems like the last time they reacted to any comments here on wp.org were 15 months ago.

39 unanswered support requests and 19 new reviews since the last time someone from FB reacted to any of them.

This is a pretty bleak track record for a company of that size.

Works fine for me.

• WordPress 6.6.1
• Gravity Form 2.8.16
• GF BED 1.0.2

Maybe a conflict with another plugin?

• This reply was modified 7 months, 1 week ago by retrovertigo. Reason: Add debug question

Thanks furqanfazal! ??

Potential direction(s) for a fix (including a little discussion about the rational behind this deprecation in the comments)

• https://stackoverflow.com/a/74879495/472804 (Answer recommended by PHP Collective)
• https://stackoverflow.com/a/75039639/472804

• This reply was modified 1 year, 5 months ago by retrovertigo. Reason: add second link

Thank you!

Hey Maciej,

This seems to work!

Thanks lots for this super quick reply and publishing of a fix.

Best regards

Done.
https://core.trac.www.ads-software.com/ticket/58292

@t-p that helped! Thanks ??

Hey Michael,

Thanks for your reply.
Someone from MLP got back to me with the following instructions:

Please navigate to My Sites → Network Admin → Sites for each of your sites.
In the tab Post Type Slugs fill in the custom post type slug for your particular custom post type (the rewrite slug you set up during post type registration).
This feature allows you to set up a different translated slug for each post type on every site.
You can find more information about this subject in our documentation:
https://multilingualpress.org/docs/how-to-translate-custom-post-types-and-taxonomies/#Enter-Post-Type-slug-value-on-each-site

That worked and https://domain.com/meet-our-team/john-doe is keeping its /john-doe ??

Hey Michael,
Thanks for getting back to me so quickly. Indeed I overlooked the simple test of switching MLP off – it fixes the permalink for the post in the CPT ‘team’. It fixes it right away, without updating the permalinks by re-saving, so it must be changing something on-the-fly.
Testing the permalink https://domain.com/meet-our-team/team-a where team-a is a ‘standard’ WP page, the permalink is correct, though, with MLP and CPTUI switched on.
Therefore I can only assume the CPTUI might be doing something that MLP is not expecting!? I sent them a message and will get back to you in case something of interest comes up.
Feel free to close this ticket, if you want to.
Thanks for a great plugin.

@mrodwin I might not be able to properly test this as it only happened on a production site and not on local or staging, where the setups are slightly different and hard to fully replicate.

Hi Gerard!

Thanks for the quick answer.

> I don’t think this is related to Enable Media Replace, because the -X suffixes are added by WordPress upon uploading an image with the same filename.

Good to know.

> Just to make sure, can you please deactivate all plugins except Enable Media Replace and try to reproduce the issue?

Fair enough. This will take a while, but will let you know in case I find something useful.

All the best!