Hi,
Couldn't work out why, otherwise I'd love to help, but enabling Shadowbox 6.x-1.x-dev removes all the navigation of IMCE 6.x-1.1.
By Navigation, I mean:
* Upload
* Thumbnails
* Delete
* Resize
* Send to FCKEditor
Looked at this for ages, totally confused.
This exact same bug report has been posted to both Shadowbox and IMCE modules.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | shadowbox_6_that_worked.zip | 27 KB | armanatarchispot |
Comments
Comment #1
psynaptic commented6.x-1.x of this module is dated. It has only the most basic of features and shouldn't be considered ready for production use. I'm going to be porting 5.x-2.0 to 6.x-2.0 and probably won't be porting 5.x-1.0 to 6.x-1.0 since that's the old Shadowbox release.
Could you perhaps try out version 5.x-2.0 with IMCE and report back if that works? Any info will help.
Comment #2
armanatarchispot commentedHey mate,
I uploaded 5.x-2.0 as per your request, and I went to enable it in "Admin - Modules" but I get this:
[Red Cross] Shadowbox 5.x-2.0 A JavaScript modal media viewer application
This version is incompatible with the 6.4 version of Drupal core.
Comment #3
armanatarchispot commentedHi,
Bit of Further information;
I'm using Core 6.4
and Shadowbox doesn't work at all now... Though I've used it in a few sites,
e.g.
http://www.space43.com.au/?q=node/9
I'm double checking my coding to make sure it isn't me...
Also, I noticed that an older version of Shadowbox 6.x-1.x-dev I had dowbloaded (which works) had more files in it than the new one (including galleries etc etc)...
finally, I've tried JQuery update, but no luck...
Comment #4
psynaptic commentedYou look new to Drupal so I'll be gentle.
5.x and 6.x denote compatibility with those versions of Drupal core. 2.0 and 1.x denote versions of the module.
The bottom line is that 5.x-2.0 won't work with Drupal 6, only Drupal 5.
I'm an experienced developer and have yet to build a client site in Drupal 6. I would not use a -dev status module in any production sites unless I know it works 100% for the purpose it is required. Modules with -dev in the version string are development versions and are much more likely to contain bugs, security holes, untested new features etc. In this case it contains old, stale code that's not fit for use.
I recommend either going back to 5 or waiting for a stable release.
Comment #5
armanatarchispot commentedHey mate,
I'm actually not so new, funny I left that impression but! But definitely not a developer like you! Thank you for the friendly reply all the same, that's what I love about our 'free' software community!
Anyway dude, I'm aware of the difference betwen "5.x and 6.x" etc but I tried hacking it so they'll get along, no luck... so I downloaded the 6.x-1.x-dev one which I already had running on
http://www.space43.com.au/?q=node/9
(as the one I got most recently from drupal didn't work) and then uploaded it to the new site, which now also works!
see:
http://uto.com.au/site001/node/4
I've attached that (less the shadowbox/shadowbox) to this email.
Let me know if there's anyway I can help out upgrading the module, e.g. testing etc. I'm not a php king but will try to help too.
Comment #6
psynaptic commentedThanks for the offer and user testing is definitely an area that needs outside help.
Comment #7
Tony Sharpe commentedSubscribe
Comment #8
psynaptic commentedCan someone please confirm this is still an issue?
Comment #9
austintnacious commentedHi!
I can't confirm that this is still an issue but this is the closest thread I've found to the question I have!
Is it possible to intergrate Shadowbox with FCK and IMCE in the same way it appears to be possible to integrate other combos of WYSIWYG editor, image upload and lightbox type displays?
If you tell me it is / how then I'll go ahead and install and test.
I've had a quick look and at the moment I do not see a way in either the FCK or IMCE interfaces to add the rel="shadowbox" attribute.
I know I could do this manually in the source code but I'm trying to come up with a solution for my editor users who I don't want to look at / edit source code.
Thanks in advance for any answers. . .
Comment #10
psynaptic commentedI'd also like this feature. I just don't have time to look into the best way to achieve it.
It would probably be done via JavaScript if it can't be added via a custom WYSIWYG button.
Comment #11
austintnacious commented@ psynaptic
Are you the maintainer of the Drupal Shadowbox module?
Does that mean you write the necessary code?
I went ahead and installed the shadowbox module and shadowbox 2.0 and I do NOT see any conflict with IMCE (at least when using IMCE via FCK, I am not using the IMCE CCK field so cannot say if there's a problem there)!
My set up is as follows. . . D6.9, IMCE 6.x-1.1, Shadowbox module 6.x-2.1 and Shadowbox 2.0 (full distribution).
What I can say is that using the global setting has worked for me, clicking on my thumbnails now opens the enlargements in Shadowbox!
YAHOO!
BTW, I think the wording for this on the Shadowbox admin pages is misleading "Global Kill Switch" with checkbox checked seems to mean the opposite thing to me, i.e. checking the box next to the words "Global Kill Switch" sounds like it should have the effect of turning of the global shadowbox effect.
Something that should probably be made clear(er) in the documentation is that you'll probably need to clear caches for it to work.
I have cahcing and css / javascript optimization / flattening switched on in Drupal Core's Performance module.
At first Shadowbox was not working, I cleared caches, experienced the site going very slow, infact some pages timed out and I was worried that maybe Shadowbox had broken my site, but as the caches got built up again or whatever everything started to work just fine!
Another thing that should be made clearer in the documentation is that when you download Shadowbox 2.0 (full distribution) and un-zip.
The resulting directory is called ./shadowbox-2.0, that'll need to be uploaded and renamed to ./sites/all/modules/shadowbox/shadowbox (removing "-2.0")
So this thread can probably be marked as fixed!
I wonder if it might be worth switching it to feature request though but I'm not really sure how that works.
I'm not a programmer so I don't know if this is possible but it seems to me like Shadowbox integration would be easier and more flexible in the Drupal context if Shadowbox was invoked via an id="" or class="" attribute rather than rel="". . . (hope that makes sense)
Comment #12
psynaptic commentedI've changed the Global kill-switch as this was misleading. It now just reads: Enable Shadowbox.
The INSTALL.txt already has the line:
3. Extract the download, rename the shadowbox-2.0 directory to just 'shadowbox' and place it inside the shadowbox module directory.I have added a note to INSTALL.txt to clear cache if it isn't working.
Comment #13
SophieG commentedHi,
i can confirm that it is still an issue for me : shadowbox is creating some trouble with IMCE (no more buttons...).
Anyway, i also saw taht you're having an issue with the rel attribute. I have found a solution, i know it is not the best one because it makes you modify a bit the fckeditor source but it is the only simple way i have found to offer my users a rel attribute (and not be forced to get into the code). Anyway, her is the link : http://drupal.org/node/373467
Comment #14
psynaptic commentedAhh ok, sorry for marking as fixed then.
Thanks for the info on FCK.
I'll try to find some time to set up a test site and figure out this issue. If you can provide any debugging info that would be awesome.
Comment #15
psynaptic commentedClosed to clear queue. If anyone comes up with a patch for this then please reopen this issue.