Problem Description: deployed a new gadget xml but gadget does not refresh although parameter nogadgetcache=1 is used.
Steps to Reproduce:
i makes changes to a gadget xml. Deploy using Eclipse, to an appspot site.
2, Deploy through code.google.com's google app console ( i think this is only for changes to manifest, but with or without this step, refresh does not happen ).
Able to see latest changes on the appspot site hosting the gadget xml
logout of gmail, login with : https://gmail.com/?nogadgetcache=1
gmail gadget behaves like the old version.
Even stopped development for more than a week, still not refreshed.
Anyone here can help or encounter similar issues?
Try renaming the gadget spec file so it uses a new URL (then update your manifest to reflect this new URL). This is from Google's documentation.
we have the same problem it take 30mins to get it work..
https://mail.google.com/mail/u/0/?shva=1#inbox?nogadgetcache=1
i found the problem in chrome take's very long.. if you do it in internet explorer prived mode it much quicker..
Related
I'm having the strangest problem with Jira.
We were in the process of setting up links between Jira and Confluence and everything seemed to be working. After a restart of the machine we had some startup issues due to disabled plugs. We resolved this by deleting the rows indicating inactive plugins in the MySql database.
Everything seemed to be working. Could log into Jira. Could log into Confluence. Could connect from each to the other using application linker widget in the upper left corner of the applications.
While trying to embed some Jira into a Confluence page a user got an error and we checked the Application links.
Application link from Jira to Confluence looks good.
Application link from Confluence to Jira looks like this.
If I log onto the host machine and try to log into Jira as http://localhost:8080 i get this very strange behavior:
http://localhost:8080 brings up my Jira log on page.
If I try to log on as userX I get a try again screen.
If I try to log on as userY I get a try again screen WITH A CAPCHA.
BOTH logons DO WORK if I try to logon from https://jira.myorg.com!!!
Really confused why I can access the application but authentication fails. Any help would be greatly appreciated.
I'm still seeing this strange behavior but I've solved the problem by changing the application url to the outward facing one (https://jira.myorg.com). At one point this didn't work (that's why we used http://localhost:8080 in the first place, jira and confluence are on the same server). It seems to not need this at this point.
We did delete and recreate the links from scratch also. This is mention as a suggestion in the documentation if you are having problems with the links.
For development, I'm using the integrated weblogic feature in JDeveloper. So far, this has worked fine. I was recently put onto a different project, however, and when I try to deploy it, I'm having trouble. Here are the steps I take:
Run->Debug Server Instance (IntegratedWeblogicServer)
In the Projects, I right-click on Web Content->index.html and select Debug.
According to the log, the applicatoin deploys successfully with the target URL of http://localhost:7101/Myapp-Myapp-context-root/index.html and it then attempts to open the page.
However, this gets me a "This page can't be displayed" in Internet Explorer. No error messages in JDeveloper's log or IE's console. I realize this doesn't give a lot of information to work with, but it's all I've got right now.
One other thing, and I don't know how relevant this is, but if I attempt to refresh the page or enter it into a different browser, it redirects to https://localhost:7102/Myapp-Myapp-context-root/index.html
I figured it out. It switching to a secure port was related, as the finalized product is supposed to do that. Development requires the security-constraint fields in the web.xml to be commented out.
We are in the process of implementing Success Factors LMS, and trying to play and view SCORM compatible files exported from Adobe Captivate 8 and 9 in Success Factors LMS.
I get the message - 'ERROR – unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support’
I have tried SCORM versions 1.2 v3 and 2004 V2 and V4. We can view the content, however it does not track, show as complete etc.
We are also producing Scorm compliant files using Skillcast and Articulate, but we still hit the same issue, we can view the content after closing the API error window, but still does not track.
Anyone experienced this problem before? Or know of a fix?
Many thanks
Normally this issue comes up when the course is unable to get the SCORM API from the LMS...I have seen a ton of SCORM content running in Success Factors before, so I wonder if the issue is in the setup. Are you seeing any "Access Denied" type errors in the browser element inspector/developer tools? I wonder if the course just can not find/have access to the player window. If the course is launching in a new window, you may want to try launching it in the frameset. I have seen folks get around this issue by making sure the player and sco are in the same window...
If you wanted to rule out the content being the issue, you can always test your content in the SCORM Cloud's free sandbox (https://cloud.scorm.com) to make sure the course is properly asking for the API...
If you have any other questions, we would be happy to help...you can just shoot us an email at support#scorm.com.
Thank you!
Joe
The error occurs because the content is not speaking to the Learning Management System (LMS). The code that runs to initialize the session doesn't happen. There is no return "ping" from the LMS.
You will get this error when you publish in SCORM and run from your desktop, or from a web server that isn't connected to an LMS. If it occurs when you are launching from an LMS it can either mean that the SCORM API isn't configured correctly, or your content server is on a different domain (cross-domain) than your application servers.
To test, you should try launching your content in different browsers. Our system was configured in such a way that Firefox and Chrome read our content to be cross-domain issue, and threw the SCORM API error, but Internet Explorer worked just fine.
In the end, it was determined that our server configuration in tandem with our firewall and security settings read the Content server as cross-domain and we had to redeploy our content servers within the firewall.
I am trying to deploy a node app on heroku via the web GUI for dropbox, and I get the error:
Item could not be modified:
"Content-Type" request header must be set to "application/json".
Any clues as to what that might mean?
Disclaimer: I was not the one who wrote the app, just made two mods for heroku.
In case you haven't found an answer... I have the same problem.
You probably need to update your runtime stack.
Here's Heroku's message on their website:
"The legacy Cedar-10 stack has been deprecated and reached its end-of-life on November 4, 2015. Applications may continue running, however you will not be able to push to your application without upgrading to Cedar-14 first."
How to update informations are available here:
https://devcenter.heroku.com/articles/cedar-14-migration#upgrading-the-production-app-to-cedar-14
I have the same problem. I raised a ticket at Heroku. They replied,
"Are you using Firefox? We seen this recently with Firefox and we are currently working on a fix. In the meantime, you can use another browser like Google Chrome for deploying your app."
And using Google Chrome fixes the problem.
I want to start developing a contextual gadget for GMail apps and have been following the guide.
In the part about Installing and Testing the Gadget, it tells me to go https://code.google.com/googleapps/console/a/{Domainname} and upload the manifest file there. I have done this, the manifest file was accepted and I used the Deploy button.
I get to the page where it asks for the data permissions, click yes, and then get a Server Error. I have re-uploaded the manifest and triple-checked that the <Url> leads to a valid gadget xml. I get zero feedback about what the error could be, only that it's a Server Error and it happens every time I try. If the gadget XML is somehow invalid, I would not be able to check, as Google gives me no way to check such files for correct content.
Can anyone help, perhaps?