Hi there,

when I upgrade from 6.x-2.6 to 6.x-2.7 the caching issue is solved, but the thick box integration does not work anymore. Downgrading back to 6.x-2.6 solves the issue...

Comments

jcl324’s picture

jcl324
he/him
Primary language English
Location Portland, OR
commented

I concur, Thickbox 1.6 not working with 2.7. I have new install of D6, installed both modules, and all I get is a horizontal bar that seems to be trying to open the window with my splash node in it. Frustrating that all answers in the Thickbox issue queue seems to be "upgrade to colorbox", but will not help us here with Splash.

capellic’s picture

capellic
he/him/his
Location Austin, Texas
commented

Fresh install.. reverted back.. not working.

sanpi’s picture

sanpi commented

Used hook_boot instead of hook_init is probably not a good idea.

In my case, the module Thickbox doesn't exists (http://drupalcode.org/project/splash.git/blob/HEAD:/splash.module#l182) because the module list contains only two modules.

Change the module weight can probably bypass the problem, but hook_init is the right place to do this.

millions’s picture

millions commented

Thickbox isn't working for me after upgrading also.

pierre_cotiniere’s picture

pierre_cotiniere commented

Same problem, revert to 6.x-2.6 and it works with thickbox.

rheo’s picture

rheo commented

How can I get a copy of 6.x-2.6 ?

I need the thickbox functionality. But it also needs to work with caching..

Has anyone found a solution to this yet?

patrickroma’s picture

patrickroma commented

Is this module still maintained?

envirodefence’s picture

envirodefence commented

We had the same problem, so disabled the module I uninstalled splash, removed the module files, and installed the dev version instead. It seems to be working properly again.

Not sure what is going on here, but I highly recommend giving the dev version a try.

mail@victorquinn.com’s picture

mail@victorquinn.com commented
Status: Active » Closed (fixed)

@patrickroma it is now!

This works in the latest version, so I'm marking this as fixed. If it presents itself again, please open a new issue.