We integrated the Google Classroom Share button per these docs - https://developers.google.com/classroom/guides/sharebutton - back in Apr. Today we noticed it was not working, and saw these errors in the JavaScript console. Googling for "homeroom_share_widget" turns up very little, though there is a page with a copy of another StackOverflow post where someone reported this on Aug 4th 2020 and it "resolved itself."
www.gstatic.com/classroom/sharewidget/widget_stable.html?usegapi=...com&pfname=&rpctoken=71244563:1
Refused to apply style from
https://www.gstatic.com/_/hr/_/ss/k=homeroom.homeroom_share_widget.-6njcba4tmj9p.L.X.O/d=1/ct=zgms/rs=AK3ymSVKf9-q6qT49CxfhvwE4dkes0zTHw/m=share_widget
because its MIME type ('text/html') is not a supported
stylesheet MIME type, and strict MIME checking is enabled.
Google identified the problem on their side and fixed it. See https://issuetracker.google.com/u/1/issues/162785095 for details.
Related
I'm trying to add a netconf-connector into my Open Daylight Nitrogen controller and keep coming up against this error:
">Error parsing input: Could not find module for namespace urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"
I'm posting to rest via the postman application using the below URL and Schema used in the guide below:
"http://192.168.0.1:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules"
Has anyone had the same issue, this is the guide I'm following..
http://docs.opendaylight.org/en/stable-nitrogen/user-guide/netconf-user-guide.html
I found the same issue reported on the old Open Daylight forum but it went un-answered..
https://ask.opendaylight.org/question/28561/error-adding-node-to-odl-via-restconf/
Thanks,
Simon
Judging from the error message, you tried to use the controller-config loopback mechanism. This mechanism was deprecated and I believe was completely removed in Nitrogen (unfortunately the documentation wasn't updated to indicate this). Either way, you should use the mechanism outlined in the "Netconf-connector configuration with MD-SAL" section.
In dynamics CRM 2016 I have a custom button that opens up a HTML WebResource and runs some JavaScript.
It works perfectly in our development environment.
However, in our pre-production it gives the message:
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
F12 Debugging only provides the same message, and i cannot access the specific resources (the code) because it is a managed solution in preproduction.
Google only return very general "500 error fixes", or similar questions that have not been answered, that are very old.
Any suggestions how to go about this?
(And yes I have checked that it is actually pointing at the correct files).
It turns out that in the RibbonWorkbench in the Url command the path called, begins with /Udv/WebResources/myPage.htm, which is a hardcoded part of the development path.
The answer was to change the parameter to $webresource:myPage.htm
I have searched the answers to similar questions asked about this SagePay error, and checked that the fixes don't appear to apply to my problem.
Specifically:
I am using a correct 2-letter country code for BillingCountry and DeliveryCountry.
I am POSTing VPSProtocol, TxType and Vendor as well as the Crypt value.
I have re-checked that I am using the correct encryption key from the MySagePay test portal.
Now I was using http://localhost:8084/app/success and http://localhost:8084/app/failure for my success and failure URLs, since I thought that although these are (obviously) not visible externally, it shouldn't matter since SagePay is re-directing at the end of its part of the transaction. (Is this assumption correct, or do these URLs need to be externally accessible?) Some of the answers have thrown doubt on this, so I changed them to an external website I own, and I still get the same error.
Another line of thought is that the client I am developing for has already gone live, and there seem to be hints that once you have gone live, you no longer have access to the test server (Is this true?)
Is there anything else I should be checking? (Additional info: I'm using the SagePay api (sagepay-api-1.2.2.0.jar and related libraries) to validate the form contents and encrypt them.
I used the integration from https://github.com/tolzhabayev/sagepayForm-php
I had this error (5080) and spoke to SagePay support and they guided me to the MySagePay portal where you can view Invalid transactions to be able to troubleshoot this error easily!
Hope this helps someone.
Chris Rickards
I had exact same problem and I tried everything that you described as well, one day after I found that the problem was in "VendorEMail" field, it had 2 email addresses separated by ;, once I removed second and left only one email everything worked.
As of 2013-04-16 WEST, the official getting started example of the YouTube iframe API results in error messages when run in Chrome 25 on WinXP/SP3:
I am accessing the example hosted on a web server, i.e. not via the local file system.
Am I doing something wrong? Is the example / the API broken? Can you reproduce the issue?
This error message has been around for quite a while -- as this Google Group post explains, it's due to an unresolved (4-year unresolved!) bug in WebKit:
https://groups.google.com/forum/?fromgroups=#!topic/youtube-api-gdata/VKGl4ahBGyk
It shouldn't affect anything -- it certainly hasn't for our projects, and in visiting the demo URL you posted, it looks like it isn't affecting the API functionality there (i.e. in that demo, the video still stops after 6 seconds per what the code states). There was an SO question a while back that thought it might be affecting analytics:
youtube "Unable to post message to..." causing video analytics to not be tracked
But it was never confirmed as being relevant.
It will be interesting to see if Chrome's move to the new Blink fork of WebKit leads to the bug itself being resolved.
I've created a content security policy for our sites, but i'd like to trial it first to see if it will cause any problems so I've used the report only header and added a report-uri directive.
The header name X-WebKit-CSP-Report-Only works correctly in Webkit based browsers, but neither X-Content-Security-Policy-Report-Only or Content-Security-Policy-Report-Only work in Firefox (version 15). X-Content-Security-Policy works, sending violation reports to the URL specified in my report-uri directive. However, this also implements the policy which I don't want to do yet. Has anyone else come across this?