You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a script to replace URL:s when copying my database from development to staging and production. The script does a "wp search replace" and works fine when qtranslate-xt is deactivated but does not work when the plugin is active.
There is a warning when the plugin is active:
Notice: Undefined index: wp-path in .../wp-content/plugins/qtranslate-xt-master/qtranslate_core.php on line 445
I just tried to blindly remove that line from the condition - without really knowing what I did :-). The warning disappears, but the problem remains, so that is not a solution.
This could be related to the issue #766 (just an idea).
The text was updated successfully, but these errors were encountered:
More info: In fact I think the problem HAS to do with the stuff around line 445, since there you check if there is a language indicator in the URL. I changed the language settings for the plugin and ticked the "Hide URL language info for default language", and with that things work as they should! So I guess it has something to do with language info (of course) not being passed when using WP-CLI.
Hey, many thanks for these investigations, this can be very useful to understand the problem! I must say i dislike url_info quite a lot, it's been a source of many problems. I'm refactoring code around it to make it simpler but there is still a lot to do.
It is very likely related to #766 but i'll try to give a look soon!
I use a script to replace URL:s when copying my database from development to staging and production. The script does a "wp search replace" and works fine when qtranslate-xt is deactivated but does not work when the plugin is active.
There is a warning when the plugin is active:
Notice: Undefined index: wp-path in .../wp-content/plugins/qtranslate-xt-master/qtranslate_core.php on line 445
I just tried to blindly remove that line from the condition - without really knowing what I did :-). The warning disappears, but the problem remains, so that is not a solution.
This could be related to the issue #766 (just an idea).
The text was updated successfully, but these errors were encountered: