- Development - lists.drupal.org

[drupal-devel] [feature] Enable customizing of "Title" field on node forms
by chx 20 May '05

20 May '05

Issue status update for http://drupal.org/node/10056 Project: Drupal Version: cvs Component: node system Category: feature requests Priority: normal Assigned to: Anonymous Reported by: Anonymous Updated by: chx Status: patch Patch still applies (yes, with some offset, but applies). ANd yes, we need this very badly. chx Previous comments: ------------------------------------------------------------------------ August 14, 2004 - 20:17 : Anonymous Attachment: http://drupal.org/files/issues/node.set-title-field.patch (2.02 KB) The default "title" field in a node object is useful but not always appropriate. For some node types it would be preferable to rename the field for display to users (e.g., from "title" to "name" for a record of an organization or business), while in others the title might be best drawn from a combination of other fields (e.g., first_name and last_name fields, for a record of an individual). This patch enables two new alternatives for node titles: renamingThe title field can be renamed, e.g., from "title" to "name". substutingOther fields can be substituted for the title field. The functionality is implemented through a new proposed node hook, _title_field($op). There are two possible values for $op: "action" (either "rename" or "substitute") and "names" (a list of field names to be used in the title field). Sample uses: [?PHP function example_title_field($node, $op) { switch ($op) { case 'action': $return = 'rename'; break; case 'names': $return = array('Name'); } return $return; } ?] In this case, since the requested action is "rename", the title field would be labelled "Name" (instead of "Title") in node add and edit forms for nodes of type "example". [?PHP function example_title_field($node, $op) { switch ($op) { case 'action': $return = 'substitute'; break; case 'names': $return = array('first_name', 'last_name'); } return $return; } ?] In this case, no "Title" field would be displayed in node add or node edit forms of node type "example". Instead, the fields "first_name" and "last_name" would be concatenated to form a title. Implementing this patch would significantly increase the flexibility of the node system, making it feasible to store information of many types not currently supported because they don't have a "title" attribute. ------------------------------------------------------------------------ August 15, 2004 - 18:39 : Dries This is best accomplished through the existing nodeapi hook, using a separate module. ------------------------------------------------------------------------ August 16, 2004 - 01:02 : nedjo Thanks for the suggestion. I did look for a way to accomplish this through _nodeapi (and other existing hooks), but couldn't see how. The "title" field is hard-coded into node.module. The _nodeapi hook allows various types of manipulations, but not, so far as I could see, changes to elements that have been generated by, e.g., form_textfield() calls. Are there possibilities I'm missing? Other approaches? Any specific suggestions as to means we could use to change the hard-coded "title" field? ------------------------------------------------------------------------ August 19, 2004 - 20:27 : nedjo Attachment: http://drupal.org/files/issues/node.set-title-field_0.patch (741 bytes) Drawing on Dries's suggestion, I've substantially revised this patch to enable node title field customization with only three additional lines of code in node.module. In place of the existing line in function node_form() <?php $output .= form_textfield(t('Title'), 'title', $edit->title, 60, 128, NULL, NULL, TRUE); ?> the patch substitutes a the following: <?php $title = variable_get('node_titlefield_'. $edit->type, 'Title'); if(!($title == 'none')) { $output .= form_textfield(t($title), 'title', $edit->title, 60, 128, NULL, NULL, TRUE); } ?> With this change in place, node modules will be able to override the standard node title label by setting a variable, node_titlefield_nodetype, where nodetype is the type of node. This could be done, e.g., in a _settings hook, so that the first time settings were accessed the module would set the variable: <?php if (variable_get('node_titlefield_example', '') == '') { // since none is already set, set this variable variable_set('node_titlefield_example', 'Name'); drupal_set_message('Example module initialization completed.'); } ?> The special value 'none' would suppress the title field altogether in node forms, used as follows: <?php if (variable_get('node_titlefield_example', '') == '') { // since none is already set, set this variable variable_set('node_titlefield_example', 'none'); drupal_set_message('Example module initialization completed.'); } ?> In this case, a _validate hook would be used to set the title field value. Assuming a module where a first name-last name combination was to be used for a title: <?php function example_validate(&$node) { if(!(isset($node->title))) { $node->title = $node->first_name . ' ' . node->last_name; } } ?> In short, this three-line addition to the node.module would significantly increase the flexibility of the node system by removing the hard-coded 'Title' field in node add and edit forms and instead enabling custom labelling or concatenation of the field from other sources. ------------------------------------------------------------------------ August 19, 2004 - 20:50 : moshe weitzman I like this functionality. But the implementation still seems unclean. I would prefer to simply remove the 'title' form field from node_form() and require that modules present this field in whatever way they please. in some cases, they will use a hidden form field because no customer interaction is required. This causes a break with backward compatibility, but cleanliness is facored over compatibilityness (when you must choose). I'm moving this back to 'Active', since I don't think this patch is committable as is. ------------------------------------------------------------------------ August 28, 2004 - 01:46 : nedjo Attachment: http://drupal.org/files/issues/node.set-title-field_1.patch (830 bytes) Thanks for looking at this. The suggestion - dropping the title field altogether and leaving this for module authors - has the advantage of simplicity. However, this change would imply significant new work as it would would require all or nearly all existing modules - core and contributed - be modified. While I think enabling title field customization is important for Drupal as a whole, and while this is a change I need for two modules I'm working on, I'm not immediately convinced that the benefits of this change justify this cost. Also, in most cases, the present title field works fine, so keeping it as a default option would I feel be desirable. Hence the following patch. In place of my (poorly conceived) initial hook proposals, above, this patch introduces a single very straightforward new node hook, _title_field. By setting this hook to return FALSE, node modules authors will suppress the default title field, and be free therefore to substitute what they wish or need. Returning TRUE, or not using the hook, will result in the default title field being used. Sample usage: <?php function example_title_field() { return FALSE; } ?> This is, I feel, a much better solution than the previous two I suggested--proof, if it's true, that the Drupal issue system works! ------------------------------------------------------------------------ September 6, 2004 - 17:50 : nedjo Are there any objections to or issues raised by this small patch (introducing a new hook to make the title field optional in node forms)? If not, can it be applied? ------------------------------------------------------------------------ September 7, 2004 - 15:46 : Anonymous I think I agree with Moshe's opinion that this should be accomplished by having node modules display the title field. In any event, this is a new feature and shouldn't go in during the feature freeze for 4.5. ------------------------------------------------------------------------ September 7, 2004 - 15:58 : ccourtne +1 for just moving the title field to be a responsibility of the implementing module instead of node_form. There is already to some extent "hook overload", in addition there may be several modules which don't want to even display a title module. Why add that only fixes some of the problems just to have to remove it later when you make a fix that address the whole problem. ------------------------------------------------------------------------ September 7, 2004 - 23:09 : nedjo Attachment: http://drupal.org/files/issues/node.remove-title-field.patch (636 bytes) Thanks for comments. As per feedback, the attached patch removes the title field from node forms, leaving this instead to node modules. Understood that possible approval of this patch this will need to wait until code unfrozen. ------------------------------------------------------------------------ October 24, 2004 - 14:06 : moshe weitzman please patch all core node modules as well. ------------------------------------------------------------------------ November 28, 2004 - 03:00 : nedjo Attachment: http://drupal.org/files/issues/node-move-form-title-field.patch (4.29 KB) Good point Moshe. This patch of node.module plus all core node modules simply moves the title field out of node.module and into the node modules, enabling (if desired) customization of the title field by a module. Patches to contributed modules will in most cases be as simple as adding the line <?php $output = form_textfield(t('Subject'), 'title', $node->title, 60, 128, NULL, NULL, TRUE); ?> at the beginning of a typename_form() function (and, if necessary changing an existing $output = to $output .=). In the attached patch, I've customized the title field for only one of the node types, calling the title of a forum topic the "Subject". We could consider calling the title of a blog a "Subject" or "Topic" as well. I feel this is a good solution (thanks for the feedback and discussion) and, for minimal work (minor updates to contributed modules), will have the significant benefit of enabling flexibility in content types beyond those that have "title" attributes. ------------------------------------------------------------------------ November 28, 2004 - 19:45 : nedjo Ability to customize title as provided in this patch was requested here [1]: "When adding/editing, the 'title' field is manditory, which is fine. Except that its label is hardcoded to 'title'. A custom node modelling, say, a 'Company' would much rather this field be presented to the user as 'Company Name'. " [1] http://drupal.org/node/13596 ------------------------------------------------------------------------ March 4, 2005 - 05:44 : nedjo Here's another patch that's sat for months without being either applied or turned down, although there was expressed support and, after several iterations, it addressed all issues that had been raised. The point is to remove the hard-coded "Title" field - inapprioriate for many node types, e.g., companies - from node forms, instead allowing node modules to treat this as appropriate (e.g., a "Subject", "Name" or "Topic", or nothing at all). Are there problems with this approach that were not raised? Is there a reason this wasn't accepted? ------------------------------------------------------------------------ March 4, 2005 - 05:54 : Steven nedjo: if you read the backlog you can see that this feature was delayed for after the 4.6 release. "I've customized the title field for only one of the node types, calling the title of a forum topic the "Subject". " This is really inconsistent, as what you call the title of a blog, story or forum node is purely subjective. "Subject" "Topic" and "Title" are pretty much interchageable and any subtle differences will surely be eroded by translation. The only thing I can agree on so far is naming a polls' title "Question". ------------------------------------------------------------------------ March 4, 2005 - 07:15 : nedjo Thanks for the note. I'm not sure what you mean by the "backlog". Where would I find this? I agree that a "Question" field would make sense for polls. ------------------------------------------------------------------------ March 4, 2005 - 16:12 : JonBob Actually UnConeD, it was postponed until after the 4.5 release, not 4.6, and looks like everyone forgot about it when the release happened. And no, Nedjo, I don't take this as proof that Drupal needs more bureaucracy. :-) Marking this active again; I'm sure the patch will have to be updated once the code branches. We had rolled this function into the needs for CCK, but in our discussions split it off again. ------------------------------------------------------------------------ April 3, 2005 - 07:28 : chx Attachment: http://drupal.org/files/issues/node-move-form-title-field_0.patch (4.59 KB) The patch applies to ucrrent HEAD with some offset. I have rerolled it so it applies cleanly.

