I already had SCALD up and running. Then I 'just' added multi-language support (i18n) and now trying to add files I realized that the modal window doesn't work anymore. It does open, it shows "loading" with a progress bar – but it's neither loading nor making any progress. It's just stuck. Any help / pointers would be appreciated very much.
| Comment | File | Size | Author |
|---|---|---|---|
| Screen Shot 2015-03-18 at 16.24.42.png | 22.37 KB | tille |
Comments
Comment #1
nagy.balint commentedHi!
Adding i18n to the site should not cause any issues. However maybe you have done some modification on the scald entity as well?
Apart from that, you can check your console log (most browser have that), for any javascript errors, and copying the error for us would be helpful.
You can also check your dblog, or server log, for any php errors.
Comment #2
tille commentedyep, the console does actually show these two messages:
#1 "Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help http://xhr.spec.whatwg.org/
...A.onload=A.onreadystatechange=null;r&&A.parentNode&&r.removeChild(A)}}}r.insertB..."
jquery.js?v=1.4.4 (line 139)
#2 "uncaught exception: The editor instance "edit-body-und-0-value" is already attached to the provided element."
( I guess I'll do a fresh install nevertheless :[ )
Comment #3
nagy.balint commentedLet me know if the issue persists after a fresh install.
If it does, you can provide more information on how to reproduce the issue.
Comment #4
nagy.balint commentedComment #5
tille commentedFinally I did a fresh install over the weekend – and I think I can narrow the problem down a bit. It seems to have nothing to do with i18n or any other module. Instead my suggestion is, that there is actually a conflict between SCALD and the latest CKEditor.
The current situation is like this:
During the installation and setup process I tried to stick to the prcedure as it is decribed here: https://www.drupal.org/node/1775718 –– but a couple of steps I just couldn't match with the recommended descrition:
So far everything went fine and dandy – and until this point the modal window still works fine. I guess the above steps are necessary to have the (working) scald support without widget support. So this is what makes my above case (a) working – without widget support.
I then downloaded the latest CKEditor build with widget plugin enabled and continued with "CKEditor 4.3 Widget support" from the install descrition page (https://www.drupal.org/node/1775718).
So the above steps failed – but still I have scald items in the 'widget mode' – and a 'broken' modal window as described earlier.
The custom CKEditor build I used is version 4.4.7 (http://ckeditor.com/builder) and I added the blugin "widget" and "common widgets". Maybe SCALD is only compatible with 4.2.x ? I hope this issue can be solved somehow because I would really love to use SCALD. It seems to be quite powerful – and I suppose it would be very handyand easy to use for the editors. Please let me know if I can provide any other details about this issue... Thank you very much!
ps: one more detail: the firefox console shows this error "uncaught exception: The editor instance "edit-body-und-0-value" is already attached to the provided element." only when widget/button is enabled and modal window is not loading.
Comment #6
nagy.balint commentedYou need the dev version of scald to do the "CKEditor 4.3 Widget support", i will edit the document to be more clear about that.
Comment #7
tille commentedThank you for your reply!
Now I can do the steps I earlier marked with (X) – but the SCALD sidebar does not show any more and I get the following error message:
Warning: Unexpected character in input: '\' (ASCII=92) state=1 in /www/htdocs/.../sites/all/modules/scald/modules/fields/mee/mee.module on line 787what now? Thank you!
Comment #8
nagy.balint commentedMake sure that you have run the update.php, also that you have cleared the drupal cache, and the user cache.
Also that all the files got correctly updated, as generally that unexpected character should not happen.
Comment #9
tille commentedupdate.php didn't give me anything to update – and the caches are flushed. Also I dumped (renamed) the previous scald module folder and replaced it 100% with the dev version. Maybe now language support is interfering? I guess I'll try another fresh install... (argh)
Comment #10
nagy.balint commentedHmm upon having a closer look, it is complaining about the line
"\DOMXPath"
We never had this issue before, but then maybe it could be an issue with php version?
Apparently that command brings in a requirement to have php 5.3.3 at least. So then the dev requires higher php now :(
Comment #11
tille commentedThank you! I updated from PHP Version 5.2.12-nmm3 to PHP Version 5.3.18 and the error went away.
But now I'm again stuck with the previous situation: old nodes open the modal window correctly, but missing the scald button and the widget fundtionality. And new nodes have the widget fundtionality – but modal window is not loading.
Since I updated scald to dev version in both installs I now have the same situation in the fresh install and in the install with multi language support and other modules installed.
Comment #12
nagy.balint commented@tille
Is the input format correct on the old nodes? Like if ckeditor profile is set up for full html, and maybe on the old nodes the input format is set to filtered html or something else?
Generally there should be no difference between old and new nodes if they all use the same input format.
About the php version issue i will post a new issue: #2457707: Php version 5.3 is now required in dev
Comment #13
nagy.balint commentedThe module was tested extensively with ckeditor 4.4.6, not sure about 4.4.7 but since its a minor version, should not break anything.
Comment #14
nagy.balint commentedTested with 4.4.7, no issues.
Likely those JS issues you are having causes the problem. Just have to find how to reproduce.
Comment #15
nagy.balint commentedChecked "Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org/."
We can discard that for now, it does not cause any trouble for me.
So it must be the other JS error you have. Which does not happen for me.
Comment #16
nagy.balint commentedCant reproduce on firefox or chrome.
Can you tell me which browser are you using?
Comment #17
tille commentedChecking on the filter format brings this:
...while 'filtered html' did not have 'Embedded atoms' on and 'full html' did.
Trying to switch 'Embedded atoms' on/off didn't have any effect (cache flushed). Then unchecked the buttons "Scald SAS conversion" and "Scald DnD integration" in WYSIWYG-Profile for 'full html' since I was anyways a bit irritated that buttons are activated in two different prefs pages. The 'loop' is still the same as described above – only the images are not shown anymore when I view the node.
Comment #18
tille commentedI'm on Firefox 36.0.1 (Mac OS 10.7.5) (no noscript-plugin or thelike running)
Comment #19
nagy.balint commentedOkey just a note that the modal to add an image is in no direct relation to the wysiwyg or its configuration. Its two separate things.
What could cause an issue is, if you have a JS error, and maybe even JS aggregation, cause if you have a JS error in a script, that will block other JS code in that same script to execute.
So likely you have a JS error there related to your wysiwyg configuration, but it ruins other scripts, like the ctools modal implementation of the dnd library.
However the issue is i cant reproduce that JS error on firefox 36 on ubuntu.
We have to figure out what causes that JS error for you.
Comment #20
nagy.balint commentedThe "Embedded atoms" in the text format is a must to have for the widget integration.
Also in the ckeditor config only the " Scald Drag and Drop integration - CKEditor 4 widgets" should be checked. (and for me the "Plugin for inserting Drupal teaser and page breaks." but thats a core thing)
Comment #21
tille commentedYay! I think that was the right pointer!! As I mentioned in one of the above posts I was already a bit annoyed of declaring the buttons in CKEditor Profiles AND in WYSIWYG Profiles... Now I removed the editor from the 'full html' profile under admin/config/content/wysiwyg and the problem seems to be solved.
So I suppose the editor and/or the editor plugins were declared/loaded twice – which would also fit the error message I got earlier:
uncaught exception: The editor instance "edit-body-und-0-value" is already attached to the provided element.So maybe it would be helpful to mention that when using the SCALD in the recommended way, one should deactivate any previously activated editor under WYSIWYG Profiles (admin/config/content/wysiwyg) since it's now active through the CKEditor Profiles (admin/config/content/ckeditor/edit/). Or am I now completely missing something?
Comment #22
tille commentedps: that also explains why the modal did work in my 'filtered html' – there simply was no editor actuve for that WYSIWYG Profile... It just didn't work properly since I didn't have the "Embedded atoms" ect. active for the corresponding CKEditor profile… Hah!
Thank you very much for your kind and patient support!!
Comment #23
nagy.balint commentedAh glad its sorted :) And we have discovered a potential issue with php versions as well!
We usually only use the ckeditor, and the ckeditor module, and not using the wysiwyg module anymore.
Comment #24
tille commentedYep, so glad it's sorted! I was just about to have either another fresh install OR drop the hole idea of using SCALD... But I really want to use it – it seems to make so much more sence than any other approach i tried so far..
Maybe the wysiwyg-issue could also be one point worth mentioning on the installation guide page – at least since you might run into this re-declaration trouble if you happen to have any profiles defined via wysiwyg..
Comment #25
smsivaprakaash commentedI too got the same error, In my case both ckeditor and wysiwig module was enabled. So it result in this error. I disabled ckeditor module, since i use wysiswig .Problem solved.
Thanks!
Comment #26
oschuetze commentedI've had the same error, but without using the WYSIWYG module (ckEditor as library + module). My solution was to install the jQuery Update module.