Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
when enabling the Nodejs/AJAX Framework (req by watchdog) it stops parts of cck working, mainly the image and link options, when trying to either add a new image or edit an existing img details by double clicking on the image, it just says 'loading' and sits there, it I uninstall the Nodejs/AJAX Framework part it all works again as intended.
bug report over, hope I did it right
thanks
Comment | File | Size | Author |
---|---|---|---|
#3 | screenie.png | 150.27 KB | kokrull |
Comments
Comment #2
glekli CreditAttribution: glekli commentedI'm not exactly sure what you mean by 'cck not working'. What do you mean by image and link options? Image and link fields on the node edit page?
Could you please provide steps to reproduce on a clean Drupal install, and a screenshot of the malfunctioning element?
Comment #3
kokrull CreditAttribution: kokrull commentedyeah easy to replicate install drupal
over to drush
sudo drush dl nodejs
sudo drush en nodejs nodejs_config nodejs_watchdog
The following extensions will be enabled: nodejs, nodejs_config, nodejs_watchdog, nodejs_ajax
Do you really want to continue? (y/n): y
nodejs was enabled successfully. [ok]
nodejs_ajax was enabled successfully. [ok]
nodejs_config was enabled successfully. [ok]
nodejs_watchdog was enabled successfully. [ok]
to the web site
create or edit a page, press the icon on the editor to load an image wait while it says "loading" and wait, and wait.... etc
https://www.drupal.org/files/issues/screenie_4.png
edit to add
once the nodejs watchdog is uninstalled (gui) the editor works as expected
Comment #4
kokrull CreditAttribution: kokrull commentedJust an FYI
Setting up for evaluation on https://simplytest.me/ with the above enabled gets the same result so not specific to my setup.
Comment #5
kokrull CreditAttribution: kokrull commentedSomewhere between the original post and now, as of Drupal 8.4 this has become fixed (ain't these the best kind of fixes), so you might want to move it to fixed status as I don't know how.
Thanks