Has anybody found that the Obout Calendar control has stopped working in the latest Google Chrome update (17.0.963.56 m)?
We have an active licence with Obout, but following two emails and two telephone calls we have yet to receive a response or even an acknowledgement that an issue exists. Anyone using the latest version of Chrome can replicate the issue on the published examples:
http://www.obout.com/calendar/calendar_live_styles.aspx?style=default
Try paging through the months a few times and you should eventually see the following error:
Uncaught TypeError: this is not a Date object.
If anybody has a workaround or can shed light on the matter I would love to hear from you. At the moment it has crippled our live site and we are frantically looking for a solution.
The new version of the Obout Calendar has been released today:
http://www.obout.com/calendar/changelog.aspx
It contains the fix for the latest Google Chrome.
I have seen the problem and am also waiting to hear back from Obout. Have sent 3 emails and as yet nothing. I have only just bought the suite this week! and am hoping that this difficulty in getting a response is just my lack of using the correct channels.
OK Problem Solved!...Obout have just emailed me a revised DLL. Happy to forward this if anybody requires.
Related
I've been a passive StackOverflow user for more than a decade now. I don't really think this is the place to ask this but Google Developers Help page referred me here.
Adwords has been updating to a beta version and I'm a heavy user of its Scripts console, but recently, when I want to ad a new script with the big red button, it starts loading and then this message displays: "There was a problem loading the script. Please try again later"
I've already tried with Chrome and Safari, a cookieless browser and with a different account and nothings seems to work. I also Google the error and there is nothing. I don't think I'm the only person experiencing this, do you have any solution?
I couldn't reproduce your problem and was able to create scripts—however, I've noticed quite a lot of bugs in the new web interface (to be fair, they say it's still in beta).
But as a workaround, just use the Return to previous AdWords link in the three dot option menu, which will take you back to the old interface. I could well imagine that you'll be able to add a new script there.
My chrome extension has been rejected twice and the reason from the email is
it currently does not work or provide any functionality upon
installation.
However, I have tested it on multiple computers with different accounts and it works fine. I sent an email back asking for clarification and they sent me the same email, but with the above quote highlighted in bold.
I emailed them again asking for further clarification but I don't think I'll be receiving it any time soon.
I believe the issue may be that I am defining the key in the manifest file, I read that you aren't supposed to do this (from a post from 2014). However, I'm using the key from the developer dashboard after uploading my extension.
Removing the key isn't mentioned in the publishing guide so I want to make sure before resubmitting (repeatedly resubmitted results in an account suspension).
Thank you for your time, any help would be greatly appreciated.
Chrome Version: Version 54.0.2840.99 m (64-bit)
OS: Windows 10
Extensions: None enabled
I want to upload an extension to the web store developer dashboard. Since it will be my first one I have to pay 5 dollars as an entry fee. When I tried the first time I was able to see a button to press that loaded the form in which I put my CC info.
But I had trouble with my cc and I had to try it again later. But now the button is missing from the page and there is nothing I can do to bring it back.
This is a picture that shows a screen shot with the button enabled and what I'm seeing right now.
Link here.
Does anyone here had a similar problem and knows how to deal with it?
It is known bug and being tracked at crbug.com/652178
I doubt whether Google Webstore team have fixed it yet, but as a workaround you can try updating your payment details at https://wallet.google.com , then retry. I got it solved earlier in same steps.
Hope it helps!
I'm getting tones of these very generic errors in my solution while accessing the Google Drive service via the SDK.
Can anyone provide pointers as to why these errors are happening? For the most part the solution works but then randomly these exceptions will just pop up!
Maybe if I can email support directly that would be great :)
Also, over the last hour I've received in excess of 600 occurrences of this exception and really need to resolve it!
In the newly published version of my app that is using Google Maps Android API V2, I've implemented all the things suggested by the developer guides to ensure the user has GooglePlayServices installed, and it has been working well on all the devices I own and the several hundred people that have updated to the new version of the app so far.
Today I received a bug report via acra with a strange error. This is happening on the following line of code, after setupMapIfNeeded() has completed:
mMap.setMyLocationEnabled(true);
Logcat reports:
W/GooglePlayServicesUtil(10401): Google Play Store is missing.
Shouldn't the call to GooglePlayServicesUtil.isGooglePlayServicesAvailable() also ensure that the Play Store is installed? That seems like a huge oversight on Google's part if it doesn't.
Any help is appreciated.
In case someone came here by accident or was just wondering why it was not working...
This could happen when user had old Android Market installed, which was replaced by Google Play Store.
Here is relevant issue: http://code.google.com/p/gmaps-api-issues/issues/detail?id=4862 (fixed in february update).