Closed (won't fix)
Project:
Date
Version:
6.x-2.5
Component:
Date API
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 May 2010 at 11:14 UTC
Updated:
16 Aug 2010 at 09:18 UTC
Jump to comment: Most recent file
Comments
Comment #1
t3hk0d3 commentedbump
Comment #2
t3hk0d3 commentedbump
Comment #3
karens commentedI wish someone had tested this. I assume it fixes unicode but need to make sure nothing else breaks. I went ahead and committed it with a doc note to watch the changes.
Comment #4
dboulet commentedGetting these errors on fresh install of Drupal, using date CCK field:
Reversing the change proposed here fixes the issue.
Comment #5
Ardshael commentedI also ran into this error today. Drupal and all modules are updated.
I wasn't using the jQuery before and just installed it today. Before that was installed it was working. I haven't started testing to see if disabling it will make it work again yet.
Comment #6
arlinsandbulte commentedI confirm #4. Reverting back eliminates the errors.
Comment #7
arlinsandbulte commentedPatch to revert above changes attached.
Comment #8
arlinsandbulte commentedSteps to reproduce the error:
Drupal 6.19 clean install, CCK 6.x-2.8, Date 6.x-2.5, jQuery UI 6.x-1.3
Applying the patch in #7 makes the errors go away & node is saved.
Comment #9
arlinsandbulte commentedI reverted this change back and committed the fix:
http://drupal.org/cvs?commit=407136
Once the -dev tarball is updated, that should include this fix. Or you can grab it straight from CVS now.
Warning! This is my first ever Drupal CVS commit. I hope I did not mess things up even worse!
Thanks for trusting in me, Karen
Comment #10
karens commentedThis looks like a serious problem, I may need to do a new release.
Arlin, the patch is perfect, please go ahead and make the same change to the D7 version.
Comment #11
karens commentedChanging status.
Comment #12
karens commentedI rolled a new release, 6.x-2.6. This looks potentially serious enough that I want to get a new release out before other people make the upgrade. We hit a quiet time on Friday night with the first release, so hopefully not too many people will have already done this and everyone else will see the later release.
Comment #13
dboulet commentedAre we sure that this should be marked as fixed? Has the original issue been addressed?
Comment #14
karens commentedOnly one person reported any problem in the beginning and no one else ever confirmed either the problem or the fix. And then the proposed fix broke everything. If someone can confirm the problem and there are at least a couple people willing to figure out a fix that does not break other things we can work on a fix. Otherwise it appears to be something so little used that only one person cared about it.
I certainly don't have time to try to figure out how to fix something I don't use.
So I guess I will say won't fix unless there is more interest.