On a test copy of one of my sites I was able to upgrade to drupal 6.10 without issue but when I attempt to upgrade to date 2.0 from 2.0-rc6 I get the following text on a white screen on any URL I attempt to load ( /, /admin, /user, ....).
Fatal error: Cannot access empty property in [snip]/sites/all/modules/date/date/date_handler_field_multiple.inc on line 127
I've run the update.php three times with no change and have tried several different copies of my production site which is www.thedirt.org. Again I'm seeing the above error on a test copy of my site and looking for suggestions on how to proceed.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | Event-content_type-export.txt | 21.52 KB | TallDavid |
Comments
Comment #1
les limIt looks as if this already being discussed at #302498: Event repeats in Views when date has multiple dates.
Comment #2
Toddv commentedI have found the same error and am starting to suspect a theme-related problem.
I am running Calendar, date, views, etc all the latest release versions for Drupal 6.10. Also running php 5.2.6
When upgraded calendar/date/views to the latest versions today I experienced a fatal error so restored to previous versions and re-installed one by one. So I was able to reduce the problem to the date module.
But I discovered that everything worked fine in the Garland Theme and would only break when I went back to my site's theme (Acquia Marina). Curious, I reverted to the old Date, ran update.php, re-installed date 6x2.0, update.php and tried all the other themes on my system (all are Drupal core themes). They all work, that is I do not get the error. It's not until I activate Acequia Marina that I get the error:
Cannot access empty property in /foo/sites/all/modules/date/date/date_handler_field_multiple.inc on line 127
I hope that is helpful in sorting this out, I don't even know where to begin to look.
My question would be - could this still be considered a date problem or is it a problem with the contributed theme?
Thank you
Comment #3
Toddv commentedAs far as I can tell, it's not a duplicate - thnx
Comment #4
karens commentedThis is interesting information, but the Garland theme is used during the upgrade, so messages that happen on upgrade should not be affected by the theme. But maybe you are seeing this message somewhere else? It's hard to tell. If you can create a reproduceable situation I can try to debug it. That means you need to be able to do a clean install, set the theme to the Acquia theme, create a date field (I need to know exactly what the field settings are -- kind of field, granularity, timezone options, etc), and then tell me where you see the error message.
I tried just switching to that theme and don't see this error anywhere, so I need more info.
Comment #5
TallDavid commentedI am also seeing this error on a site that was updated from 6.x-2.0-rc6 to 6.x-2.0.
Some additional observed behavior:
With the Date Repeat API module enabled, when I click "create content", I immediately get the error:
If I then disable the Date Repeat API module, this error does not occur, but, the CCK Time field for my Event content_type is not visible. Next, viewing the "Manage fields" screen for the Event content_type I see the following messages:
Since I only have a few test events setup, next I'll try Uninstalling/reinstalling the Date module. Please let me know if there is any specific troubleshooting that you would like for me to perform.
BTW, I'm using the Colorfulness Theme (6.x-5.1).
Comment #6
TallDavid commentedIn an attempt at troubleshooting, I preformed a complete uninstall of the Calendar & Date modules, downloaded fresh copies of 6.x-2.0 from Drupal.org and reinstalled. Behavior is the same as documented in #5 above.
An export of my Event content_type is attached.
Karen, please let me know if there is any specific troubleshooting that you would like for me to perform.
Comment #7
TallDavid commentedWith the Date Repeat API module enabled, the error also occurs when I go to a calendar display (e.g. http://example.com/calendar) or attempt to display a page containing a calender block. With the Date Repeat API module disabled, these errors does not occur. FYI.
Comment #8
TallDavid commentedProblem also occurs with Garland theme.
Problem also occurs with Date version = "6.x-2.x-dev" datestamp = "1235952291".
Comment #9
jpp commentedI'm having the same problem. However a virgin install (drupal 6.10 and the latest non-dev cck, date, views) does not show the symptom.
The line in question (127) is this
I cloned my broken system and added a print_r($node) just above the line in question in render()
and the same print_r for $this->aliases
So there is no $this->aliases['nid'] which is what's causing the Fatal error and the variable it's trying to set $node->nid is all ready set anyway (cloned from $values->nid)
I'm still digging to find out why this is different form a virgin install but I have a ton of modules installed.
Comment #10
jpp commentedI think I figured it out - I have both the value and the value2 (ie the end date) referenced in my view. If I just reference the start date it works with views outputting a date with a time range (eg "3 Mar 2009 1pm-3pm").Strike that - I forgot I had some code commented outComment #11
jpp commentedIf I uncheck group multiple values it works if I check it (including on my virgin test system) I get the error.
Comment #12
TallDavid commentedConfirmed. Deselection of "Group multiple values" for Configure field Content: - value on my Views configuration screen (/admin/build/views/edit/upcoming_events) results in the error no long occurring.
Hopefully this is enough to point our hard working code mavens in the right direction!
Comment #13
Toddv commentedSo, TallDavid, just trying to understand: you revert to a pre Date2.0 installation, deselect to "group multiple values" in your view, then proceed to upgrade to Date2.0?
Thanks - ToddV (from #2 above)
Comment #14
TallDavid commentedTodd,
no, using Date 6.x-2.0, I deselect "Group multiple values" in the view, and the problem no longer occurs.
Comment #15
Toddv commentedI concur that the issue is no longer occurring when "Group Multiple Values" is not selected in any of my calendars. But I'm not sure if the fact that it's not happening has a cause/result relationship or if something else changed...
So to elaborate on what I did to apparently fix this error:
I have three different calender views, each with multiple displays. Only one display in each view has a field with a type that allows the toggling of the setting to "group multiple values". It's a CCK date field. So before upgrading to the latest Date I made sure that "group multiple values" was deselected in each of these displays. Update.php gives an error on the first run-through but running it a second time seems to get everything shipshape.
Thank you!
TV
Comment #16
karens commentedUpgrade to the latest version of CCK. Pretty sure that is the source of the problem.