This issue will keep track of the ongoing process of porting localize.drupal.org to Drupal 7.

Drupal.org servers

https://localize-7.staging.devdrupal.org/ displays the current status of the port of localize, it may be broken sometimes.
This is a staging site, that contains partially sanitized info.

You can set up you own version of localize with sanitized data from the original localize.drupal.org by working with the infra team servers

Roadmap

  1. Update Drupal core
  2. Update OG
  3. #1510384: Views Role Filter Needs tests
  4. #2512722: Missing text format filtered_html
  5. #2513800: Duplicated VBO select all operation
  6. #2514920: "Missing strings?" link runs into error
  7. #2534606: Users testing localize staging report being unable to create Story or Poll content
  8. #2543440: Localization remote submission fails
  9. Test project listings (dump tsv) integration and figure out if there are any issues mandatory to fix
  10. Test .po file packaging cron and figure out if there are any issues mandatory to fix
  11. #1392694: Replace Messaging/Notification modules (postponed for after upgrade)
  12. #1666262: Verify permissions after D7 upgrade
  13. Ongoing until the end: update, test and patch l10n_server D7 by filling the issue queue

Non-blockers to launch but (very) nice to fix

  1. #2512110: Translation team admins membership date is reset in migration
  2. #2524384: Wrong URLs returns not 404
  3. #2511482: Primary profile link not shown on profiles
  4. #2534610: A user should be returned to the group page when deleting story or poll content

Comments

Gábor Hojtsy’s picture

- The drupal.org modules are all at http://drupal.org/project/drupalorg
- killes can give you a dump (and I think gave you one before?)

SebCorbin’s picture

- The drupal.org modules are all at http://drupal.org/project/drupalorg

Ok, I did not know d.o modules were there.

- killes can give you a dump (and I think gave you one before?)

Yes, a sanitized dump dated 10th April 2011, the question is: is it still good for this port? Should I get one fresher?

Updating list...

SebCorbin’s picture

Project:Drupal.org infrastructure» localize.drupal.org
Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

Gábor Hojtsy’s picture

Project:localize.drupal.org» Drupal.org infrastructure

@SebCorbin: anything else you need that I can help with?

Gábor Hojtsy’s picture

Project:Drupal.org infrastructure» localize.drupal.org
Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Project:localize.drupal.org» Drupal.org infrastructure

@Gábor I'm good for now, thanks for all!

Updating summary to make this issue an entry point for other people.

SebCorbin’s picture

Project:Drupal.org infrastructure» localize.drupal.org
Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

Ayesh’s picture

Project:localize.drupal.org» Drupal.org infrastructure

It's a little confusing for completely new Drupal 7 users that Interface of drupal.org is much different to what they have installed. So I think it's the perfect time to get drupal.org sites ported to D7.

One other point that we probably have to take care is Bakery SSO. It works between D6 master site and new D7 - but will need some testing.

What about Flag (D7 ready) module for subscriptions ? Honestly I'm not sure where and why Messaging and Notifications modules are used. But at least I guess Flag module can lift the weight.

amitaibu’s picture

5. Find a replacement for Messaging & Notifications

Last time I talked with Gabor about using Message module, he said and I agreed, that it needs to mature.

Since then (Drupalcon Copenhagen), It was re-written by fago and myself to take advantage of entity API and it had 2 stable releases since.
So, Message can be used for an activity stream, and notifications can be handled by Message-notify

rvilar’s picture

@SebCorbin If I can help you, please contact me. I'm the team leader for Catalan translation and I love l.d.o. It's one of the best Drupal system for the past few years.

podarok’s picture

You can Use my skills and free time for testing, coding, reviewing and so on for do this more efficiently
http://www.linkedin.com/in/podarok

wulff’s picture

I'd be happy to help as well. I mostly do backend stuff, but I can help test the frontend and write test cases as well.

I'm the maintainer of the Danish translation of Drupal (and thus a heavy user of l.d.o) and have provided a couple of patches for the D6 version of the localization server.

Kristen Pol’s picture

