Just curious if this issue has been actually “resolved?”
I’ve like to switch over to mqTranslate but all our websites use Qtranslate Slug and my boss is going to kill me if anything breaks. Many directory sites link back to us via specific links and it’s important we keep the structure.
To be clear, it was said we can modify qtranslate-slug.php by replacing line 261 with this:
return ( version_compare($wp_version, "3.3", "<" ) || (!is_plugin_active('qtranslate/qtranslate.php') && !is_plugin_active('mqtranslate/mqtranslate.php')) );
and adding this after line 678:
if ($GLOBALS['q_config']['url_mode'] == QT_URL_PATH)
$req_uri = preg_replace("/^{$GLOBALS['q_config']['language']}(\/|$)/", '', $req_uri);
Will my slugs work the same by doing this? Having read n4than’s post I’m assuming it’s no. ??
N4than, have you had any progress with this?
chsxf, I understand it’s not your responsibility to account for other plugins, but I have to admit this is an important feature! Like you said, it’s been long since there’s been any activity with Qtranslate Slug and I don’t foresee any in the near future… Like Dr. Phil says, “The best predictor of future behavior is past behaviour!”
That said, we’re at your mercy! ?? Do you foresee any of the following…
- Integrating seamless compatibility with Qtranslate Slug?
- Implementing a feature in mqTranslate that handles slugs?
- Perhaps creating a second child plugin, um you could call it “mqTranslateSlug”? ??
Just trying to get a grasp on whether or not I should continue looking in this direction as an alternate to Qtranslate as the slugs are an important factor to us!
Thanks! ??