I have Colorbox and the plugin installed, and enabled.

enter image description here

The module is in the sites/all/modules folder, and the plugin is in the sites/all/libraries folder.

I've created a new content type and called it Image Gallery.

enter image description here

I've created a new field for that content type also called Image Gallery

enter image description here

The display format for my Image Gallery field is set to Colorbox.

enter image description here

I can create an image gallery, but the images are not opening in Colorbox. I'm stuck, the console isn't showing any errors, as far as I know everything is configured right but it's not displaying properly. What am I missing?

  • 1
    First, you can check your console for any errors. Sometimes it is due to jquery version conflicts which causes the problem. Try jQuery Update module and switch to different jQuery versions and see if it works for you.
    – echo
    Jul 3, 2015 at 5:43
  • @echo - The jQuery Update module did the trick. My install of Drupal is just the automatic GoDaddy install of drupal (probably should have mentioned that in the question), which I know doesn't provide the most recent releases of everything. Make your comment an answer and I'll accept it.
    – ShemSeger
    Jul 8, 2015 at 20:19

2 Answers 2


As per the comments:

JQueryUpdate Module solved the problem.

It Upgrades the version of jQuery in Drupal core to a newer version of jQuery.


This problem might occur because the path to library is incorrectly set. It is typically like so:


Though via /admin/config/media/colorbox it is possible to set some other path for it (within 'advanced settings').

There was a time (some older version in colorbox) that the solution was to correct the path to the Colorbox plugin directory, so that after unpacking it looked like so:


Refer to issue #1906156 for more details on this.

If that doesn't help, then check if there are any other modules that use Colorbox that are trying to find it on this path.

Of course, make sure also that the "permissions" to the plugin are set correctly (if no read access is granted, then that is probably what is causing the problem).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.