broke our website

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.

Hello

Thank you for your quick answer

Our website is https://www.rcinet.ca/

We are trying to fix it currently

This is what is displayed:
Note that the website may appear OK – it is cached with akamai
just add a ? with any characters after to bypass the cache

<?php
/**
* Front to the WordPress application. This file doesn’t do anything, but loads
* wp-blog-header.php which does and tells WordPress to load the theme.
*
* @package WordPress
*/

/**
* Tells WordPress to load the WordPress theme and output it.
*
* @var bool
*/
define( ‘WP_USE_THEMES’, true );

/** Loads the WordPress Environment and Template */
require( dirname( __FILE__ ) . ‘/wp-blog-header.php’ );

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

Thank you again.

Yes, it does not seems like something that a plugin could cause.

Our devop is looking at the error log at this time.

The apache service is being restarted…

It is very strange.

We’ll keep you informed.

Regards.

Hello again.

It appears that the plugin was not the cause, just the trigger.
And more precisely, the trigger appears to have been the lengthening of the post_name column in the database.

It made visible a pre-existing weakness.

Thank you again for your help.

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

Glad to know that the plugin was not the cause.

Thank you very much for the update.

Hello again!

After further analysis, it appears the plugin was indeed the source of the problem.

For an unknown reason, the line 101 in longer-permalinks.php:

$sql="INSERT INTO {$wpdb->prefix}postmeta (post_id, meta_key, meta_value) SELECT ID, 'longer-permalinks-post-name-longer', {$wpdb->prefix}posts.post_name FROM {$wpdb->prefix}posts";

created about 13 million lines in each wp_X_postmeta tables, X being the site id for two of our sites for which the plugin was activated, so more than a hundred times for each post_id

Combined with this WordPress bug meta_form performs a potentially expensive query, our MySQL server choked, which made our apache web service choke.

We erased all lines with “longer-permalinks-post-name-longer” meta_key and it fixed our problem.

Regards.

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.

Hello,

Yes, that is what it is supposed to do, but it created many copies for each post.

For example, for one of our sites, the posts table has 78385 entries.
So it should have created, at most, 78385 entries in the postmeta table.

In fact the plugin added 132 lines into postmeta table for each entry of the posts table, for a total of more than 10 million new entries.

Regards.

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

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.

Hello

Yes we were using the latest version of the plugin.

It was a first install, we never used it before, and so it was not an update.

Regards.

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.

Thank you !

We will test it and get back to you with our feedback.

Regards.

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.

Hello

We did not have time to test yet.

We’ll get back to you.

Regards.