• If stuck in a catch 22:

    I run qtranslate x in a subsite on a multisite (okay, should have removed it much earlier, I know). The frontend does work, but backend causes white screen. So I had to manually remove qtranslate x from the plugin-folder. Now the subsite is working again and backend could be entered, qtranslate-?wpml-importer could be installed but then on the importer settings you read this:
    “Please save the qTranslate settings to the database first. Go to Languages Tab of Qtranslate settings Edit the languages that are active & enabled and update their names to something, save and revert back.”

    Is there a way to bypass this requirement, as qtranslate x no longer works in the backend?

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘can not save qtranslate settings – therefore can not import’ is closed to new replies.