I have never understood the excitement behind Drupal install profiles. They purport to cut development time significantly and bring Drupal closer to the masses. Kris at The Worx Company calls them "a game changer for the entire CMS market." The patterns project has been long in development to provide platform to deploy install profiles to multiple sites.
For those eagerly awaiting the next member of the Drupal family, WorkHabit is proud to announce Rupal, the CMS designed exclusively for our valued cross-dressing community members.
Core modules include automatic pronoun feminization, rounded corners on everything, and auto-filtering of "it's a trap!" comments. Over 9,000 hours have been put into lovingly crafting the first community release.
We just had an impromptu conversation over here about validating phone numbers that morphed into validating email addresses and more.
Adam brought up the fact there are a lot of email addresses that don't pass the basic regex validation that a lot of sites use. In fact, there was a good discussion of this very issue on Slashdot in a larger article on regexes. One comment:
My session on Amazon AWS & Drupal at DrupalCampLA. We're walking out the door at DrupalCamp, so I'll get more details up shortly.
When I was in high-school, I worked at an office supply chain in the "Business Machines" department. I sold computers, adding machines, Palm Pilots (the first revision!), printers, cables, you name it. Aside from helping customers, I had to stock those items on the floor, take daily inventory, complete cleaning/organizing projects, set up new displays to specs (Planograms) and take on whatever other tasks my managers wanted me to finish. Eventually, I was promoted to "Business Machines Lead" -- which came with a sweet $0.75/hr raise.
So I'm working on a project now where nodes are mass-imported from a third party. By default, these nodes are unpublished until the delegated party can add additional information that the import can't capture. We publish the node when it's through being reviewed and updated.
To be clear, the workflow looks like:
1) Import nodes (CCK type: "Item"), default status is Unpublished.
2) User with "Reviewer" role looks at the queue of Items that needs reviewed
3) Reviewer reviews Item nodes, then sets them as Published.
Here's the problem though:
