[support] upgrading rules module

[Jim Ruby]

I re-installed drupal and install the rules module just fine v7.23, so I
went to my production site and I uninstalled every module rules was
dependent on "did the full uninstall" cleanred the cache twice and then
tried to install rules 7.23 again and again it died on the install. I have
no idea what is in my production db that rules does not like.

Problem is I really would like to upgrade from 7.20 to 7.23 and I keep
banging my head against the brick wall.

Here is my module list, the ones with * in front of them are the ones I
uninstalled.
*advanced_help
backup_migrate
ctools
*entity
filefield_paths
filefield_sources
globalredirect
*node_convert
*node_export
pagestyle
pathauto
pathologic
redirect
rss_field_formatters
*rules
scheduler
*service_links
*taxonomy_entity_index
taxonomy_menu
textsize
token
*uuid
views



-----Original Message-----
From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On
Behalf Of Jim Ruby
Sent: Thursday, April 11, 2013 2:08 AM
To: support at drupal.org
Subject: Re: [support] upgrading rules module

I did the fresh install of drupal 7.22 and upgrading rules from 2.0 to 2.3 I
see there was some database updates. When I upgrade my production site I
never see these database updaes.

So what would be the best way to get rid of rules and all of its related
modules and info from my production db so I can try a install of 2.3?

Could I just uninstall all of its modules in modules and then use uninstall
to remove all from the db and try to install the latest version 2.3.

Thanks.


-----Original Message-----
From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On
Behalf Of John Summerfield
Sent: Wednesday, April 03, 2013 4:52 AM
To: support at drupal.org
Subject: Re: [support] upgrading rules module

On 03/04/13 11:40, Jim Ruby wrote:
> I have been waiting for help with rules module upgrading from 7.x-2.0 
> to
> 7.x-2.2 or the latest dev version. Every time I do it kills my site. I 
> have three sites and it does it on all three of them. Has anyone else 
> encountered this and if so any suggestions on how to resolve this?
> http://drupal.org/node/1920784
> Thank you
>

See whether you can reproduce this with a brand new site, not a migrated
one, using your chosen D7 modules.

If that has no problems, try converting a brand new D6 site with your chosen
D6 modules to D7.

Check that you are logging all the information you can. If you're running
postgres, log its statements etc too. If you're using another database, turn
on whatever it allows you to log.




--
[ Drupal support list | http://lists.drupal.org/ ]

-- 
[ Drupal support list | http://lists.drupal.org/ ]