I just updated the following modules to their latest D5 releases. Please report any odd behavior.
- cck
- date
- calendar
- signup
- link
- token
I am working on the D6 upgrade for groups.drupal.org. At this point, it looks like the only stumbling block is panels for the custom group pages. If I can get panels and og_panels working for D6, I will deploy them in the upgrade. If not, we will temporarily lose that nice feature. I know, I know - this really really really sucks. No matter how many 'really' you add on there, I agree. But the fact remains that we are 50 weeks past the release of Drupal6 and Panels is at 6.x-2.0-alpha3 according to its project page. If this news upsets you, please grab a shovel and work the panels issue queue however you can. Help reproduce bugs or close down unreproducible ones. Help write patches, review patches, write docs, write unit tests, etc.
My timeframe for this D6 upgrade is within 2 weeks.
Comments
Remove private posts?
The panels developers are working hard to make their module ready for groups.drupal.org. It turns out that this is a simpler task than getting the whole panels suite ready.
Also, I am considering removing private groups and private posts. It is a very infrequently used feature, and it does clutter the UI and complicate the listing queries a little. groups.drupal.org is a great example of a scalable node access site but hardly anyone knows it runs node access so that benefit is minimal. Thoughts?
If we proceed, I would archive existing private posts into a text file and then remove them from the site. By definition, google can't access them so no loss there.
Summer of Code
As I recall, it specifically gets used quite heavily for GSOC, so that might be an issue.
True - if that is the only
True - if that is the only use case, they can put up a private drupal site somewhere.
problem with editing group node
Trying to edit a group node today - the username autocomplete field hung, and I could only get my changes to submit by turning off JS.