Functional problems in new version wordpress

Hello @arielloscerbo,

Tested in WordPress 5.5.3. No problems found. Can you provide more details?

Thanks

@loyaltymanufaktur Is it wokring in wordprss 5.6 and will it export and include custom fields such as custom fields from ACF?

@alriksson yes

@loyaltymanufaktur I do have sme feedback like dont export user_login and user_password. For no reason this is needed to successfully export and import.

Otherwise it seems to work great! It’s a simple bug great plugins just would prefer some fixes.

Not sure if it’s 100% compatible with wpml as if a page has the same name in multiple languages how does it detect which one to import? Slug can be the same but the url will nto exmaple.com/en/slug/ which other is example.com/slug/ do you detect the difference and if they have the same page name?

Search & override articles that have the same name or slug.
Name or slug could also change maybe option to use ID also which also could change for sure. Please confirm WPML support.

Maybe a last confirmiation once you have detected same name or slug etc? “do you want to replace with this one?” and give a popup screen with the link to the post-edit and frontend url. That would make it more confortible it detected the correct one. And see maybe diff-checker to show what is changed for users who want?

Then in settings you can enable or disable double check, diff-checker etc. I agree slug is a good way to detect same as they should not or are rare to change.

Waiting with the 4 or 5 star for a bit ??

• This reply was modified 4 years, 2 months ago by Rookie.
• This reply was modified 4 years, 2 months ago by Rookie.
• This reply was modified 4 years, 2 months ago by Rookie.
• This reply was modified 4 years, 2 months ago by Rookie.
• This reply was modified 4 years, 2 months ago by Rookie.
• This reply was modified 4 years, 2 months ago by Rookie.
• This reply was modified 4 years, 2 months ago by Rookie.

Hello @alriksson,

if WPML uses the same slug (post_name) in different translations – then the plugin won’t work as expected and will replace the first found post with the same slug.

Your idea of asking the user to select posts to be replaced is really good but it won’t be implemented so fast. But with the next release, it may come.

Thanks!

if WPML uses the same slug (post_name) in different translations – then the plugin won’t work as expected and will replace the first found post with the same slug.

Ok problem. Yes if users pick to use so which I do. As it’s not used as language it’s used as market.

Could you consider supporting wpml?

Until then if it adds complexity right now maybe work around to allow to be on the specific page edit and open zippy and that would trigger replace for the specific page if slug match? That way I could work around.

Your idea of asking the user to select posts to be replaced is really good but it won’t be implemented so fast. But with the next release, it may come

That would be amazing. What’s up for next release and when hehe. Maybe to support single at page replacement as mentioned above? ??