I think 'op' is simply the arbitrary identifier of the element being validated. form_set_error() marks the element on the form with styling (typically appears in red, or with a red asterisk or a red background) when in error, e.g. a required element was left blank. ..chris On Wed, Jan 21, 2009 at 10:57 AM, Sheryl (Permutations Software) <sheryl@permutations.com> wrote:
Yes, I already did all the things you suggest. I would not have bothered the people on this list with my question if I hadn't already tried hard to find the answer on my own.
-----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Earnie Boyd Sent: Wednesday, January 21, 2009 9:57 AM To: development@drupal.org Subject: Re: [development] converting a module from Drupal 5 to Drupal 6
Quoting "sivaji j.g" <sivaji2009@gmail.com>:
On Wed, Jan 21, 2009 at 11:56 AM, Sheryl (Permutations Software) <sheryl@permutations.com> ...r how I need to rewrite them for
Drupal 6. Any guidance you can give me would be greatly appreciated!
Did you try this ?
A start in the right direction. It doesn't do everything because it just doesn't know how. For instance you'll need to watch out for those ``if ($may_cache)'' and remove them even thought the deadwood removed the parameter in the goodwood version.
Coder is a lint helper to give you suggested ideas of how well your code is formatted to the code standard for that Drupal version. Your module will look prettier but it doesn't help the functionality.
You will also want http://drupal.org/project/schema on the version 5 side of your conversion if you have tables. The project/schema module can help on the version 6 side if you're developing a new table in say phpMyAdmin and now need to create the schema array for your .install file.
-- Earnie http://r-feed.com Make a Drupal difference and review core patches.