No countdown

Hmm that’s strange, the countdown should be showing up. Do you or your host have a form of caching turned on? What’s your website?

Bob

Hi, I′m just testing on my local machine at the moment. A Windows machine with a WebMatrix setup, using a child theme. I have emptied the cache and cleared all fields I′m not using. The only thing printed in the debug log is “[21-Mar-2015 15:59:53 UTC] easy-pie-coming-soon:displaying coming soon page”. Any plugins that are known to cause issues with your plugin? I′m guessing the javascript for the countdown is not loading.

I haven’t heard of issues before with the countdown but yeah it does sound like a javascript issue. If you go into Chrome or Firefox, load up the page and hit Ctrl-Shift-J (or equivalent on mac) the console may indicate error’s that the page is experiencing..If it something looks odd could you paste in a reply – thanks

Hi, what I get is this:

[ Moderator note: Code fixed, please wrap code in backticks or use the code button. ]

"autoptimize_7a830094d1eef4f5bf55e6e57f6d5869.js:14 Uncaught SyntaxError: Unexpected end of input", and the code:

[ Moderator note: excessive code redacted, please use pastebin.com instead. ]

Oh, sorry :-|. That was quite a pile of code…

I can see now that the problem derives from the AutOptimize plugin, which is set to optimize javascript to increase site performance. Not a big deal, since I can temporarily disable that setting when I need to use the countdown. But maybe it could be interesting for you to look into if others use the AutOptimize plugin?

Did you give any thought to the suggestions I made in my first comment?

Sorry again for posting that pile of code. Maybe you could just delete that from the comment?

All the best, and thanks for responding so quickly!

I hadn’t thought about adding the time before. I can see that would be helpful when used as a maintenance mode plugin since that’s usually the reason the site is down for shorter timer periods.

I have the roles idea on the todo list for my pro (Coming Soon Page Elite – easypiewp.com) plugin although I’m not sure in what order I’ll add the feature.

Thanks for both suggestions and also for bringing to my attention the conflict with AutOptimize. Good luck and if you have any other questions/issues feel free to ping me.

Bob

Thanks Bob! ??

Hi guys;
I’m Autoptimize’s developer. You can easily configure AO to exclude either inline or external JS from being optimized, which should allow you to fix the issue with “coming soon page”. There’s more info on this topic (and many others) in the FAQ.

Have a nice weekend,
frank

Very cool. Thanks for chiming in Frank.

Great! Thanks Frank! ??

Frank, now that you did chime in, I remembered that I never could get that working. How exactly should I reference the path to scripts to exclude?

I have read tha FAQ:s and readme files but it doesn′t seem to work. In this case, if I add the path “plugins/easy-pie-coming-soon/mini-themes/base-responsive/js/” as the path to exclude, I get the following errors instead: “jquery.countdown.min.js:26 Uncaught ReferenceError: jQuery is not defined” and “custom.js:3 Uncaught ReferenceError: $ is not defined”. Shouldn′t these files instead be ignored by AO, and the scripts load?

Hi Gorillo;
the error indicates you also have to exclude jquery from being optimized (or you could alternatively “force JS in head” in stead).

Hope this helps,
frank

Hi Frank, thanks for answering. I′m afraid I don′t quite understand what also excluding jquery actually means here? And if I were to force JS in head, wouldn′t that mean that all js used in the site would be forced into the head? In that case it seems I could just as well temporarily disable AO while the countdown plugin is in use.

And by the way – otherwise I think AO works great. It really helps, allthough it breaks css in my case if I use that feature on this site.
??

well, easy-pie-coming-soon/mini-themes/base-responsive/js/jquery.countdown.min.js relies on jquery being loaded. if you exclude countdown and you don’t exclude jquery as well (which means adding jquery.js or jquery.min.js to the comma-seperated “exclude from optimization”-list) countdown will stumble giving the error you copy/pasted earlier.

force all in head indeed means the autoptimized js-file is in the HTML head instead of being deferred at the end. this is still way better then not having your JS optimized, as it is still aggregated in 1 file.

regarding CSS-breakeage; what happens; blank page, completely unstyled page or some of the style missing?

frank