1 0

Re: [drupal-devel] creating drupal-doc teams
by Kobus Myburgh 20 May '05

20 May '05

Charlie, I am interested in this section - it is part of my current 4th year studies in Human Computer Interaction. > * Initiatives for improving the collaborative book and other technological solutions to improve Drupal documentation usability, integration, and creation. I can also help out with: > * Restructuring/reorganizing each of the new handbook sections as defined on the V2 page: Regards, Kobus

1 0

Re: [drupal-devel] creating drupal-doc teams
by Kobus Myburgh 20 May '05

20 May '05

Charlie, If there is a place where I can be involved, please let me know. I am not very big on the coding, so this is a good area for me to get involved in. Regards, Kobus >>> cel4145(a)cyberdash.com 5/20/2005 12:02 AM >>> Currently, it seems we have lots of interest in taking Drupal documentation in new and interesting directions. To facilitate this, I'd like to see if we can't form some documentation teams. Much like I asked if Djun and Bryan would be in charge of reorganizing the About section of the handbook, I'd like us to form other two person teams for any major area that we have expressed interest in developing. Here are just a few examples of some areas I could imagine Documentation teams for * Restructuring/reorganizing each of the new handbook sections as defined on the V2 page: http://drupal.org/handbook/v2 For example, the About the handbook section. We need a couple of people to be in charge of our authoring guidelines and best practices for creating Drupal handbook documentation. (Anisa spearheaded the style guide revision; perhaps we could coax her and one other person to handle the About the handbook section?) * Best practices for configuring and building Druapl sites (Roland has already volunteered for this one :) Is there another?) * Initiatives for improving the collaborative book and other technological solutions to improve Drupal documentation usability, integration, and creation. (Djun has already been working on this. Perhaps he'd like to be one of the team members. We'd only need one other volunteer then.) * Marketing materials (Andre? You seem to have lots of marketing ideas :) * Etc. The documentation team would be responsible for most decisions regarding their project (in some cases there might be some overlap between other documentation teams, so they'd have to coordinate). Initially, I would hope that each documentation team would run a proposal by the drupal-docs list so that all of us could offer feedback in the construction of their individual project so that a good compromise of the important opposing interests (if any) can be reached. Otherwise, let us know when new documentation is posted (maybe this will be automated) so that we can offer feedback and suggestions. Or when the documentation team members are having trouble solving an issue between themselves, contact the list for assistance in resolution. In the case of any who volunteer for restructuring/revising the handbook sections, if they would like, they could also continue on as the offical book maintainers for those new books. If anyone has ideas for other documentation team areas, please respond to this post via the drupal-docs list. I've mentioned a few people here, but I'm sure there are a lot more. If anyone would like to volunteer to be a documentation team member for a specific project, feel free to post to the drupal-docs list or contact me privately. Once the documentation teams have been created, I'll create a page in the About handbook section so that people know who's in charge of individual projects. I hope this works well for everyone. Putting people in charge of specific areas seems to me the best way for us to get the things we want accomplished. Charlie

