Didn't look at the address bar and didn't mean to send that off list.

The Coder Upgrade is a pretty handy module. It's not 100%, but it does most of the "dirty" stuff. You'll still have to look through all the code, particularly at any queries. But it's also pretty good at inserting messages to let you know where you have to finish the work.
 
Nancy
 
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.

From: Earnie Boyd
I've used Coder occasionally, more for D5 to D6 though.  There are a
lot more changes for D7 and I hear D8 will even be more.  I've tried
to promote the idea of massive API changes on the odd numbered
versions and user experience changes in the even numbered versions but
did get very far.  I still need to look at advuser, that poor module
needs some love.

Earnie

On Mon, Mar 19, 2012 at 10:06 AM, Ms. Nancy Wichmann
<nan_wich@bellsouth.net> wrote:
> Interesting. I found that there raw version out of Coder was still being
> seen by Drupal and apparently overriding the other code that I had cleaned
> up. As soon as I deleted that, I started getting somewhere.
>
> It seems that the idea of looking ahead may not be such a good one. I did
> this module after the concept of splitting some hooks into "_operations"
> calls came out. So the hook_block() had already been split and properly
> named. Coder Upgrade apparently choked on that.
>
> Thanks.
>
> Nancy
>
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King,
> Jr.
>
> ________________________________
> From: Earnie Boyd
> Frustrating ain't it?  When I have these problems I code up a little
> script that bootstraps Drupal and then includes the module.  I then
> use the command line to run it through PHP alone.  The script will
> probably need to execute some of the functions and may need to also
> include other files like .install.  Doing this I find it easier to
> find the PHP errors.



--
Earnie
-- https://sites.google.com/site/earnieboyd