Deleting translatepress causes my plugins to malfunction

@cristiandraghia

@cozmoslabs

• This reply was modified 1 year, 6 months ago by chiefdeveloper.

Hello there,

Thank you for reaching us!

If you followed this guide on how you can delete plugin data and translations,then this problems should not appear:https://translatepress.com/docs/developers/delete-all-translations-and-plugin-data/

If not, try to follow this and see how it goes.

Also, our plugin is not supposed to do any damage to your website when you delete it from your website as the site should work as expected without TranslatePress too.

Let me know about this!

Kind Regards.

Dear that is the guide I followed, But then it leads all my plugins and OAuth to stop working. I am guessing deleting translate press might be affecting my permalinks or website url in a way. But I cant tell.

Dear @anghelemanuel99,

Any updates regarding this? This is slowing down my customer base.

@cristiandraghia

@cozmoslabs

@anghelemanuel99,

Please, I need assistance with this issue ASAP.

Hello there,

Can you give us detailed examples of what’s happening with screenshots regarding the problem that you have? We’re not excluding TP from causing this, but it seams unlikely it should cause issues with the default language.

I`m asking this because we need to check what is really happening and how the issue appears on your side.

Like this, we can spot the problem and see what we can do about it!

Also, TranslatePress does not modify the home_url for the default language, only in secondary languages. Can you please send us a screenshot of the TranslatePress settings page as well?

Let me know!

Kind Regards,

Deleting translatepress causes this error to appear in one of my payment gateway plugins

Notice: Undefined property: WC_fastpay::$redirect_page_id in /home/agoradeng/public_html/wp-content/plugins/fastpay_woocommerce/index.php on line 57

I checked the error and it is a redirect to my success-page, it uses site permalinks on wordpress to get the URL or the page id, for some reason it gets undefined. It works perfectly when translatepress is on. Once it is deactivated that plugin loses all its settings and the redirects become undefined.

I also tried deleting translatepress data from the database, as well as the plugin’s, and do everything from scratch, but the error persists.

I sadly cant share code nor screenshots from the plugin code, as this will violate our agreement with them

Hi,

In the plugin fastpay_woocommerce how is the redirect configured? Does it point to a language parameter?

The thing is, if TP is deactivated, it’s not really responsible for that error. And most likely the redirect is configured incorrectly. It’s possible it was configured with TP active and stored the incorrect URL or home_url.

In which case you will need to reconfigure that plugin with TP deactivated. I don’t see a workaround for this.

Did you had the setting “Use a subdirectory for the default language” set to Yes in the TranslatePress settings? That setting will change the home_url even in the default language.

Aside from choosing CKB as the default language, I have not changed the settings at all. they stayed as the were.

I pretty much assumed the same conclusion you made, the issue is, I tried reconfiguring the plugin and changing all the redirection pages once more, I even changed them in my merchant panel provided by the plugin authors. But nothing worked.

The plugin uses get_site_url() or get_permalink() to get the redirect page url from its ID.

What was the order in which you made these configurations initially?

Did you install and configure:
* Translatepress first
* The payment processor second?

If so, it’s possible this issue was happening even without having TranslatePress installed. And due to some of the changes we’re doing inside WordPress to better work with URL’s and make multilingual possible it actually fixes this?

The one function I can think of that might cause this is that we’re filtering home_url. We don’t touch site_url.

Try to go to translatepress-multilingual/class-translate-press.php and comment out this line:

$this->loader->add_filter( ‘home_url’, $this->url_converter, ‘add_language_to_home_url’, 1, 4 );

Then see if the error is appearing. If it is, it should narrow down the issue.

Another thing to check is to connect to your database using something like PhpMyAdmin and see what’s inside wp_options -> site_url and home_url.

The ones you see in the WordPress -> General Settings page can be filtered and incorrect.

Finally, clear and disable all and every caching you have. I see you have cloudflair in front if I’m not mistaken. Disable all caching in cloudflair temporarely when investigating this issue.

And please ask for support from FastPay, having TranslatePress disabled causing it to fail sounds like something they should be able to investigate properly and see WHY reconfiguring the plugin is causing it to fail as this is not an issue of TranslatePress.

Thank you for the detailed response, I have set a meeting with them today.

Sorry it took us a while to get back to you. We try to get back to users on the free version as fast as possible, but at times delays do happen.

Please let us know if it’s anything else we can help with.

And if possible, please update your 1 start review. It looks more like a weird setup issue with your payment processor then anything else.

Best Regards!

@sareiodata

I got an error by commenting the line you mentioned

$this->loader->add_filter( ‘home_url’, $this->url_converter, ‘add_language_to_home_url’, 1, 4 );

Parse error: syntax error, unexpected ‘url_converter’ (T_STRING), expecting function (T_FUNCTION) or const (T_CONST) in /home/agoradeng/public_html/wp-content/plugins/translatepress-multilingual/class-translate-press.php on line 19

Hi,

An error at that line makes no sense. It’s possible you typed by accident in your file url_converter when you searched for it. By pressing Ctrl+V perhaps?

Please overwrite the entire file the the original by re-downloading the plugin from wp.org and then try again.

No dear,

I merely commented the line, the editor will not let me save if there is a syntax error.