I might be able to help with this project depending on timing. I'm working on a D7 i18n book and will likely be buried in that for the next month. Also, I'd like to help out with D8MI too. So... I'll keep track of progress and jump in if I can!

Thanks for organizing this!

Kristen

Gábor Hojtsy’s picture

Talked to @Amitaibu over IRC.

[07:42am] GaborHojtsy: amitaibu: hi
[07:42am] amitaibu: GaborHojtsy: Hi man, what's up?
[07:47am] GaborHojtsy: amitaibu: hey, I was wondering if you know of any upgrade path for og_user_roles to og 7 and/or messaging/notifications to your message module for the l.d.o D7 update?
[07:48am] amitaibu: GaborHojtsy: ogur to OG should be easier to write (no upgrde path that I know of). messaging => message would require more effort, as Message is a simple API, and the subscription logic isn't there
[07:49am] amitaibu: GaborHojtsy: about ogur -- are the roles the same in each group, or different?
[07:51am] GaborHojtsy: amitaibu: they are same, I don't think ogur allows us to have different roles for different groups
[07:53am] amitaibu: GaborHojtsy: ok, that's good, it will be easier to map the roles
[07:54am] GaborHojtsy: amitaibu: :)
[07:54am] amitaibu: GaborHojtsy: is there already a dev site with OG7 running there?
[07:55am] GaborHojtsy: amitaibu: no, not yet
[07:55am] GaborHojtsy: amitaibu: I'm trying to help connect the dot for the guys there is a d.o test site to use for this but that is still running a copy of the D6 site
[07:56am] GaborHojtsy: amitaibu: basically the two biggies we expect in the update are the ogur and messaging upgrade/migration
[07:56am] GaborHojtsy: amitaibu: the site is going to be http://d7upgrade-localize.redesign.devdrupal.org/
[07:57am] amitaibu: GaborHojtsy: i think/ hope ogur shouldn't be a big issue. Messaging is imo the bigger problem
[07:59am] GaborHojtsy: amitaibu: hm, ok
[08:01am] GaborHojtsy: amitaibu: thanks

Gábor Hojtsy’s picture

Project:Drupal.org infrastructure» localize.drupal.org
Component:localize.drupal.org» Code

Move to new queue. Please help moving all issues to our own new queue :) Also create components as needed.

Gábor Hojtsy’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Updated issue summary

Thanks all! Upgrade is in progress but I'm currently struggling with drupal.org development servers as it appears that I am the first one to test an core upgrade on them.

I'll update this issue as soon as I have at least Drupal Core upgraded. Then we will be able to test OG with the actual accounts.

Ayesh’s picture

Hooray!
Let us know if you need testers or any other help!

droplet’s picture

Im holding few patches for l10n_server, feel free to PM me if any issues need a reroll or upgrade.

http://drupal.org/project/issues/search/l10n_server?participant=droplet&...

droplet’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

The port is going forward, I just need to contact Amitaibu about OGUR, for now:

  • The groups are shown
  • Main pages too (home)
  • l10n_packager needs to be tested in real conditions, as files were not part of the imaging
  • Translate interface is up (for the admin, as OGUR is not ported)
  • Some views (related to blocks) need to be updated

I will contact each person who offered his/her help with a single-time login link as soon as it's worthy of testing.

SebCorbin’s picture