1 0

Re: [drupal-devel] Contact people for translations
by Kobus Myburgh 20 May '05

20 May '05

Kieran, Something else - if you need to speak to someone specifically who have done a translation, you can contact me - I'd be glad to help if I can. Regards, Kobus >>> kieran(a)civicspacelabs.org 5/20/2005 2:25 AM >>> Hi, we have been talking about how changes to admin help might effect translation efforts. I think we have some proposals on the docs list. Who should I speak with from the translation efforts to see if what we are proposing is reasonable? Thanks, Kieran

1 0

Re: [drupal-devel] Contact people for translations
by Kobus Myburgh 20 May '05

20 May '05

Kieran, You should speak to Gerhard (Killes), as far as I know, as he is the Translations co-ordinator. Regards, Kobus >>> kieran(a)civicspacelabs.org 5/20/2005 2:25 AM >>> Hi, we have been talking about how changes to admin help might effect translation efforts. I think we have some proposals on the docs list. Who should I speak with from the translation efforts to see if what we are proposing is reasonable? Thanks, Kieran

1 0

Re: [drupal-devel] creating drupal-doc teams
by Steven Peck 20 May '05

20 May '05

Doh.... teach me to pick to day to catch up on a month long backlog. Yes I am interested. I have some ideas for some more stuff in that direction as well. My current workload is killing me so I would love to help review other submissions as well. My method of configuring/setting up a Drupal site is not necessarily the best for all sites, so it would be good to have several differnet methods/suggestions for differnet scenerios/viewpoints. I also like the two person team lead type of idea. Less of a chance that there will be a gap when things like 'work projects suck up all your time.. -sp ________________________________ From: drupal-devel-bounces(a)drupal.org on behalf of Gerhard Killesreiter Sent: Thu 5/19/2005 3:48 PM To: drupal-devel(a)drupal.org Cc: drupal-docs(a)drupal.org Subject: Re: [drupal-devel] creating drupal-doc teams On Thu, 19 May 2005, Charlie Lowe wrote: > * Best practices for configuring and building Druapl sites > > (Roland has already volunteered for this one :) Is there another?) I can recommend Steven E Peck (sepeck). I don't know if he is on any of these lists. If he isn't, he can be reached through the contact module at drupal.org or #drupal. > * Initiatives for improving the collaborative book and other > technological solutions to improve Drupal documentation usability, > integration, and creation. > > (Djun has already been working on this. Perhaps he'd like to be one of > the team members. We'd only need one other volunteer then.) I might be able to help with this (depending on the direction of the ideas). Cheers, Gerhard

1 0

Re: [drupal-devel] [drupal-docs] creating drupal-doc teams
by Charlie Lowe 20 May '05

20 May '05

You are definitely right. I should clarify. Of course we can have more than two people working on each of these projects. But I'd like to have two people in charge of the project group. Perhaps they should be called "team leaders" :) Andrew Hoppin wrote: > Charlie, I'd love to help on marketing materials, though the next > couple of weeks are bad for me, and I'd love the team to be larger than > 2 if I were 1! :) > > Andrew > > **************************************** > Andrew Hoppin > 1.212.464.7665 (m) > andrew(a)civicspacelabs.org > **************************************** > > > On May 19, 2005, at 3:02 PM, Charlie Lowe wrote: > > >>Currently, it seems we have lots of interest in taking Drupal >>documentation in new and interesting directions. To facilitate this, >>I'd >>like to see if we can't form some documentation teams. Much like I >>asked >>if Djun and Bryan would be in charge of reorganizing the About section >>of the handbook, I'd like us to form other two person teams for any >>major area that we have expressed interest in developing. >> >>Here are just a few examples of some areas I could imagine >> >>Documentation teams for >> >>* Restructuring/reorganizing each of the new handbook sections as >>defined on the V2 page: >> >>http://drupal.org/handbook/v2 >> >>For example, the About the handbook section. We need a couple of people >>to be in charge of our authoring guidelines and best practices for >>creating Drupal handbook documentation. >> >>(Anisa spearheaded the style guide revision; perhaps we could coax her >>and one other person to handle the About the handbook section?) >> >>* Best practices for configuring and building Druapl sites >> >>(Roland has already volunteered for this one :) Is there another?) >> >>* Initiatives for improving the collaborative book and other >>technological solutions to improve Drupal documentation usability, >>integration, and creation. >> >>(Djun has already been working on this. Perhaps he'd like to be one of >>the team members. We'd only need one other volunteer then.) >> >>* Marketing materials >> >>(Andre? You seem to have lots of marketing ideas :) >> >>* Etc. >> >>The documentation team would be responsible for most decisions >>regarding >>their project (in some cases there might be some overlap between other >>documentation teams, so they'd have to coordinate). Initially, I would >>hope that each documentation team would run a proposal by the >>drupal-docs list so that all of us could offer feedback in the >>construction of their individual project so that a good compromise of >>the important opposing interests (if any) can be reached. >> >>Otherwise, let us know when new documentation is posted (maybe this >>will >>be automated) so that we can offer feedback and suggestions. Or when >>the >>documentation team members are having trouble solving an issue between >>themselves, contact the list for assistance in resolution. >> >>In the case of any who volunteer for restructuring/revising the >>handbook >>sections, if they would like, they could also continue on as the >>offical >>book maintainers for those new books. >> >>If anyone has ideas for other documentation team areas, please respond >>to this post via the drupal-docs list. I've mentioned a few people >>here, >>but I'm sure there are a lot more. If anyone would like to volunteer to >>be a documentation team member for a specific project, feel free to >>post >>to the drupal-docs list or contact me privately. >> >>Once the documentation teams have been created, I'll create a page in >>the About handbook section so that people know who's in charge of >>individual projects. >> >>I hope this works well for everyone. Putting people in charge of >>specific areas seems to me the best way for us to get the things we >>want >>accomplished. >> >>Charlie >>-- >>[ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ] > >

