Can you access your php error log? That may tell you exactly where it's breaking.
On Thu, Jan 9, 2014 at 8:06 PM, Jim Ruby jim@v-community.com wrote:
I can not do it this way because once update.php is run and it does its update things crash. Here is my results this time.
- cleared cache twice
- uploaded rules 7.dev
- ran update.php and here are the updates is said it was going to do.
7203 - Add a database column for specifying a queue item handler. 7204 - Rename rules_scheduler.state into rules_scheduler.data.
Once this was done I received the error and can not longer access the site.
Note updating from rules 7.20 to 7.2.dev so there should be a lot more db updates. Where the table is being created is at 7211
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Linda Romey Sent: Thursday, January 09, 2014 6:19 PM To: support@drupal.org Subject: Re: [support] updating rules module
- install rules module
- run update.php
- clear all caches
On Thu, Jan 9, 2014 at 5:40 PM, Jim Ruby jim@v-community.com wrote:
That I did not do. So I can re install things then update rulesmodule again, so I should do things in this order?
1 clear cache 2 install and update rules module via update.php I'll try it as right now once rules updates the sights is history. -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Linda Romey Sent: Thursday, January 09, 2014 2:04 PM To: support@drupal.org Subject: Re: [support] updating rules module
Did you clear all caches? On Thu, Jan 9, 2014 at 2:21 PM, Jim Ruby <jim@v-community.com>wrote:
The first time I ran update.php I saw two updates, nowwhen I try to run update.php and it just shows an error with no updates available.
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Gordon Heydon Sent: Wednesday, January 08, 2014 5:27 PM To: support@drupal.org Subject: Re: [support] updating rules module
You need to run update.php. There is a change in thedatabase which needs to be fixed before everything works right.�
Gordon.� Sent from my iPhone On 9 Jan 2014, at 9:59 am, Linda Romey <lromey@gmail.com>wrote:
Yes, I did what Jim suggested and found the issue.I also made sure that there were no errors in any of the rules--i.e. I use og and it uses rules. Some of the og fields had changed with that upgrade and so it broke the rules--which I didn't realize. And then the update went fine.
On Wed, Jan 8, 2014 at 5:13 PM, Frank Nikola <fnikola@cognisync.com> wrote:
Hey Jim, This sounds like the standard white screenof death (wsod) problem that is usually caused by a php error.�
You will need to enable error displays andchecking your server logs to help resolve the issue.
See https://drupal.org/node/158043�forassistance. �
On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby <jim@v-community.com> wrote:
I have had this problem in thepast, but the sight gets the white screen of death when I update Rules 7.x-2.0 to 7.x-2.6 Any suggestions on how to troubleshoot this? I have enquired this with in the rules issue cue, but really was never a fix since the author could never reproduce my problem.
Thanks for any suggestions -- [ Drupal support list |-- [ Drupal support list |-- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]-- [ Drupal support list | http://lists.drupal.org/ ]