Gorillo

I′m happy to say that this issue finally seems to be resolved now. A dev version with a bug fix provided by Valentin solved the problem for me.

Hi,

I also had this problem and found that this occur if you have the “Checkout Core Fields” module enabled. Downgrading Booster to version 2.3.7 solved the problem.

Thanks for the fix, mgusmao! works fine. One wonders if development stopped for this plugin though, and whether it could start causing other problems later on since it′s not updated. A pity. Really nice little plugin this, and also quite unique in it′s limited but very useful functionality.

??

Hi,

Thanks for your response.
Well, on the admin settings page under settings > page for handling cancelled subscriptions, I have multiple links to the handle subscriptions page. This is what it looks like next to the dropdown where you choose the handling page:
(“F?rhandsgranskning” = Preview, “Redigera” = Edit)
F?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | RedigeraF?rhandsgranskning | Redigera

Hi Stefano,

Thanks for your response. My point was just consistency. It would be better to be able to translate every single bit of the plugin into the language you want to use. Any particular reason you are not using po/mo files for translation?

Hi,

I have been struggling with this too. This seems to be the only thing that cannot be translated via the plugin translation functions, so why use HTML5 validation as an excuse not to make it translatable?

There are many people (myself for one) that chooses to use browsers with a different language than their spoken language, but still wants websites that uses their spoken language translated all the way. It just doesn′t look goood that that single sentence is the only thing that is not translated.

Thanks

ThankYOU. Keep up the good work! I will write a review for you! ??

Hi, thanks for your reply.

Product id works, thanks. In my case there is just on product, so this works fine. However, if you have hundreds of products in your shop it would take hours to fill in all the id:s in the box. I think you should consider putting the “Disable on yhis page” dialog on woocommerce products/pages anyway. And I also think it would make the plugin more user friendly to have settings for icon sizes, placement etc. in the configuration settings. Just a friendly advice. I will go on with a little bit of css tweaking now. ??

Hi,

I noticed the same thing. Had to disable the popup until this is fixed. An update to fix this would be appreciated.

Thanks!

Hi,
Thanks for answering. I′m well aware that there are different language files for admin and frontend.

In my woocommerce-sv-SE .po file, the string “"%s" was successfully added to your cart.” is translated to “"%s" placerades i din varukorg.”, but that string does not get translated (same thing with “Customer details on the thankyou page).

I am aware of the case sensitivity, so that′s not the problem. As I said, my language files worked fine until you started splitting up certain files. After that, some of them are not translated anymore. Since there is an option to override the default language files by putting them in wp-content/languages/woocommerce, it should just work.

Hi,

Thanks for your answer. It turned out to be a combination of an error at the web hosting company and another error in PayEx admin.

That′s just great! Thanks Bob! What I forgot to mention in my feature request was that it would also be nice to have an option where the plugin sets itself to “Off” when countdown is complete. That way, you would not need to monitor if you′re shure you want your site to go live again at a certain date/time.

Cheers! ??

OK, I understand. But since the countdown plugin is only used while the site is in maintenance mode, I could just as well disable AO for a short period of time.

Regarding the css, I guess there is some custom styling in my child theme that conflicts with styling in the main theme. Some of the styling is broken and I didn′t have time to pinpoint exactly where it breaks. So I settled for just optimizing js for the time being.

Thanks for your answers, I′ll get back to you if I still have problems when I do find the time to dig into it.

??

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.
??