I'm finding that while I'm able to see it in the browser that I've been using as User 1, in all other browsers on Mac and PC that I've visited my site while it's in maintenance mode, the countdown timer's numbers never show up. The page loads and completes loading, the maintenance message shows up, even the countdown timer's layout with weeks/days/hours/etc. show up, but no numbers.

I'm wondering if this module is simply abandoned as it doesn't have a green-lit release anyway and the last release was 48 weeks ago.

Any idea on my issue and a proper release? I definitely like the idea of this module, just doesn't seem I'll be able to use it since I'm unable to really get it to work. Maybe it's a conflict with another module, maybe not.

Does this module require that a user has to have already signed-in and some cookie saved to work? Just a thought.

CommentFileSizeAuthor
#6 Maintenance_Countdown_ERROR.php_.html_.zip11.13 KBdeanflory

Comments

deanflory’s picture

deanflory commented

FYI, tested and failed on:

Mac Firefox

Win Vista IE
Win Vista Firefox
Win Vista Safari

Was able to see it working on Mac Safari though I'm wondering if that was because of some cookie or other data that's been stored from using it to develop the site.

EllECTRONC’s picture

EllECTRONC commented

Yes, it's about JS conflict. Will be fixed ASAP.

EllECTRONC’s picture

EllECTRONC commented
Title: Doesn't Work » Doesn't Work D6 + D7 + JS conflict + HEAD
Version: 7.x-1.1 » 7.x-1.x-dev
Priority: Critical » Normal
Status: Active » Closed (fixed)

Fixed in all tags. Released new releases for drupal 6 and 7, but I don't know why these still generating and not shows up at project page.

All Releases for Maintenance Countdown http://drupal.org/node/1286070/release

For D7 you can use 7.x-dev absolutely safe. Or for both D6 and d7 just replace js file with this. D6-dev has not yet been renewed, don't know why.

deanflory’s picture

deanflory commented
Status: Closed (fixed) » Needs work

Tried v1.2, no difference, didn't display the countdown numbers on all the same browsers except Mac Safari that I was logged into where I was able to see them at the bottom of the update.php results page.

Tried dev also, same, no apparent change from the previous non-working version.

Even tried a full cache flush, still nothing. :(

EllECTRONC’s picture

EllECTRONC commented
Status: Needs work » Postponed (maintainer needs more info)
  1. What template you see in maintenance mode?
  2. Do you have JS enabled in other browsers in which you trying to get this?
  3. Show me list of all js files that loaded on maintenance page.
  4. Do you use any other modules that alter theme registry?

If you can record screen video to show me what exactly happens.

deanflory’s picture

deanflory commented
StatusFileSize
new Maintenance_Countdown_ERROR.php_.html_.zip11.13 KB
  1. It appears to be the Maintenance Countdown template as those are not the fonts I'm using on the rest of the site. I do have the logo turned off presently.
  2. Javascript is on in all browsers tested.
  3. Code of page is attached which should show all .js files as I turned off aggregation.
  4. I have no idea if I use any modules that alter the theme registry, haven't really gotten to that part of development yet, just turned on what I felt I needed. I do have a few modules that deal with theming parts of the interface though I'm fairly sure I haven't implemented any yet other than AdaptiveTheme settings and setting a few HTML5 elements on some content wrappers in panels and such.

Site is ecudchi dot com if you need to see it in action/inaction and it would be helpful to have a second outside opinion.

EllECTRONC’s picture

EllECTRONC commented
Title: Doesn't Work D6 + D7 + JS conflict + HEAD » Doesn't Work (JS conflict)
Status: Postponed (maintainer needs more info) » Closed (fixed)

Yep, I see so many JS conflict, that I decide cut all unneeded JS files at all to prevent js conflict forever and ever.

deanflory’s picture

deanflory commented

My hero! :P
I'll check it out after a slew of module updates.

Thanks for your help. I think this type of functionality should be pulled into core as I feel it is so necessary for a good user experience.