antithesisgr

Dear @margroup,
I am glad everything worked out for you.

Since your last message here there further updates released that should also work fine as you wrote in your last message.

Thank you.

Dear @matthieulllrc,

as you might have seen, there is also a newer update (v 1.21) recently.
We assume your issue is correctly addressed using the latest version.

Thank you very much.

There is a new release today (version 1.21) handling related functionality.
Could you please give try the updated version?

Thank you.

Dear @alihoseiny let me ask you:
Are you on a network WordPress installation or on a single WordPress website installation?

Thank you.

Hi @alihoseiny, were you using an older plugin version before version 1.20?
Or was this a fresh install of the plugin?

For a quick fix: You can safely delete all those records with that value from wp_postmeta table (value “longer-permalinks-post-name-longer”) without a problem.

We cannot reproduce this problem but we are investigating the issue and will have news the soonest possible.

Thank you.

Hello Yiannis!

Can you please check which plugin version was running when this happened?
Was this on 1.17?

Thank you.

Dear @matthieulllrc thank you for your feedback.

Today we released a new version (1.20) that should handle correctly the situation you were in.

If you can do try it on your staging environment, your feedback is welcome.

Best regards.

Hi,
where you using the latest version of the plugin when this happened?
Where you running the plugin for a long time (previous versions) and where doing the updates?

Thank you.

Thank you very much for the extra info.

The plugin keeps existing long titles as a “backup” for you and this is what this sql query is doing. Because of the size of your database/site this was a long shot to end.

We are already working on a next update to remove the need for this query.

Best regards.

Glad to know that the plugin was not the cause.

Thank you very much for the update.

I see this (by entering a query string as you wrote).

This is the WordPress PHP code.
This should be executed (never displayed).

Having PHP code displayed in the browser (not executing) is definitely a problem in server configuration not related to the plugins and PHP code (since no PHP is executed at all to be code related).
Did you had any PHP error (see your php error log) before?

Thank you.

• This reply was modified 5 years, 1 month ago by antithesisgr.

Hello,
please can you provide more information?
What kind of errors do you get now (even after deactivation)?
How did this break your site when activated?

As of current version today, it should not bring any delays but only when first activated for a while.

Will be glad to help here.

Thank you.

Please try the latest version released today.

Thank you.

Hello,
after some tests, updating to latest WordPress version did not break anything: Longer permalinks are working on all old and new posts.

A question please: Were you on plugin version at least 1.15 BEFORE doing the WordPress update?

(Please see the “IMPORTANT” bullet in “Changelog” on version 1.15 here:
https://www.www.ads-software.com/plugins/longer-permalinks/#developers)

Thank you for your feedback.

Hello,
we plan to investigate (and fix) WP 5.3 update in the following days.
Please stay tuned.

Thank you.