After installing the latest version of module (both 3 and 3.x-dev), the following message is displayed on the Shadowbox configuration page:
Shadowbox: A language file does not exist for your language: English (en). Tried to load: /languages/shadowbox-en.js. You can resolve this by either copying an existing language file and renaming the file or creating a new language file. Using either method you must use the 2-letter code for your language so the filename has the form: shadowbox-xx.js where xx is your 2-letter language code.
Moreover clicking on the "Test Shadowbox with the current settings" link, shows the Drupal test image on a new page - not in Shadowbox.
Comments
Comment #1
kirilius commentedThe second part was my mistake actually, I hadn't set the correct path to Shadowbox.
The language error message still appears after an install though. Good thing it doesn't stop Shadowbox from working.
Comment #2
janv commentedthis is how i fixed it:
i went to admin/settings/shadowbox, saved the current settings again, and then i ran update.php again.
Comment #3
janv commentedComment #4
aaron commentedThat is hardly 'fixed', as that message is enough to scare even a seasoned developer into not using this module. Especially considering the instructions in the message are flawed, as there is no "existing language file" to copy that I can find.
Comment #5
aaron commentedA more useful message might be telling the user the Shadowbox plugin is not yet installed, and where to find it, in case (like myself) they hadn't yet read INSTALL.txt.
Comment #6
RichieRich commentedI just can't get shadowbox to work at all. I got the language error message as described above so I installed the plugin in the directory specified in the install.txt:
sites/all/plugins/shadowbox-build-3.0b
However, no joy. According to the error messages shadowbox was looking for the language file in modules/shadowbox/shadowbox/languages. I therefore created modules/shadowbox/shadowbox/languages and added the contents of the folder in the plugins directory. The error messages disappeared, but I have no shadowbox functionality.
What kind of an install process is this? Not only is it not made clear that you have to install a plugin, but the plugin installation instructions don't seem to work at all. Can anybody help as the module itself looks great.
Regards,
Richard
Comment #7
psynaptic commented@aaron: I don't think it's really my fault that you didn't bother to read the INSTALL.txt.
I have changed the error message. It now reads "Shadowbox is not properly installed. Please check the status report"
When you go to the status report you get a more detailed report of what is wrong:
Third party Shadowbox software missing
In order for the Shadowbox module to work, the third party Shadowbox distribution should be downloaded and its location set. It is recommended to put the third party plugin in sites/all/plugins/shadowbox but the location can be changed in the settings. Currently looking for shadowbox in sites/all/plugins/shadowbox
Previously, I had a number of issues posted about why Shadowbox wouldn't work and it turned out to be down to a missing language file. These language files are in sites/all/plugins/shadowbox/languages and if there is a missing file (based on the current value of $language->language) Shadowbox fails.
I have decided that instead of trying to tell people to copy the language file and translate to their own language I will just default to English.
Marking as fixed but feel free to reopen if there is still a problem.
Comment #8
Steve Dondley commentedOK, so what's the fix for 6.x-3.0? Download the dev version? I can't get the thing to work no matter what I name my shadowbox directory in sites/all/plugins
Comment #9
Steve Dondley commentedOK, downloading the dev version and renaming the shadowbox directory in sites/all/plugins from "shadowbox-build-3.0b" to just "shadowbox" fixed the problem for me.
But since this is still a bug in 6.x-3.0, it should be left open until 6.x-3.1 is released with the fix in place.
Comment #10
pvasili commentedI think you should be released without this error!
Comment #11
psynaptic commentedIs the dev version in good enough shape for a release, that is the question.
Comment #12
psynaptic commentedI'm going to hold off until I commit #558146: Wrong path to sizzle.js and swfobject.js and see if there is anything in the queue I can add before I make a full release. Sorry about the wait.
Comment #13
psynaptic commentedI made a new release today.
Comment #14
psynaptic commented