Closed (duplicate)
Project:
Drupal.org customizations
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
30 Sep 2009 at 07:57 UTC
Updated:
24 Jan 2014 at 11:06 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
markus_petrux commentedComment #2
gábor hojtsyProject module and l10n_server module are not running on the same Drupal instance, so we have no way to influence the links of project module from localize.drupal.org or the localization server. Also, your suggestions are drupal.org specific changes to project module links. Those are maintained in drupalorg.module, specifically in drupalorg_project_page_link_alter() on the DRUPAL-6--1 branch which we are running with ATM:
We'd need to add such links there. Also, I've been working a little on the source code warnings, which might be something we'd want to link in from the project page to let people easier improve their code quality. Where the project translation overview is at http://localize.drupal.org/translate/projects/cck the warnings are at http://localize.drupal.org/translate/projects/cck/warnings
Retitled so that it does not say we need work on ldo. Also, ldo already cross-links to drupal.org project pages, so we have no work to do there in terms of cross-linking.
Comment #3
markus_petrux commentedThanks for addressing the issue. I had something to ask, but I had little idea on how to, nor where to. Thanks.
Comment #4
gábor hojtsyHere is an initial patch for drupalorg module. There are a few things we need to clean up here:
- we can only link to the same page for view and contribute because we don't know whether the user is member of any team (we could check whether they are logged in at least though, but that does not help that much)
- I've also included the source code warnings interlink, up for discussion
Comment #5
dwwMostly looks fine to me. All projects are automatically synced on l.d.o, right? The only question is which language teams exist, no? So, it's not really the case that the link brings you to all the translations for a project (yet). Some translations might only exist in CVS, etc. Not sure if we really care, but I thought I'd mention it. Otherwise, no objections here.
Thanks!
-Derek
Comment #6
gábor hojtsyYes, all projects are synched. When a project does not have stable releases available for Drupal 5, 6 or 7, then we have "No data available." We probably need better guidance / help text for project developers then to let them know how to fix this issue, and why it happens. Example: http://localize.drupal.org/translate/projects/aBeesParadise
Comment #7
markus_petrux commentedHow about showing these links only when the project has at least one supported release?
I haven't tested, but the patch could be:
Comment #8
dww@markus_petrux: Very good point. I especially like the check that releases are enabled on the project. These links would be silly at http://drupal.org/project/infrastructure for example. ;)
Comment #9
pasquallefixed typo "wanings"
Comment #10
gábor hojtsyWups, looks like I forgot about this one and already committed #827704: Provide translation download links in resources, which took care of one issue this did not handle: translation projects on d.o, but did not take care of things like no releases found. I also don't think we should include the contribution links yet, it seems like duplication and makes it harder to find the useful stuff. Committing this to DRUPAL-6--1 since it was approved above, and setting to be ported to HEAD.
Comment #11
mgiffordWould be nice to see this.
Comment #12
pasqualleThe missing check for "no release found" was already implemented in #827704: Provide translation download links in resources