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

Languages management problems #102

Closed
herrvigg opened this issue Jun 21, 2018 · 7 comments
Closed

Languages management problems #102

herrvigg opened this issue Jun 21, 2018 · 7 comments
Labels
legacy issue Legacy issue imported from original repo

Comments

@herrvigg
Copy link
Collaborator

herrvigg commented Jun 21, 2018

Issue by pedro-mendonca
Thursday Mar 26, 2015 at 11:45 GMT
Originally opened as qTranslate-Team/qtranslate-x#102


qTranslate version 3.2.9.2

I've spotted some issues with the list of languages.

  1. Deleting a manually added language won't deactivate it and it keeps listed in Default Language / Order and in dropdown list without any name or flag. I have to readd it, then deactivate it and finally delete it.

  2. Editing Language Code in a pre-defined language will create a duplicate in the list that automatically substitutes the pre-activated with this new duplicate with new Language Code. This duplicate issue won't happen if editing Language Code of manually added languages.

@herrvigg herrvigg added the legacy issue Legacy issue imported from original repo label Jun 21, 2018
@herrvigg herrvigg added legacy PR Legacy PR imported from original repo and removed legacy issue Legacy issue imported from original repo labels Jun 22, 2018
@herrvigg herrvigg changed the title Always show post content switch Languages management problems Jun 23, 2018
@herrvigg herrvigg reopened this Jun 23, 2018
@herrvigg herrvigg added legacy issue Legacy issue imported from original repo and removed legacy PR Legacy PR imported from original repo labels Jun 23, 2018
@herrvigg
Copy link
Collaborator Author

Comment by johnclause
Friday Mar 27, 2015 at 22:14 GMT


  1. is fixed on 3.2.9.4
  2. this is probably by design. If you change code of a manually added language, then there is no reason to keep the language with previous code, since if a new language wanted, then it can be added as new instead of replacing language code of existent language. Am I missing something?

@herrvigg
Copy link
Collaborator Author

Comment by pedro-mendonca
Friday Mar 27, 2015 at 22:28 GMT


  1. is fixed on 3.2.9.4

Great.

  1. The correct behaviour is what's happening with the manually added languages of course, no duplicate is created.
    This usually won't even be an issue because no one will want to change this, but I was messing around with the codes to invesigate the issue Language Codes conflicting qTranslate-Team/qtranslate-x#104 and found this possibility.
    The incorrect behaviour that I've issued as bug is what's happening with predefined languages, the duplicate creation and all the confusion it creates because there is no easy way to spot the differences between the two listed languages if you just change the Language Code.

@herrvigg
Copy link
Collaborator Author

Comment by johnclause
Saturday Mar 28, 2015 at 03:50 GMT


pre-defined language cannot be deleted and code cannot be modified on them, that is why it creates a new language instead.

I added column 'Code' (3.2.9.5, the latest master) so that one can distinct otherwise indistinctable items. I guess this is the best that can be done without a major re-design.

@herrvigg
Copy link
Collaborator Author

Comment by pedro-mendonca
Monday Mar 30, 2015 at 10:11 GMT


Looks fine and usefull. 👍

@herrvigg
Copy link
Collaborator Author

Comment by pedro-mendonca
Monday Mar 30, 2015 at 10:47 GMT


Deleting added languages already disables them and remove them from the top order list.

@herrvigg
Copy link
Collaborator Author

Comment by pedro-mendonca
Monday Mar 30, 2015 at 10:49 GMT


About de duplicate creation, I'm not sure if it should necessarly happen, because it works from the loaded database and not from the files. In the end this is not so important so I'm closing the issue as the main 1) problem is solved.

@herrvigg
Copy link
Collaborator Author

Comment by johnclause
Monday Mar 30, 2015 at 15:46 GMT


because it works from the loaded database
It now reads both and merge. This fixes the problem, when newly added pre-defined languages would not show up. Also it keeps database cleaner, since it stores only modified or added languages. The majority of people never modify any language and database stays free from unnecessary values. It also helps to speed up the load a little bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy issue Legacy issue imported from original repo
Projects
None yet
Development

No branches or pull requests

1 participant