I have had this problem in the past, 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
Hey Jim, This sounds like the standard white screen of death (wsod) problem that is usually caused by a php error. You will need to enable error displays and checking your server logs to help resolve the issue. See https://drupal.org/node/158043 for assistance. On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby <jim@v-community.com> wrote:
I have had this problem in the past, 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 | http://lists.drupal.org/ ]
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 screen of death (wsod) problem that is usually caused by a php error.
You will need to enable error displays and checking your server logs to help resolve the issue.
See https://drupal.org/node/158043 for assistance.
On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby <jim@v-community.com> wrote:
I have had this problem in the past, 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 | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
You need to run update.php. There is a change in the database 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 screen of death (wsod) problem that is usually caused by a php error.
You will need to enable error displays and checking your server logs to help resolve the issue.
See https://drupal.org/node/158043 for assistance.
On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby <jim@v-community.com> wrote:
I have had this problem in the past, 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 | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
The first time I ran update.php I saw two updates, now when 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 the database 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 screen of death (wsod) problem that is usually caused by a php error.� You will need to enable error displays and checking your server logs to help resolve the issue. See https://drupal.org/node/158043�for assistance. � On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby <jim@v-community.com> wrote: I have had this problem in the past, 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 | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
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, now when 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 the database 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 screen of death (wsod) problem that is usually caused by a php error.�
You will need to enable error displays and checking your server logs to help resolve the issue.
See https://drupal.org/node/158043�for assistance. �
On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby < jim@v-community.com> wrote:
I have had this problem in the past, 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 | 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/ ]
That I did not do. So I can re install things then update rules module 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, now when 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 the database 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 screen of death (wsod) problem that is usually caused by a php error.� You will need to enable error displays and checking your server logs to help resolve the issue. See https://drupal.org/node/158043�for assistance. � On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby <jim@v-community.com> wrote: I have had this problem in the past, 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 | 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/ ]
1. install rules module 2. run update.php 3. 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 rules module 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, now when 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 the database 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 screen of death (wsod) problem that is usually caused by a php error.�
You will need to enable error displays and checking your server logs to help resolve the issue.
See https://drupal.org/node/158043�for assistance. �
On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby < jim@v-community.com> wrote:
I have had this problem in the past, 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 | 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/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
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. 1. cleared cache twice 2. uploaded rules 7.dev 3. 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 1. install rules module 2. run update.php 3. 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 rules module 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, now when 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 the database 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 screen of death (wsod) problem that is usually caused by a php error.� You will need to enable error displays and checking your server logs to help resolve the issue. See https://drupal.org/node/158043�for assistance. � On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby <jim@v-community.com> wrote: I have had this problem in the past, 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 | 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/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
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.
1. cleared cache twice 2. uploaded rules 7.dev 3. 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
1. install rules module 2. run update.php 3. 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 rules module 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, now when 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 the database 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 screen of death (wsod) problem that is usually caused by a php error.�
You will need to enable error displays and checking your server logs to help resolve the issue.
See https://drupal.org/node/158043�for assistance. �
On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby < jim@v-community.com> wrote:
I have had this problem in the past, 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 | 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/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
No, but reading this thread others are having this problem. Too: https://drupal.org/node/2094879 Looks like creating owner column in the rules_config may be the fix, but why it is not working just don't make sence. -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Linda Romey Sent: Thursday, January 09, 2014 7:37 PM To: support@drupal.org Subject: Re: [support] updating rules module 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. 1. cleared cache twice 2. uploaded rules 7.dev 3. 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 1. install rules module 2. run update.php 3. 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 rules module 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, now when 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 the database 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 screen of death (wsod) problem that is usually caused by a php error.� You will need to enable error displays and checking your server logs to help resolve the issue. See https://drupal.org/node/158043�for assistance. � On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby <jim@v-community.com> wrote: I have had this problem in the past, 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 | 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/ ] -- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
Reading now, think I ran across this, but I am not putting the sight in maintenance mode at any time. -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Nancy Wichmann Sent: Thursday, January 09, 2014 8:13 PM To: support@drupal.org Subject: Re: [support] updating rules module Have you seen: https://drupal.org/node/2090511 Nancy
Well just rebuilt the db and tried the rules upgrade to 7.26 from 7.20 and still same thing. Guess I'm not needing the latest version of rules. This is taking way to much time I've spent two days going round and round, reading forums and trying different things with no success. I would like to thank you all for your help it is appreciated, but if a module is this hard to upgrade it is not worth it. All my other modules never had this problem. Maybe in the next update of rules 7,.27..... all though it looks like if I create the owner column in the rules_config table it may work, but phpmyadmin it not a friend of mine and the current screen reader I'm using. -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Nancy Wichmann Sent: Thursday, January 09, 2014 8:13 PM To: support@drupal.org Subject: Re: [support] updating rules module Have you seen: https://drupal.org/node/2090511 Nancy
For got to mention it only showed the two updates pending 7203 - Add a database column for specifying a queue item handler. 7204 - Rename rules_scheduler.state into rules_scheduler.data. And I know there should be more. -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Nancy Wichmann Sent: Thursday, January 09, 2014 8:13 PM To: support@drupal.org Subject: Re: [support] updating rules module Have you seen: https://drupal.org/node/2090511 Nancy
Found what I think is the fix, but I can not manually fix it cause I don't do phpmyadmin or drush and trying the dev build did not fix a thing, but looks like it is a missing table If I had step by step instructions I think I could handle phpmyadmin, but it has been a while. Here is the link and the error: Note I am upgrading from 7.20 to 7.2.dev Column owner not created in rules_config on update 2.3 to 2.5 ... https://drupal.org/node/2094879 I have also requested help there. Error message PDOException : SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base.owner' in 'field list': SELECT base.id AS id, base.name AS name, base.label AS label, base.plugin AS plugin, base.active AS active, base.weight AS weight, base.status AS status, base.dirty AS dirty, base.module AS module, base.owner AS owner, base.access_exposed AS access_exposed, base.data AS data FROM {rules_config} base WHERE (base.status IN (:db_condition_placeholder_0, :db_condition_placeholder_1, :db_condition_placeholder_2)) ; Array ( [:db_condition_placeholder_0] => 3 [:db_condition_placeholder_1] => 2 [:db_condition_placeholder_2] => 6 ) in EntityAPIController->query() (line 187 of /home/7/public_html/access/sites/all/modules/entity/includes/entity.controll er.inc). The website encountered an unexpected error. Please try again later. -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Linda Romey Sent: Wednesday, January 08, 2014 4:51 PM To: support@drupal.org Subject: Re: [support] updating rules module 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 screen of death (wsod) problem that is usually caused by a php error. You will need to enable error displays and checking your server logs to help resolve the issue. See https://drupal.org/node/158043 for assistance. On Wed, Jan 8, 2014 at 2:45 PM, Jim Ruby <jim@v-community.com> wrote: I have had this problem in the past, 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 | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
I now just uninstalled everything to do with rules and entity.api and re-installed and the sight crashed on install of the module. Guess this one is going on the back burner. I do have other sights running same modules using a later version of rules, but I'm not going to attempt to upgrade at this time. Steps: 1 clear cache 2 upload modules rules and entity 3. enabled rules and entity modules in modules area 4 once installation started the sight crashed. If there was a way to rebuild fresh sight and them put all my content back in it, I'd try it. Now for heck of it doing new install in test area to install rules. -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Jim Ruby Sent: Wednesday, January 08, 2014 1:45 PM To: support@drupal.org Subject: [support] updating rules module I have had this problem in the past, 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 | http://lists.drupal.org/ ]
Sites. On Jan 10, 2014 2:46 PM, "Jim Ruby" <jim@v-community.com> wrote:
I now just uninstalled everything to do with rules and entity.api and re-installed and the sight crashed on install of the module. Guess this one is going on the back burner. I do have other sights running same modules using a later version of rules, but I'm not going to attempt to upgrade at this time.
Steps: 1 clear cache 2 upload modules rules and entity 3. enabled rules and entity modules in modules area 4 once installation started the sight crashed.
If there was a way to rebuild fresh sight and them put all my content back in it, I'd try it.
Now for heck of it doing new install in test area to install rules.
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Jim Ruby Sent: Wednesday, January 08, 2014 1:45 PM To: support@drupal.org Subject: [support] updating rules module
I have had this problem in the past, 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 | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
Ok, I had a little rest and want to try and tackle this again, I just don't know where to begin. I've read just about every page on drupal.org about this problem and it seems I'm at a dead end. I'm wondering if I could do the upgrade manually and if so where would I get the sql to add it in myphpadmin. That I can handle. I just need the sql to paste it in the db. My steps would be 1. open phpmyadmin 2. select my test database 3 open the query window and paste in the sql for the upgrade. 4. upload the latest rules module at this time is 7.26 Other then this I'm at my last resort I just don't know what to try I'd like to thank everyone who have gave me suggestions and help. -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Jim Ruby Sent: Wednesday, January 08, 2014 1:45 PM To: support@drupal.org Subject: [support] updating rules module I have had this problem in the past, 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 | http://lists.drupal.org/ ]
When I am confronted with problems like this I usually create a new site on my development machine and add modules one by one until something breaks. That will give you an idea of where the problem lies. Good luck! Warren On Jan 11, 2014, at 1:31 PM, "Jim Ruby" <jim@v-community.com> wrote:
Ok, I had a little rest and want to try and tackle this again, I just don't know where to begin. I've read just about every page on drupal.org about this problem and it seems I'm at a dead end. I'm wondering if I could do the upgrade manually and if so where would I get the sql to add it in myphpadmin. That I can handle. I just need the sql to paste it in the db. My steps would be
1. open phpmyadmin 2. select my test database 3 open the query window and paste in the sql for the upgrade. 4. upload the latest rules module at this time is 7.26
Other then this I'm at my last resort I just don't know what to try
I'd like to thank everyone who have gave me suggestions and help.
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Jim Ruby Sent: Wednesday, January 08, 2014 1:45 PM To: support@drupal.org Subject: [support] updating rules module
I have had this problem in the past, 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 | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
participants (7)
-
Frank Nikola -
Gordon Heydon -
Jim Ruby -
Linda Romey -
Nancy Wichmann -
Tony -
Warren Keuffel