search

qTranslate-Team / qtranslate-x

Wordpress plugin: Adds user-friendly and database-friendly multilingual content management and translation support.
http://qtranslatexteam.wordpress.com/about/
GNU General Public License v3.0
205 stars 149 forks source link

Full Uninstalling qtranslate x #200

Open RattleSneyk opened 9 years ago

RattleSneyk commented 9 years ago

How to completely remove it?

johnclause commented 9 years ago

This is not yet implemented, as it is mentioned in https://qtranslatexteam.wordpress.com/startup-guide/ This is a free community project, If you are PHP fuent, could you implement it? Submit pull request then.

What do you plan to use instead, by the way, and why do you need to remove it?

rafaelski commented 7 years ago

Well, it brokes my Salient plugin, so i need to remove it. Can someone just point which files i need to find and delete manually?

qtranslateteam commented 7 years ago

This is not a matter of deleting files, it is a matter of the database cleanup. Maybe it is easy enough to integrate Salient? Would you consider that?

On Sep 17, 2016 3:40 PM, "rafaelski" notifications@github.com wrote:

Well, it brokes my Salient plugin, so i need to remove it. Can someone just point which files i need to find and delete manually?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/qTranslate-Team/qtranslate-x/issues/200#issuecomment-247812464, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ4SUW2LJnv-Cpc_EF7CmdjJEIQpHIwGks5qrGxSgaJpZM4FdbkN .

bielu commented 7 years ago

If some one have similar problem I write short code for do this: https://l.facebook.com/l.php?u=https%3A%2F%2Fbitbucket.org%2Fbielu%2Fremove-qtranslate%2Fsrc&h=ATNqf-vGkONiJ6XgcoM9PqWKgwE-3Ge4DVY7dhT6B5_t9fp1BjNOz5KQSs98CfcEIRdREwxUmcR-PmNAoz9v_6tyRKXjFenygAenYJIFt7VJGILXNQ8CICcxWGvBPrqo9__zoIYX_kZrww :) It's using basic wordpress conf file :)

ephestione commented 6 years ago

"database cleanup" sounds like there will be just one language to be kept and all the others purged (which required anyway to be written, so a big portion of work and content will be lost). In my opinion, a wider approach would give the option to choose the primary language that will keep the post assignment, and also keeping all the other languages by creating more posts with just that language.

In my case, I came in this thread because of Gutenberg. I don't like having to rely on a "particular" extension to wordpress that could break so that my website would become unuseable, so I'd rather prefer to have the primary language be kept in the post, and another (o more) new posts made with the other languages in them.