Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Looking at the project tables for sharing project data turned out to not be enough. We also need information like whether a project or release it actually published. Unpublished projects and releases should not be sycned, since we have nothing to do with them. Also, when a release or project is unpublished on drupal.org we should take appropriate action on localize.drupal.org.
So here is a request to get read access to the node table for the localize_ro DB user.
Comments
Comment #1
nnewton commentedI just granted select on node to localize_ro. Let me know if it doesn't work for you.
Comment #2
gábor hojtsyThanks, works well.
Comment #3
gábor hojtsyUhm, looks like for the release file information, we also need the files table. Sorry for only noticing now, but I just got to syncing the release info, now that syncing the project info works well.
Comment #4
gábor hojtsyShould never promise that those were the last ;)
The project tables have no information on the project type, and we should not syndicate the translation projects obviously. So we'd need access to the taxonomy tables, or actually at least "term_data", so we can join projects through this table to identify projects under http://drupal.org/taxonomy/term/29 which should not be handled by the localization server.
Comment #5
gábor hojtsyHuh, thank God Narayan did not have time ;) I meant files and term_node (not term_data).
Comment #6
nnewton commentedDone. I got you files and term_data, let me know if you need anymore of the term tables.
Comment #7
gábor hojtsyUgm, you did got me term_data but I've updated the issue a nice 14 hours before you to ask for term_node *instead*, realizing my mistake. Please fix.
Comment #8
nnewton commentedHoora for old tabs in firefox :), fixed. let me know if you need anything else.
Comment #10
gábor hojtsyMoving to new queue (sorry for issue-bombing).