Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full Uninstalling qtranslate x #200

Open
RattleSneyk opened this issue Jul 22, 2015 · 5 comments
Open

Full Uninstalling qtranslate x #200

RattleSneyk opened this issue Jul 22, 2015 · 5 comments
Labels

Comments

@RattleSneyk
Copy link

How to completely remove it?

@johnclause
Copy link
Member

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
Copy link

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
Copy link

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
#200 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ4SUW2LJnv-Cpc_EF7CmdjJEIQpHIwGks5qrGxSgaJpZM4FdbkN
.

@bielu
Copy link

bielu commented Jul 9, 2017

@ephestione
Copy link

"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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants