Closed (fixed)
Project:
Date
Version:
6.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
24 Jan 2009 at 01:13 UTC
Updated:
3 Jan 2014 at 00:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
SaxxIng commentedSame to me too!
Saxx
Comment #2
terrychild commentedMe to - just upgraded from previous dev version.
I have an 'event' content type with a CCK date field and the warning occurs only for the 'Upcoming Block' display of the attached view.
Regards
Terry Child
Comment #3
bonobo commentedI saw this with the dev version -- uninstalling the dev version, and reverting back to rc 6 eliminated the issue.
Comment #4
choster commentedI get a completely different set of warnings (db name "library") upon running update.php, which may or may not be related:user warning: Table 'library.date_format_types' doesn't exist query: SELECT dft.type, dft.title, dft.locked FROM date_format_types dft ORDER BY dft.title in /usr/www/sites/all/modules/date/date_api.module on line 1857.Never mind, the previous, which seems to have cleared up after the third time I ran update.php . Unfortunately, now I [i]am[/i] seeing the line 85 error.
Comment #5
junro commentedAfter dev 26/01
Be careful, you have to run update.php 2 times.
Comment #6
junro commentedwarning: Attempt to assign property of non-object in /www/sites/all/modules/date/date/date_handler_field_multiple.inc on line 85.
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '= users_comments.uid WHERE (.status <> 0 OR .uid = 7 or 1 = 1) AND (.type in ('' at line 3 query: SELECT COUNT(*) FROM (SELECT uid FROM users users LEFT JOIN users users_comments ON .uid = users_comments.uid WHERE (.status <> 0 OR .uid = 7 or 1 = 1) AND (.type in ('fiche')) ) count_alias in /www/sites/all/modules/views/includes/view.inc on line 699.
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '= users_comments.uid WHERE (.status <> 0 OR .uid = 7 or 1 = 1) AND (.type in ('' at line 14 query: SELECT uid, timestamp, subject, cid, nid, field_titre_france_url, field_titre_france_title, field_titre_france_attributes, type, field_annee_value, name, homepage FROM users users LEFT JOIN users users_comments ON .uid = users_comments.uid WHERE (.status <> 0 OR .uid = 7 or 1 = 1) AND (.type in ('fiche')) ORDER BY DESC LIMIT 0, 5 in /www/sites/all/modules/views/includes/view.inc on line 725.
Comment #7
junro commentedGot this too:
Parse error: syntax error, unexpected $end in /www/sites/all/modules/date/date_repeat/date_repeat.module on line 203
Comment #8
junro commentedGo back to the old version get still some errors, I had to restort a backup.
Comment #9
szy commentedThis update made a complete disaster in my views, and yes - there was info
about converting views after upgrade.
It changed my node types defined in views, number of displaying items, deleted
relationships... It looks like it copied one of my kind-of-event views to other
non-events views... Ugggh.
Szy.
Comment #10
SaxxIng commentedSame to me too!
All custom views are corrupted!
Saxx
Comment #11
junro commentedI decide to wait a little before to install a new dev version now lol
The Best thing to do is to wait a new recommended version I think.
Comment #12
karens commentedI just removed the code that was trying to update Views from the update in case that is breaking things. I can't replicate the original error, though, so I have to investigate that. Sorry!
Comment #13
karens commentedWell all these errors are views-related, so that fix may take are of everything. I'll keep an eye on it, but please report back if you still have problems after picking up the code with this fix.
I tested that change, I really did, so I don't know why it didn't create those problems for me.
Comment #14
cps@groups.drupal.org commentedPath and arguments are empty, and I get filter from calendar in different other views (glossary) and somtimes an ajax error.
Ok, the views working, after I edit the settings or restore the view, but I lose all my modifications.
Comment #15
szy commented@Karen, now upgrade went fine, thanks.
We still need you here - could you please look into it...? :] Thank you.
Szy.
Comment #16
jvieille commentedWith the dev of the 26th, my site was totaly messed up: views references get other ones, menu items linking to views disappearing, Imppossible to fix, having to start from a backup.
Do you think that this is solved now?
Comment #17
szy commented@jvieille, yes, there is no views' converter what was views' destroyer in fact.
I have it tested and worked on it. It's safe, imho.
Szy.
Comment #18
Aquilasfx commentedi have the same warning... date_format_types' doesn't exist query: SELECT dft.type, dft.title, dft.locked FROM date_format_types dft ORDER BY dft.title in /Users/lucky/www/drupal-6.9/modules/date/date_api.module on line 1857.
Comment #19
amccoy commentedI have installed Date 6.x-2.x-dev (2009-Jan-26) and am also getting the following error on my view:
warning: Attempt to assign property of non-object in /var/www/vhost/baystreetsh/theatre/sites/all/modules/date/date/date_handler_field_multiple.inc on line 85.
I even re-created the content type & view scenario after I ran update.php
I only seem to get this warning on the newly created content types with the Datetime CCK field -- other content types that I had created before I updated the module from 6.x-2.0-rc6 (2008-Dec-02) seem to not display any similar warnings.
Should I revert back to 6.x-2.0-rc6 (2008-Dec-02) -- or is there an imminent fix?
Comment #20
choster commentedPossible duplicate at #364740: Date module has a problem unsetting the views.
Comment #21
momper commentedwarning: Attempt to assign property of non-object in modules/date/date/date_handler_field_multiple.inc on line 85.
same like#19
Comment #22
RicardoJBarrios commentedAlso same like #19, and commenting // unset($node->view); doent's seems to work.
Comment #23
choster commentedThe code that caused the error was removed from the current dev. But if you installed the "bad" update, it seems simply updating to the newest dev does not remove the error; I tried that in combination with rebuilding the views, clearing the views cache, and making a null edit. I could only clear the error by deleting all date fields from the view and adding them anew.
Comment #24
thepanz commentedI've got the same issue. Latest -dev for Calendar and Date modules.
Warning showed after adding a date-field into a custom view:
Comment #25
szy commentedHi there, maybe it could be a hint to solve this:
when adding sort criteria, date fields are properly described with value and value2:
-> http://drupal.org/files/issues/date_add_sorting.gif
... but when adding field, there is no value descriptions:
-> http://drupal.org/files/issues/date_add_field.gif
It could be a small mistake only here, or maybe a reason of another misleading
somewhere in the code? Just thinking loudly.
I have got rid of this error by... removing all function render($values) from the code
(lines 80-87). Haven't seen any negative consequences for my site.
Szy.
Comment #26
szy commentedComment #27
pletcher commentedThis patch works for me. I'm not sure if this is correct, as I do not use Date extensively, but thus far I don't see any problems as a result of it.
Hope this helps, any feedback is welcome.
Comment #28
steveparks commentedThat patch worked for me on 6.9 and dev version of date module as of today (5th feb)
Thanks
Comment #29
choster commentedMarked #370002: Warning message from date_handler_field_multiple.inc as a duplicate.
Comment #30
karens commentedFixed it differently -- needed to initialize the empty value as an object, not an array.
Comment #31
szy commentedThanks Karen, works fine.
Szy.
Comment #32
rick hood commentedSame here, works for me.
For those who need more instructions:
sites/all/modules/date/date/date_handler_field_multiple.inc on line 84
change this:
to this: