JQuery conflict in edit mode
Because the conference site uses JQuery and Aloha does as well, we have a conflict in the Content View's iFrame because JQuery is loaded twice. The result is that you can't edit content, for example on the homepage.
We will have to solve this anyway, but how? What if the site uses a different JQuery version than Aloha? Then making sure that JQuery is loaded only once doesn't help alone.
#4 Updated by Karsten Dambekalns about 9 years ago
- Assignee changed from Karsten Dambekalns to Christian Müller
Could this be helpful? http://stackoverflow.com/questions/2228006/how-do-i-avoid-including-jquery-twice
#5 Updated by Bastian Waidelich about 9 years ago
I quickly talked with Christopher about this:
The (easiest) way to go, is probably not to avoid loading the library twice but to make sure that both versions work together. This could be achieved by using jQuery in "noConflict" mode before using it for Aloha and "resetting" $ afterwards, so that the original scripts of the site work without adaption.
#6 Updated by Sebastian Kurfuerst about 9 years ago
+1 from my side for jQuery noConflict mode. Do we need this in Aloha or can we do it ourselves?
If it is needed in Aloha, we can't do it right now as they are in a middle of a restructuring of the code... So we currently can NOT update the Aloha version.
Later, once their restructuring is done, I can work out the details with the Aloha people and commit the solution there.
#7 Updated by Christian Müller about 9 years ago
- Priority changed from Must have to Could have
I have looked into it and from a website implementors perspective we should have Aloha use the noConflict mode. As I guessed that wouldn't be possible right now due to time contraints I will change the site JS to use noConflict if I have time. But I think it isn't any longer "must have" for launch as we won't use the backend right away.