1 0

[drupal-devel] Bug#301394: marked as done ([INTL:pt_PT] Portuguese translation for drupal package)
by owner＠bugs.debian.org 19 May '05

19 May '05

Your message dated Thu, 19 May 2005 17:17:35 -0400 with message-id <E1DYsOd-0007wa-00(a)newraff.debian.org> and subject line Bug#301394: fixed in drupal 4.5.2-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 25 Mar 2005 16:22:49 +0000 >From elmig(a)debianpt.org Fri Mar 25 08:22:48 2005 Return-path: <elmig(a)debianpt.org> Received: from bl4-107-112.dsl.telepac.pt (elmig.net.dhis.org) [81.193.107.112] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1DEraC-0008JC-00; Fri, 25 Mar 2005 08:22:48 -0800 Received: (qmail 2832 invoked from network); 25 Mar 2005 16:22:49 -0000 Received: from unknown (HELO ?10.0.0.3?) (10.0.0.3) by 10.0.0.1 with SMTP; 25 Mar 2005 16:22:49 -0000 Message-ID: <42443A82.8050407(a)debianpt.org> Date: Fri, 25 Mar 2005 16:21:22 +0000 From: Miguel Figueiredo <elmig(a)debianpt.org> Organization: DebianPT.org User-Agent: Debian Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: submit(a)bugs.debian.org Subject: [INTL:pt_PT] Portuguese translation for drupal package Content-Type: multipart/mixed; boundary="------------000005010305060308080807" Delivered-To: submit(a)bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-2.3 required=4.0 tests=BAYES_44,HAS_PACKAGE, RCVD_IN_DSBL,REMOVE_REMOVAL_NEAR autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: This is a multi-part message in MIME format. --------------000005010305060308080807 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Package: drupal Version: 4.5.2 Severity: wishlist Tag: patch, l10n Here goes a Portuguese translation for the Drupal package. Feel free to use it. Best Regards, Miguel Figueiredo http://www.debianPT.org --------------000005010305060308080807 Content-Type: text/x-gettext-translation; name="pt.po" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="pt.po" # Portuguese translation od Drupal's debconf messages. # 2005, Miguel Figueiredo <elmig(a)debianpt.org> msgid "" msgstr "" "Project-Id-Version: drupal 4.5.2-1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2004-03-13 19:13+0100\n" "PO-Revision-Date: 2005-03-25 13:54+0000\n" "Last-Translator: Miguel Figueiredo <elmig(a)debianpt.org>>\n" "Language-Team: Portuguese <traduz(a)debianpt.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates.master:4 msgid "Automatically create Drupal database?" msgstr "Criar automaticamente a base de dados do Drupal?" #. Type: boolean #. Description #: ../templates.master:4 msgid "" "Drupal needs access to a database, along with initialized data structures in " "order to function properly. This can be created automatically by this " "package, for MySQL or PostgreSQL databases." msgstr "" "O Drupal necessita de aceder a uma base de dados, assim como a estruturas " "de dados inicializadas de modo a funcionar correctamente. Isto pode ser " "criado automaticamente por este pacote, para bases de dados MySQL ou " "PostgreSQL." #. Type: boolean #. Description #: ../templates.master:4 msgid "" "Automatically creating the database does not make sense if a Drupal database " "already exists or if no database server has been setup when Drupal is " "installed." msgstr "" "Criar automaticamente a base de dados não faz sentido se já existir uma " "base de dados do Drupal ou se não foi preparado nenhum servidor de bases " "de dados quando o Drupal foi instalado." #. Type: boolean #. Description #: ../templates.master:16 msgid "Run database update script?" msgstr "Correr o script de actualização da base de dados?" #. Type: boolean #. Description #: ../templates.master:16 msgid "" "If you are upgrading Drupal from an older upstream version, the database " "structure needs to be updated. This package can perform this task " "automatically." msgstr "" "Se estiver a actualizar o Drupal a partir de uma versão upstream mais " "antiga, a estrutura da base de dados necessita ser actualizada. Este " "pacote pode executar essa tarefa automaticamente." #. Type: boolean #. Description #: ../templates.master:16 msgid "The database will be backed up to prevent data loss." msgstr "A base de dados será salvaguardada para prevenir a perda de dados." #. Type: select #. Description #: ../templates.master:27 msgid "Database engine to be used with Drupal" msgstr "Motor da base de dados para ser utilizado com o Drupal" #. Type: string #. Description #: ../templates.master:32 msgid "Database server for Drupal's database" msgstr "Servidor de base de dados para a base de dados do Drupal" #. Type: string #. Description #: ../templates.master:37 msgid "Database server administrator user name on host ${host}" msgstr "Nome de utilizador do administrador do servidor de bases de dados " "no host ${host}" #. Type: password #. Description #: ../templates.master:42 msgid "Password for database server administrator ${user} on host ${host}" msgstr "Password do administrador ${user} do servidor de bases de dados " "no host ${host}" #. Type: password #. Description #: ../templates.master:42 msgid "The answer will not be stored anywhere permanently." msgstr "A resposta não será guardada em qualquer local de forma permanente." #. Type: string #. Description #: ../templates.master:48 msgid "Drupal database owner username" msgstr "Nome de utilizador do dono da base de dados do Drupal" #. Type: string #. Description #: ../templates.master:48 msgid "This username will be used by Drupal to connect to the database server." msgstr "Este nome de utilizador será utilizado pelo Drupal para se ligar " "ao servidor de bases de dados." #. Type: password #. Description #: ../templates.master:54 msgid "Drupal database owner password" msgstr "Password do dono da base de dados do Drupal" #. Type: password #. Description #: ../templates.master:54 msgid "If no password is specified here, a random password will be generated." msgstr "Se nenhuma password for especificada aqui, será gerada uma password " "aleatória." #. Type: string #. Description #: ../templates.master:61 msgid "Drupal database name" msgstr "Nome da base de dados do Drupal" #. Type: boolean #. Description #: ../templates.master:66 msgid "Remove Drupal database when the package is removed?" msgstr "Remover a base de dados do Drupal quando o pacote for removido?" #. Type: boolean #. Description #: ../templates.master:71 msgid "Remove former database backups when the package is removed?" msgstr "Remover backups antigos da base de dados quando o pacote for removido?" #. Type: boolean #. Description #: ../templates.master:71 msgid "" "These backups are stored in /var/lib/drupal/backups. This will not remove " "the current database from the DBMS." msgstr "" "Estes backups são guardados em /var/lib/drupal/backups. Isto não irá " "remover a base de dados actual do SGDB." #. Type: multiselect #. Description #: ../templates.master:79 msgid "Web server(s) that should be configured automatically" msgstr "Servidor(es) web que devem ser configurados automaticamente" #. Type: note #. Description #: ../templates.master:83 msgid "User creation failed" msgstr "A criação do utilizador falhou" #. Type: note #. Description #: ../templates.master:90 msgid "Attempt to modify config file ${conffile} failed" msgstr "Falhou a tentativa de modificar o ficheiro de configuração ${conffile}" #. Type: note #. Description #: ../templates.master:97 msgid "Database creation failed" msgstr "Falhou a criação da base de dados" #. Type: note #. Description #: ../templates.master:104 msgid "Database initialization failed" msgstr "Falhou a inicialização da base de dados" #. Type: note #. Description #: ../templates.master:111 msgid "Automatic database update failed" msgstr "Falhou a actualização automática da base de dados" #. Type: note #. Description #: ../templates.master:111 msgid "The automatic update script failed to update the database." msgstr "O script de actualização automática falhou a actualização da base de dados." #. Type: note #. Description #: ../templates.master:120 msgid "Automatic update script can not be run" msgstr "O script de actualização automática não pode ser corrido" #. Type: note #. Description #: ../templates.master:120 msgid "" "Configuration files of a Drupal package ${oldversion} have been found, but " "the package itself has been removed. Therefore, it is not possible to run " "the automatic update script." msgstr "" "Foram encontrados ficheiros de configuração de um pacote " "Drupal ${oldversion}, mas o pacote em si foi removido. Por isso, " "não é possível correr o script de actualização automática." #. Type: note #. Description #: ../templates.master:120 msgid "" "Please run it by hand after the package has been successfully installed. " "Either point your web browser to ${site_root}/update.php or run /usr/share/" "drupal/scripts/debian-update.php from a shell." msgstr "" "Por favor corra-o manualmente após o pacote ter sido instalado com " "sucesso. Ou aponte o seu browser web para ${site_root}/update.php ou " "corra a partir da shell /usr/share/drupal/scripts/debian-update.php." #. Type: note #. Description #: ../templates.master:132 msgid "Database removal failed" msgstr "Falhou a remoção da base de dados" #. Type: note #. Description #: ../templates.master:132 msgid "Script output:" msgstr "Saída do script:" #. Type: note #. Description #: ../templates.master:132 msgid "${result}" msgstr "${result}" --------------000005010305060308080807-- --------------------------------------- Received: (at 301394-close) by bugs.debian.org; 19 May 2005 21:20:27 +0000 >From katie(a)ftp-master.debian.org Thu May 19 14:20:26 2005 Return-path: <katie(a)ftp-master.debian.org> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DYsRO-0005rL-00; Thu, 19 May 2005 14:20:26 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1DYsOd-0007wa-00; Thu, 19 May 2005 17:17:35 -0400 From: Hilko Bengen <bengen(a)debian.org> To: 301394-close(a)bugs.debian.org X-Katie: $Revision: 1.55 $ Subject: Bug#301394: fixed in drupal 4.5.2-4 Message-Id: <E1DYsOd-0007wa-00(a)newraff.debian.org> Sender: Archive Administrator <katie(a)ftp-master.debian.org> Date: Thu, 19 May 2005 17:17:35 -0400 Delivered-To: 301394-close(a)bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Source: drupal Source-Version: 4.5.2-4 We believe that the bug you reported is fixed in the latest version of drupal, which is due to be installed in the Debian FTP archive: drupal_4.5.2-4.diff.gz to pool/main/d/drupal/drupal_4.5.2-4.diff.gz drupal_4.5.2-4.dsc to pool/main/d/drupal/drupal_4.5.2-4.dsc drupal_4.5.2-4_all.deb to pool/main/d/drupal/drupal_4.5.2-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 301394(a)bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen <bengen(a)debian.org> (supplier of updated drupal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster(a)debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 21:23:27 +0200 Source: drupal Binary: drupal Architecture: source all Version: 4.5.2-4 Distribution: unstable Urgency: low Maintainer: Hilko Bengen <bengen(a)debian.org> Changed-By: Hilko Bengen <bengen(a)debian.org> Description: drupal - fully-featured content management/discussion engine Closes: 301394 301946 306997 Changes: drupal (4.5.2-4) unstable; urgency=low . * [Miguel Figueiredo <elmig(a)debianpt.org>] Added Portuguese translation (Closes: #301394) * [Valentina Commissari <ayor(a)quaqua.net>] Added Italian translation (Closes: #301946) * [Gleydson Mazioli da Silva <gleydson(a)debian.org>] Updated Brazilian Portuguese translation. * Fixed typo in package description (Closes: #306997) Files: f36a5fd78d26ebb6c9935d9569cc5130 609 web extra drupal_4.5.2-4.dsc 8ec0c830ae5fa35def8748bc0c215704 38367 web extra drupal_4.5.2-4.diff.gz 30333b315df4c7e169d2ea527b01a41c 484812 web extra drupal_4.5.2-4_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjP3WUCgnLz/SlGgRArERAJ9ncqDeD/Rk2jjYdcTZYHlyhmO/9QCfW/Gn Y4dwFZSdXMrCAy7xoYrVO0Y= =71Pz -----END PGP SIGNATURE-----

