Bug #3282
closed
jQuery conflicts result in CB or 3rd party extension failing
Description
Due to different version of jQuery loading CB needs a deeper noConflict so CB can continue to function as normally.
Files
Updated by krileon about 12 years ago
- File 3282.patch 3282.patch added
- Status changed from Assigned to Resolved
- Assignee changed from krileon to beat
- % Done changed from 0 to 100
Proposed fix adds 2 new header functions to add custom html before all headers as well as after all headers. In addition to this it places CB in a deeper noconflict, caches previous jquery, redefines jquery to CBs jquery, loads in CBs jquery, then reverts jquery back to its previous values (if they exist, otherwise CBs jquery will remain as jquery). This allows CB to function without conflicting by other extensions jquery. Implementation is fully commented to further explain exactly what is happening.
Updated by krileon about 12 years ago
Updated by krileon about 12 years ago
- File 3282_rev1.patch 3282_rev1.patch added
Revision 1 uses existing functions without adding new functions to header.
Updated by beat about 12 years ago
- Status changed from Resolved to Closed
- Estimated time set to 4:00 h
r1761 and r1762 implement this patch in a slightly modified way to work also with CB modules on CB pages with same jQuery plugin, while keeping compatibility, and avoiding javascript warnings.
There is still a pending pull request for Joomla Framework pending to further improve non-conflicts between 3pds here https://github.com/joomla/joomla-platform/pull/736
Updated by beat about 12 years ago
r1780 Renames J_JQUERY_LOADED to CB_JQUERY_LOADED as we are now deep-non-conflict and wish to make sure we get our own one to avoid versions conflicts.