Blank site on upgrade to 0.21
Thu, 21/05/2009 - 19:44
I'm evaluating PP on a local Wamp install.
I've had PP-0.19 running fine and had added a few customisations to the default example site (a couple of custom content types and a few modules, plus my own theme). On upgrading to PP0.21 the site is blank on most pages. Backend appears to work fine. No error massages or anything untoward.
Accessing Editions or Channels results in a blank page. Content on a simple blog (My Blog) appears fine. i'm also unable to access editions manager or story manager. Some stories are accessible and editable, some are not. I don't see any pattern to what is accessible and what is not,
Obviously this is not critical since it's only a barely customised evaluation install. But it doesn't exactly inspire confidence. ;-)
Any suggestions?
Ian
Thu, 21/05/2009 - 21:31
#2
Ah, yes there are some
Ah, yes there are some errors:
[21-May-2009 13:33:24] PHP Notice: Undefined index: q in C:\wamp\www\pp\includes\path.inc on line 164
[21-May-2009 13:34:14] PHP Fatal error: Call to undefined function _pp_extended_status_select() in C:\wamp\www\pp\profiles\prosepoint\modules\cck\content.module(1646) : eval()'d code on line 2
Error 2 appears repeatedly. Error 1 just a couple of times.
This is on Vista.
Thu, 21/05/2009 - 22:07
#3
Did you run update.php?
Hi,
Did you run update.php at the end of the upgrade process to 0.21?
ProsePoint 0.21 removes the CCK field field_extended_status from story nodes, and it is a setting for this field which is invoking _pp_extended_status_select() and hence, triggering your fatal PHP error.
Fri, 22/05/2009 - 01:39
#4
Yes, I ran update PHP. It
Yes, I ran update PHP. It didn't throw any errors.
Fri, 22/05/2009 - 09:37
#5
I presume that, after running update.php, you still have this pr
I presume that, after running update.php, you still have this problem. The update was supposed to delete the CCK field field_extended_status from the story content type.
On your site, can you please visit .../admin/content/node-type/story/fields, and tell me if you see a row in the table with field_extended_status in the Name column?
The other thing that might be causing this is if you have overridden any ProsePoint-defined Views which are now outdated for version 0.21.
Fri, 22/05/2009 - 23:51
#6
Aha! The
Aha! The field_extended_status had been deleted from the 'story' content type, but it had not been deleted from my custom content type 'projekt' which is a copy of the 'story' content type. Deleting the extended_status field from 'projekt' content-type seems to have cured the problem.
Sat, 23/05/2009 - 11:56
#7
In that case, you probably
In that case, you probably want to edit field_extended_status for your custom type so it doesn't call _pp_extended_status_select(). Maybe define your own allowed values?
You might even want to rollback your site, make this change, and then upgrade to 0.21.
And depending on what you using field_extended_status for, you might want to look at the new Workflow module incorporated into ProsePoint 0.21.
Hi,
Can you please check your PHP error logs for any error messages? A blank screen can indicate exceeding PHP's memory_limit or max_execution_time.
Also, is this on Vista or XP or something else?