Delete abandoned projects
hass - December 24, 2007 - 17:11
| Project: | Localization server |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Description
I cannot delete an abandoned projects. :-)
I could do myself on DB level, but it think this is something we might need... something like a delete button anywhere!? But strings used somewhere else should be kept...
#1
(2 Gábor) the given code will be correct?
<?php
// 1. XXX - ID versions of the module
DELETE cr, cf, cl
FROM `l10n_community_release` cr
LEFT JOIN `l10n_community_file` cf ON cr.rid = cf.rid
LEFT JOIN `l10n_community_line` cl ON cf.fid = cl.fid
WHERE cr.rid = XXX
....
// 2. Always :)
DELETE *
FROM `l10n_community_error`
// 3. Always it is not changeable
// l10n_community_translation and l10n_community_string
?>
Attach: the Localization server scheme of data.
#2
I think, this SQL(DELETE....) it is necessary to do everyone automatically if the file is not found. If we do "local scanning".
#3
With advances in http://drupal.org/node/321637 as well as this attached patch, we can finally consider this issue fixed. Thanks for the SQL sample pvasili.
The attached patch does the following:
- Adds user interface to control enabled/disabled state for projects.
- Adds user interface and API to "start over" with projects. This is basically the above suggested query with some tweaks, existing strings are kept for rescanning of the source.
- Adds user interface and API to completely remove a project. This also cleans up orphan strings and their translations, such as those resulting from the previous step.
- Adds user interface and API to just clean up orphaned source strings and their translations.
These all should help in maintenance and development testing of the module. I hope disabling will be enough of a control on stable sites to "abandon" projects, keeping existing work. However, deleting is now also an option.
#4
Are we able to delete specific versions with this patch? For example drop all 4.7.x versions or only 4.7-1.2, but not the complete project translations? I'm also thinking about the interface going to me overloaded with this version stuff. I remember we have had Drupal 6.0, 6.1, 6.2, 6.3, etc in the German server... I think it would be sometimes enough to care about the last version only... :-)
#5
No, it is not yet possible to remove releases, but it is on the plan. From the code, this can be easily derived. I plan on providing a release listing page for each project, where you could actually remove releases you pick.
#6
Sounds good.
--project followup subject--
Automatically closed -- issue fixed for two weeks with no activity.
#7
Automatically closed -- issue fixed for two weeks with no activity.