I set the module to turn off but the splash window continues to open
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | splash_never-means-never_320067.patch | 3.1 KB | sirkitree |
| #6 | splash.module.patch | 734 bytes | seanr |
I set the module to turn off but the splash window continues to open
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | splash_never-means-never_320067.patch | 3.1 KB | sirkitree |
| #6 | splash.module.patch | 734 bytes | seanr |
Comments
Comment #1
seanrDo you have caching turned on? Try flushing the cache and testing again.
Comment #2
seanrGoing to assume that was it. If not, please reopen with more info.
Comment #4
greenmachine commentedIn my opinion, this is an existing and valid bug with Splash 6.x-2.5. I've witnessed this behavior on two sites. Steps are essentially:
-- enable splash module
-- set the "what"/"how" to display a static chunk of HTML (pasted into the config field)
-- set the "when" to once a week or once a session
-- splash page starts appearing for new visitors (redirected to domainname.com/splash)
-- set the "when" to "never" (in my cases a couple weeks later)
-- splash page continues to appear for new visitors (again, redirected to domainname.com/splash)
On the most recent site, Drupal caching is turned on ("normal"), with page compression and block cache enabled, css optimization disabled and javascript optimization enabled.
I have not investigated to try to figure out the mechanism. I did try flushing caches with the button on the Performance settings page: that did not seem to have any effect. Workaround in my case is to disable the module.
Comment #5
codewatson commentedIt looks like the culprit might the frequency logic of the splash.module.
starting at 102:
Before it does any checking for the frequency, it checks to see if there is a cookie, and if not sets splash to display and ignores the rest of the frequency logic.
Not sure yet what the best logic for this section of code would be...
Comment #6
seanrThis patch should fix it. Can you give it a try?
Comment #7
sirkitree commentedSame issue, but the patch isn't working for me. IMHO 'never' should be all inclusive, whether there is a cookie or not.
Comment #8
capellicSame problem in 2.6 and 2.7. Never means off.
Comment #9
sirkitree commentedAh, right - sorry - i missed changing the version number. Should have done against -dev too, but looks like this applies.
Comment #10
mail@victorquinn.com commented@sirkitree patch committed! Thanks!!