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:
by domenic on Tue, 08/05/2008 - 15:41Like a lot of you, I've had to create many many backgrounds for jQuery tabs.
I've mocked up a little template in Photoshop which should help make creation super-simple and fast. An example gradient is included as a style for the less photoshop-literate.
Enjoy! (click to get it!)
(Here's an RGB version that should be GIMP-able)
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.
by domenic on Sun, 04/20/2008 - 16:10Some months ago, I discussed multiple values in CCK using AJAX. A few people showed interest, so here's Part 1 of how AJAX can go together with Drupal.
We'll start with a common use case: checking that a username is available when a new user signs up. After you're done with this tutorial, you should be able to give the new user near-instant feedback on whether or not their username is available. I like to start at my desired result and work backwards, so that's what we'll do.