1 0

[drupal-devel] Bug#306997: marked as done (drupal: Typo in package description.)
by owner＠bugs.debian.org 19 May '05

19 May '05

Your message dated Thu, 19 May 2005 17:17:35 -0400 with message-id <E1DYsOd-0007we-00(a)newraff.debian.org> and subject line Bug#306997: fixed in drupal 4.5.2-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 30 Apr 2005 01:01:24 +0000 >From cafuego(a)mail.cc.com.au Fri Apr 29 18:01:24 2005 Return-path: <cafuego(a)mail.cc.com.au> Received: from mail.cc.com.au [202.125.40.176] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DRgMG-0004mv-00; Fri, 29 Apr 2005 18:01:24 -0700 Received: by mail.cc.com.au (Postfix, from userid 1000) id E976680C003; Sat, 30 Apr 2005 11:01:21 +1000 (EST) Date: Sat, 30 Apr 2005 11:01:21 +1000 From: Peter Lieverdink <debian-bugs(a)cafuego.net> To: Debian Bug Tracking System <submit(a)bugs.debian.org> Subject: drupal: Typo in package description. Message-ID: <20050430010116.GA27663(a)mail.cc.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Silly-Header: I have edited my /etc/reportbug.conf X-Reportbug-Version: 3.8 User-Agent: Mutt/1.5.9i Delivered-To: submit(a)bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: drupal Version: 4.5.2-3 Severity: minor Description: fully-featured content management/discussion engine Drupal is a dynamic web site platform which allows an individual or community of users to publish, manage and organize a variety of content, Drupal integrates many popular features of content management systems, weblogs, collaborative tools and discussion-based community software into one easy-to-use package. . More informatiion about is available at http://www.drupal.org Note the duplicate 'i' in informatiion. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-k7 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages drupal depends on: ii apache 1.3.33-4 versatile, high-performance HTTP s ii apache2-mpm-prefork [apache2 2.0.53-5 traditional model for Apache2 ii debconf 1.4.30.13 Debian configuration management sy pn makepasswd Not found. ii mysql-client 4.0.24-5 mysql database client binaries ii php4-cgi 4:4.3.10-12 server-side, HTML-embedded scripti ii php4-mysql 4:4.3.10-12 MySQL module for php4 ii php4-pear 4:4.3.10-12 PEAR - PHP Extension and Applicati ii postfix [mail-transport-agen 2.1.5-9 A high-performance mail transport pn wwwconfig-common Not found. --------------------------------------- Received: (at 306997-close) by bugs.debian.org; 19 May 2005 21:21:46 +0000 >From katie(a)ftp-master.debian.org Thu May 19 14:21:46 2005 Return-path: <katie(a)ftp-master.debian.org> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DYsSg-0005zY-00; Thu, 19 May 2005 14:21:46 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1DYsOd-0007we-00; Thu, 19 May 2005 17:17:35 -0400 From: Hilko Bengen <bengen(a)debian.org> To: 306997-close(a)bugs.debian.org X-Katie: $Revision: 1.55 $ Subject: Bug#306997: fixed in drupal 4.5.2-4 Message-Id: <E1DYsOd-0007we-00(a)newraff.debian.org> Sender: Archive Administrator <katie(a)ftp-master.debian.org> Date: Thu, 19 May 2005 17:17:35 -0400 Delivered-To: 306997-close(a)bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 3 Source: drupal Source-Version: 4.5.2-4 We believe that the bug you reported is fixed in the latest version of drupal, which is due to be installed in the Debian FTP archive: drupal_4.5.2-4.diff.gz to pool/main/d/drupal/drupal_4.5.2-4.diff.gz drupal_4.5.2-4.dsc to pool/main/d/drupal/drupal_4.5.2-4.dsc drupal_4.5.2-4_all.deb to pool/main/d/drupal/drupal_4.5.2-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 306997(a)bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen <bengen(a)debian.org> (supplier of updated drupal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster(a)debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 21:23:27 +0200 Source: drupal Binary: drupal Architecture: source all Version: 4.5.2-4 Distribution: unstable Urgency: low Maintainer: Hilko Bengen <bengen(a)debian.org> Changed-By: Hilko Bengen <bengen(a)debian.org> Description: drupal - fully-featured content management/discussion engine Closes: 301394 301946 306997 Changes: drupal (4.5.2-4) unstable; urgency=low . * [Miguel Figueiredo <elmig(a)debianpt.org>] Added Portuguese translation (Closes: #301394) * [Valentina Commissari <ayor(a)quaqua.net>] Added Italian translation (Closes: #301946) * [Gleydson Mazioli da Silva <gleydson(a)debian.org>] Updated Brazilian Portuguese translation. * Fixed typo in package description (Closes: #306997) Files: f36a5fd78d26ebb6c9935d9569cc5130 609 web extra drupal_4.5.2-4.dsc 8ec0c830ae5fa35def8748bc0c215704 38367 web extra drupal_4.5.2-4.diff.gz 30333b315df4c7e169d2ea527b01a41c 484812 web extra drupal_4.5.2-4_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjP3WUCgnLz/SlGgRArERAJ9ncqDeD/Rk2jjYdcTZYHlyhmO/9QCfW/Gn Y4dwFZSdXMrCAy7xoYrVO0Y= =71Pz -----END PGP SIGNATURE-----

