Closed (outdated)
Project:
FullCalendar
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
26 Nov 2011 at 13:39 UTC
Updated:
6 Nov 2023 at 18:28 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tim.plunkettSorry for the delay!
Can you try this patch and see if it helps?
Comment #2
Anonymous (not verified) commentedI'm afraid it doesn't. With the patch it appears as
All's Well That Ends WellComment #3
tim.plunkettWow, so that makes it even worse! Back to the drawing board.
Comment #4
tim.plunkettReferences is going to be deprecated in favor of http://drupal.org/project/entityreference, can you reproduce the bug with that module?
Comment #5
aspilicious commentedCan we try filter_xss ??
Comment #6
tim.plunkettTurns out there was a new method added to views recently that gives us the un-rendered title, which is what I think we want.
Comment #7
aspilicious commentedWorks great but needs a dependency test on views stable.
RTBC for me
Comment #8
tim.plunkettIt turns out this breaks the ability to rewrite fields to use a the title, which is a huge feature.
Instead, let's just run the opposite of check_plain. The plugin doesn't expect escaped HTML, so we can't give it escaped HTML.
Comment #9
aspilicious commented:)
better, much better
Comment #10
tim.plunkettAwesome!
http://drupalcode.org/project/fullcalendar.git/commit/f55b2ef
Comment #11
tim.plunkettAs a follow-up, I just figured out what was happening.
Since the title is passed as an attribute of the link, that the plugin uses to make the event, drupal_attributes was calling check_plain on it anyway.
Comment #13
Anonymous (not verified) commentedI just updated to 2.0-beta3 and all is looking great, so thanks guys.
Comment #14
brandenlhamilton commentedThe attached patch simply back-ports the solution in #8 for the 6.x-2.x version of this module.
Comment #15
christianchristensen commentedLooks good to me
Comment #16
heddnVersion 6.x of this module is no longer actively supported. Closing out tickets against that version. If this is still an issue in an actively supported version of this module, feel free to re-open and provide steps to reproduce the issue.