Quick update on the status of this port. After bugfixing l10n_server (see #1466262: Multiple bug fixes for 7.x-1.x branch), most of the features are now migrated:

Known bugs that need work:

  • OG User Roles proper migration/test
  • Group roles managing page to (re)write

To be tested:

  • Packaging as well as export of translations
  • PO import

BTW, notifications have not been implemented yet, I will see an approach to the Message module.

Gábor Hojtsy’s picture

Superb progress, congrats! I think the drupalorg connector will need some special attention too, just to make sure it was properly updated. It has no test coverage / it cannot have any test coverage, so hard to prove without manual testing.

Pomliane’s picture

Manual testing? May I help?

SebCorbin’s picture

Thanks to Gabor, I know have git access to l10n_server project, so it will be a lot easier, see latest logs: http://drupalcode.org/project/l10n_server.git/shortlog/refs/heads/7.x-1.x

So now the og_views module is no longer a dependency and l10n_groups provides the "River of news" that OG did provide in D6.
I rewrote the og_block_details on a group that was also missing in OG7 and cleaned the 7.x-1.x issue queue of bug reports at the same time.

Next step: drupalorg connector (I'm too afraid of OGUR for now :-))

@Pomliane: testing will come, I promise!

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

webchick’s picture

Issue tags:+Drupal.org D7

Tagging.

lucascaro’s picture

Hi there, nice to see all this progress for D7!

I just wanted to comment that I've been testing l10n_server-7.x-1.x-dev and found that the packager doesn't seem to work (see #1549780: Repackaging Form Not Working ) but importing po files worked.
I tested it connecting from a l10n_client, using a custom module, importing the .po file and also using l10n_update. All that seemed to work.

Let me know if there's something else I can help with since I'd also like to see l10n_server working for D7!

Thanks!

SebCorbin’s picture

Status update: thanks to lucascaro, l10n_server got some work done (essentially on the packager) and should be ready.

Next step: OGUR! I created an issue for this #1565546: OG User Roles (OGUR) upgrade path

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

TODO:

  • Missing "Your group" in quick navigation
  • Implement hook_og_permission in l10n_server modules
  • Discuss of the current permissions scheme and its possible change in D7
lucascaro’s picture

Hey there, here's another blocker for this: #1653328: Undefined index: upload handler in l10n_server_release_file_upload_submit() for l10n_drupal
I'm willing to help with that but I'll need some guidance :)
cheers!

SebCorbin’s picture

Gábor Hojtsy’s picture

My latest info from @Sebcorbin:

Hello Gabor,

I had little time to review what is missing in LDO D7. So thanks to drumm we now have a staging site, but the job is broken on Jenkins now that I have added and updated some modules (http://localhost:8080/view/Localize/job/snapshot_to_localize.7.devdrupal...).
I'll see about that with drumm before BoF if possible.
The job also lacks the OG migrate command, I added an issue for that in the infrastructure queue, see http://drupal.org/node/1739800

Then we have a lot of work on OG and l10n_groups:
Fix views role filter (the block displaying admins of a group is broken), see http://drupal.org/node/1510384
Verify that OG roles are migrated (should be global roles)
Verify that the permissions are migrated (or maybe they need to be updated manually) http://drupal.org/node/1666262
Control that the permissions are respected throughout the UI
Make sure the l10n packages are either linked or re-built (re-building works, but it'll take a long time, so better have the older linked)

Hope that write-up is useful. Good luck with the BoF, ping me on twitter if I'm not connected on IRC if I can help :)

Gábor Hojtsy’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

#1510384: Views Role Filter is now fixed.

Updated issue summary.

You can now all contribute by making your own server instance of LDO D7 thanks to the infra team :)

If you don't have time/the skills to put up your own version of ldo D7, please contact me on IRC (sebcorbin) so I can send you a reset password URL to log on the staging site.

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

SebCorbin’s picture

Issue summary:View changes

Updated issue summary.

drumm’s picture

Issue tags:-Drupal.org D7

(Removing Drupal.org D7 tag since this is not needed for Drupal.org itself. Still is a great thing to get done.)

Gábor Hojtsy’s picture

Title:Port localize.drupal.org to D7» Port localize.drupal.org to Drupal 7
Jose Reyero’s picture

Not the same thing, but here's some starting code for a l10n site install profile, https://drupal.org/sandbox/reyero/1775418

Jose Reyero’s picture

Issue summary:View changes

Updated issue summary.

Gábor Hojtsy’s picture

FYI marked #1392694: Replace Messaging/Notification modules postponed (until after the upgrade).

s_leu’s picture

Recently i was going through the code of the 7.x-1.x branch of the l10n_server module and found some bugs. I created issues for those in the project during the last few days: ttps://drupal.org/project/issues/l10n_server?version=1224352

Also i checked for issues that were fixed in the 6.x-3.x version but were not yet ported to 7.x-1.x. Except for #1673074: localize.drupal.org "Not allowed to submit translations in this language." i provided already patches for all of those issues.

Additionally i created a drush dsb integration that allows developers a quick setup of the l10_server by using the drush scenario builder project: Drush scenario builder. A patch for that will follow soon at #2037771: Add drush scenario builder config and scripts

Me, miro_dietiker and berdir also would like to participate in the review of the staging site of localize.7.devdrupal.org. Unfortunately we didn't get access to it yet, see #2025055: Need my public key added to localize.7.devdrupal.org I think it would also be enough to review only a dev site, but such one doesn't exists currently.

s_leu’s picture

As discussed with Gabor i also checked the issue queue of potx for patches that were only commited for 6.x-3.x and needed to be ported to 7.x-2.x, those patches are now all rerolled and should be reviewed.

Also i provided many patches in the issues that i opened after the review of l10n_server, they need reviews as well of course. In addition to that i added a test for l10n client, which tests the submission of translation suggestions to a mocked l10n_server callback. I uploaded a patch for that at #2045609: Add test for translation submission

s_leu’s picture

Issue summary:View changes

Postponed messaging

catch’s picture

Issue summary:View changes
drumm’s picture

I believe this is ready for QA & launch.

It may be a bit rough, since some D8 support has been implemented in D6, and may not be ported to D7 yet. If any of that is a hard blocker, that should be noted here.

Gábor Hojtsy’s picture

It is DEFINITELY a hard blocker. It would be a disaster to step back so much, at the time the module was ported, D8 support was almost none in the codebase. If not porting that would be a serious step-back for the release process of D8.

Gábor Hojtsy’s picture

drumm’s picture

Issue summary:View changes

Clarifying Drupal.org servers. The staging URL changed as we completed Drupal.org's upgrade. Staging only sanitizes emails (to help prevent accidental notifications) and any private keys. Dev is fully sanitized, including removing unpublished data. Localize dev is not truncated, only Drupal.org itself is large enough to need truncation.

YesCT’s picture

adding "infrastructure blocker for Drupal 8.0.0" tag, since this blocks the drupal 8 core issue: #2267715: [meta] Drupal.org (websites/infra) blockers to a Drupal 8 RC1, so that the infrastructure blockers to d8 release (in issue queues outside of the core queue) is accurate. Remove the blocker tag when this issue is fixed, and update 2267715.

webchick’s picture

Trying to get a handle on release blockers prior to 8.0.0 and what (if anything) the community can do to help things along in preparation of https://events.drupal.org/losangeles2015/sessions/plain-drupal-english-g...

So according to this issue, the localize.drupal.org port was in final QA and looked ready to go as of June 2014. I notice today though that https://localize.drupal.org/CHANGELOG.txt is still Drupal 6.

What's left to get this deployed, and is this a place where community members can jump in at LA?

drumm’s picture

hestenet’s picture

hestenet’s picture

Issue summary:View changes
hestenet’s picture

Issue summary:View changes
tvn’s picture

Category:Task» Plan
hestenet’s picture

Issue summary:View changes
japerry’s picture

Issue summary:View changes
japerry’s picture

Issue summary:View changes
Gábor Hojtsy’s picture

Issue summary:View changes

Moving #2512110: Translation team admins membership date is reset in migration to mandatory because breaking history this way would not be ok. Added the following two items where we don't know if there are issues because nobody ever tested them:

  • Test XML-RPC integration (l10n_client) and figure out if there are any issues mandatory to fix
  • Test project listings (dump tsv) integration and figure out if there are any issues mandatory to fix
  • Test .po file packaging cron and figure out if there are any issues mandatory to fix
drumm’s picture

Test project listings (dump tsv) integration and figure out if there are any issues mandatory to fix

Looks like it is working well. The release at the top of the list is on staging.

Test .po file packaging cron and figure out if there are any issues mandatory to fix

Also looks okay. Some files are being packaged, and matches production.

drumm’s picture

Issue summary:View changes
Gábor Hojtsy’s picture

Issue summary:View changes

Even though the XML-RPC is supposedly unlocked, localization client does not work with it :/ See #2033733: Invalid localization server address specified. Make sure you specified the right server address.

Balu Ertl’s picture

Screenshot to Gábor's previous comment.

Gábor Hojtsy’s picture

Seems like the XML-RPC endpoint like the rest of the site has HTTP Authentication and is therefore still untestable with the client :/

SebCorbin’s picture

Tried with https://drupal:drupal@localize-7.staging.devdrupal.org/ and I got it working, although I get permission error when submitting:

Reason: Not allowed to submit translations in this language.

The global permission 'submit suggestions remotely' is set to all authenticated users, but it may be overriden by a group permission (which seem not set at all)

Gábor Hojtsy’s picture

Status:Active» Needs work

@SebCorbin: looking at https://localize-7.staging.devdrupal.org/admin/config/group/roles/node/l... and https://localize-7.staging.devdrupal.org/admin/config/group/permissions/... all of the custom roles are fubar (no names, no assigned permissions, etc), so looks like the site was relaunched without the update completing or something?!

japerry’s picture

OG has updated a bit since the 2.7 release. Unfortunately there are two reverts that are needed because they break OG context. Patches below will do that.

Posting here because OG issue queue is pretty much dead and we need to refer to it in the make file.

Gábor Hojtsy’s picture

I guess the update ran again and it seems OG does not even think localization groups are groups anymore... That seems like another step back :/

Also I see the adminimal theme was added, which looks fine however several frontend blocks are showing up on the admin pages.

japerry’s picture

Status:Needs work» Active

Grr, I see what happened. After I did the migration, the snapshot to staging executed again. There is some manual steps that have to occur after. I've disabled the automatic deploy from production and re-migrated data, and should be good to review.

japerry’s picture

Status:Active» Needs review

After some work last night on OG roles and permissions, I think we're close to an RC. I'm marking the remaining issues as 'needs review', for testing, if those are marked fixed, I think we'll be ready to deploy.. as long as we don't find anything else ;)

Give it a try: https://localize-7.staging.devdrupal.org

japerry’s picture

Updated child issues. Unless there are any other criticals, the current staging site should be a decent release candidate.

Gábor Hojtsy’s picture

Looks like the main outstanding question is the l10n_client integration permissions issue at #2033733: Invalid localization server address specified. Make sure you specified the right server address. (issue not titled very well anymore).

Gábor Hojtsy’s picture

Issue summary:View changes

Swapped out #2033733: Invalid localization server address specified. Make sure you specified the right server address. in the summary to #2543440: Localization remote submission fails, which is a much better place to figure that issue out. The client issue was pre-existing and is not related to the update (even if it happened to the staging site too at one point, it does not happen there anymore).

japerry’s picture

Issue summary:View changes

Things getting close. Next step is to test connecting to the new site. If that can be fixed, I think we're ready for launch.

japerry’s picture

Issue summary:View changes

I think we're ready for deployment. If everything goes well over the weekend while folks test, I think we're aiming for a Tuesday or Wednesday launch.

If anything is found, please report it here!

webchick’s picture

Status:Needs review» Reviewed & tested by the community

Exciting. Updating the issue status to indicate this, as a signal for "last chance for feedback."

drumm’s picture

Status:Reviewed & tested by the community» Fixed
Related issues:+#2549799: Fix up D7 packaging

This was deployed yesterday. A followup issue is #2549799: Fix up D7 packaging.

Balu Ertl’s picture

StatusFileSize
new157.36 KB

Thanks a lot to ALL of you guys who worked on to make it happen. The faster l.d.o site helps significantly the work of translators and administrator working on already D8 localization :)

drumm’s picture

Gábor Hojtsy’s picture

@BaluErtl: woot!

@drumm: yeah, I see the tsv is rebuilt daily(?), so we get new stuff each day at about 6:20am (local time to whatever time the logs are tied to)

@all: thanks a lot for your heroic efforts, I don't think I could accurately list all the people who contributed; its really amazing to see this live finally :) let's hope we can get people now to contribute and get the site become as lively as d.o in terms of improvements

Status:Fixed» Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.