1 0

[drupal-devel] Bug#301946: marked as done (drupal: Italian po file translation)
by owner＠bugs.debian.org 19 May '05

19 May '05

Your message dated Thu, 19 May 2005 17:17:35 -0400 with message-id <E1DYsOd-0007wc-00(a)newraff.debian.org> and subject line Bug#301946: fixed in drupal 4.5.2-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 29 Mar 2005 08:59:10 +0000 >From ayor(a)quaqua.net Tue Mar 29 00:59:09 2005 Return-path: <ayor(a)quaqua.net> Received: from adsl-2-61.38-151.net24.it (psychick) [151.38.61.2] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DGCZ2-00042W-00; Tue, 29 Mar 2005 00:59:08 -0800 Received: by psychick (Postfix, from userid 1001) id E403537F2B; Tue, 29 Mar 2005 10:57:01 +0200 (CEST) Date: Tue, 29 Mar 2005 10:57:01 +0200 From: Valentina <ayor(a)quaqua.net> To: Debian Bug Tracking System <submit(a)bugs.debian.org> Subject: drupal: Italian po file translation Message-ID: <20050329085701.GA2383@psychick> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline X-Reportbug-Version: 3.8 X-Debbugs-Cc: ayor(a)quaqua.net User-Agent: Mutt/1.5.6+20040907i Content-Transfer-Encoding: 7bit Delivered-To: submit(a)bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE, X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Package: drupal Version: 4.5.2-3 Severity: wishlist Tags: patch l10n I attach the Italian po translation. Please add it to the package. Thanks Valentina Commissari -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.3 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages drupal depends on: pn apache | apache-ssl | apache- Not found. ii debconf 1.4.30.11 Debian configuration management sy ii makepasswd 1.10-2 Generate and encrypt passwords pn mysql-client | virtual-mysql- Not found. pn php4-cli Not found. pn php4-mysql | php4-pgsql Not found. ii postfix [mail-transport-agent 2.1.5-6 A high-performance mail transport pn wwwconfig-common Not found. --FCuugMFkClbJLl1L Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: attachment; filename="it.po" Content-Transfer-Encoding: quoted-printable # Italian translation of debconf for Drupal. # This file is distributed under the same license as the Drupal package. # Copyright 2005 by Valentina Commissari <ayor(a)quaqua.net>. msgid "" msgstr "" "Project-Id-Version: Drupal 4.5.2-3\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2005-02-06 00:26+0100\n" "PO-Revision-Date: 2005-03-29 10:50+0100\n" "Last-Translator: Valentina Commissari <ayor(a)quaqua.net>\n" "Language-Team: Italian <debian-l10n-italian(a)lists.debian.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=3Dutf-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Italian\n" "X-Poedit-Country: ITALY\n" "X-Poedit-SourceCharset: utf-8\n" #. Type: boolean #: ../templates.master:4 msgid "Automatically create Drupal database?" msgstr "Creare automaticamente il database di Drupal?" #. Type: boolean #: ../templates.master:4 msgid "Drupal needs access to a database, along with initialized data str= uctures in order to function properly. This can be created automatically = by this package, for MySQL or PostgreSQL databases." msgstr "Drupal necessita dell'accesso ad un database, associato a struttu= re dati inizializzate per far s=EC che funzioni correttamente. Questo puo= ` essere creato automaticamente da questo pacchetto, per database come My= SQL o PostgreSQL." #. Type: boolean #: ../templates.master:4 msgid "Automatically creating the database does not make sense if a Drupa= l database already exists or if no database server has been setup when Dr= upal is installed." msgstr "Creare automaticamente il database non ha senso se esiste gia` un= database di Drupal o se non e` stato impostato un server per database qu= ando Drupal e` stato installato." #. Type: boolean #: ../templates.master:16 msgid "Run database update script?" msgstr "Eseguire lo script di aggiornamento database?" #. Type: boolean #: ../templates.master:16 msgid "If you are upgrading Drupal from an older upstream version, the da= tabase structure needs to be updated. This package can perform this task = automatically." msgstr "Se si sta aggiornando Drupal da una versione piu` vecchia, la str= uttura del database necessita di essere aggiornata. Questo pacchetto puo`= svolgere questa funzione automaticamente." #. Type: boolean #: ../templates.master:16 msgid "A manual update procedure is available by pointing a web browser t= o <http://$SITE/update.php>." msgstr "Una procedura di aggiornamento manuale e` disponibile andando con= un browser all'indirizzo: <http://$SITE/update.php>." #. Type: boolean #: ../templates.master:16 msgid "The database will be backed up to prevent data loss." msgstr "Il database sara` salvato in un backup per prevenire perdite di d= ati." #. Type: select #: ../templates.master:30 msgid "Database engine to be used with Drupal" msgstr "Motore del database da essere usato con Drupal" #. Type: string #: ../templates.master:35 msgid "Database server for Drupal's database" msgstr "Server del database per il database di Drupal" #. Type: string #: ../templates.master:40 msgid "Database server administrator user name on host ${host}" msgstr "Nome dell'amministratore del server del database sull'host ${host= }" #. Type: password #: ../templates.master:45 msgid "Password for database server administrator ${user} on host ${host}= " msgstr "Password per l'amministratore del server del database ${user} sul= l'host ${host}" #. Type: password #: ../templates.master:45 msgid "The answer will not be stored anywhere permanently." msgstr "La risposta non sara` permanentemente archiviata." #. Type: string #: ../templates.master:51 msgid "Drupal database owner username" msgstr "Nome del proprietario del database di Drupal" #. Type: string #: ../templates.master:51 msgid "This username will be used by Drupal to connect to the database se= rver." msgstr "Questo nome sara` usato da Drupal per connettersi al server del d= atabase." #. Type: password #: ../templates.master:57 msgid "Drupal database owner password" msgstr "Password del proprietario del database di Drupal" #. Type: password #: ../templates.master:57 msgid "If no password is specified here, a random password will be genera= ted." msgstr "Se qui non viene specificata nessuna password, ne sara` generata = una casuale." #. Type: string #: ../templates.master:64 msgid "Drupal database name" msgstr "Nome del database di Drupal" #. Type: boolean #: ../templates.master:69 msgid "Remove Drupal database when the package is removed?" msgstr "Rimuovere il database di Drupal quando il pacchetto viene rimosso= ?" #. Type: boolean #: ../templates.master:74 msgid "Remove former database backups when the package is removed?" msgstr "Rimuovere i vecchi backup del database quando il pacchetto viene = rimosso?" #. Type: boolean #: ../templates.master:74 msgid "These backups are stored in /var/lib/drupal/backups. This will not= remove the current database from the DBMS." msgstr "Questi backup sono salvati in /var/lib/drupal/backups. Questo non= rimuovera` l'attuale database dal DBMS." #. Type: multiselect #: ../templates.master:82 msgid "Web server(s) that should be configured automatically" msgstr "I server web che devono essere automaticamente configurati" #. Type: note #: ../templates.master:86 msgid "User creation failed" msgstr "Creazione dell'utente fallita" #. Type: note #: ../templates.master:93 msgid "Attempt to modify config file ${conffile} failed" msgstr "Tentativo di modificare il file di configurazione ${conffile} fal= lito" #. Type: note #: ../templates.master:100 msgid "Database creation failed" msgstr "Creazione del database fallita" #. Type: note #: ../templates.master:107 msgid "Database initialization failed" msgstr "Inizializzazione del database fallita" #. Type: note #: ../templates.master:114 msgid "Automatic database update failed" msgstr "Aggiornamento automatico del database fallito" #. Type: note #: ../templates.master:114 msgid "The automatic update script failed to update the database." msgstr "Lo script di aggiornamento automatico ha fallito nell'aggiornare = il database" #. Type: note #: ../templates.master:123 msgid "Automatic update script can not be run" msgstr "Lo script di aggiornamento automatico non puo` essere eseguito" #. Type: note #: ../templates.master:123 msgid "Configuration files of a Drupal package ${oldversion} have been fo= und, but the package itself has been removed. Therefore, it is not possib= le to run the automatic update script." msgstr "Sono stati trovati file di configurazione di un pacchetto Drupal = ${oldversion}, ma lo stesso pacchetto e` stato rimosso. Per questo motivo= non e` possibile eseguire lo script di aggiornamento automatico." #. Type: note #: ../templates.master:123 msgid "Please run it by hand after the package has been successfully inst= alled. Either point your web browser to ${site_root}/update.php or run /u= sr/share/drupal/scripts/debian-update.php from a shell." msgstr "Eseguirlo manualmente dopo che il pacchetto e` stato installato c= on successo. Tramite un browser web andare all'indirizzo ${site_root}/upd= ate.php o eseguire /usr/share/drupal/scripts/debian-update.php da una she= ll." #. Type: note #: ../templates.master:135 msgid "Database removal failed" msgstr "Rimozione del database fallita" #. Type: note #: ../templates.master:135 msgid "Script output:" msgstr "Output dello script:" #. Type: note #: ../templates.master:135 msgid "${result}" msgstr "${result}" --FCuugMFkClbJLl1L-- --------------------------------------- Received: (at 301946-close) by bugs.debian.org; 19 May 2005 21:21:45 +0000 >From katie(a)ftp-master.debian.org Thu May 19 14:21:45 2005 Return-path: <katie(a)ftp-master.debian.org> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DYsSf-0005zL-00; Thu, 19 May 2005 14:21:45 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1DYsOd-0007wc-00; Thu, 19 May 2005 17:17:35 -0400 From: Hilko Bengen <bengen(a)debian.org> To: 301946-close(a)bugs.debian.org X-Katie: $Revision: 1.55 $ Subject: Bug#301946: fixed in drupal 4.5.2-4 Message-Id: <E1DYsOd-0007wc-00(a)newraff.debian.org> Sender: Archive Administrator <katie(a)ftp-master.debian.org> Date: Thu, 19 May 2005 17:17:35 -0400 Delivered-To: 301946-close(a)bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 2 Source: drupal Source-Version: 4.5.2-4 We believe that the bug you reported is fixed in the latest version of drupal, which is due to be installed in the Debian FTP archive: drupal_4.5.2-4.diff.gz to pool/main/d/drupal/drupal_4.5.2-4.diff.gz drupal_4.5.2-4.dsc to pool/main/d/drupal/drupal_4.5.2-4.dsc drupal_4.5.2-4_all.deb to pool/main/d/drupal/drupal_4.5.2-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 301946(a)bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen <bengen(a)debian.org> (supplier of updated drupal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster(a)debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 21:23:27 +0200 Source: drupal Binary: drupal Architecture: source all Version: 4.5.2-4 Distribution: unstable Urgency: low Maintainer: Hilko Bengen <bengen(a)debian.org> Changed-By: Hilko Bengen <bengen(a)debian.org> Description: drupal - fully-featured content management/discussion engine Closes: 301394 301946 306997 Changes: drupal (4.5.2-4) unstable; urgency=low . * [Miguel Figueiredo <elmig(a)debianpt.org>] Added Portuguese translation (Closes: #301394) * [Valentina Commissari <ayor(a)quaqua.net>] Added Italian translation (Closes: #301946) * [Gleydson Mazioli da Silva <gleydson(a)debian.org>] Updated Brazilian Portuguese translation. * Fixed typo in package description (Closes: #306997) Files: f36a5fd78d26ebb6c9935d9569cc5130 609 web extra drupal_4.5.2-4.dsc 8ec0c830ae5fa35def8748bc0c215704 38367 web extra drupal_4.5.2-4.diff.gz 30333b315df4c7e169d2ea527b01a41c 484812 web extra drupal_4.5.2-4_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjP3WUCgnLz/SlGgRArERAJ9ncqDeD/Rk2jjYdcTZYHlyhmO/9QCfW/Gn Y4dwFZSdXMrCAy7xoYrVO0Y= =71Pz -----END PGP SIGNATURE-----

1 0