Did Google stopped their Spell Service? It seems that my TinyMCE's spellchecker stopped working using GoogleSpell as the engine. It was working previously and just this week it stopped, when I changed the engine to PSpellShell its working.
The TinyMCE editor is in a SugarCRM installation.
Actually, the service is down (https://www.google.com/tbproxy/spell).
But this has occured several times in the past already.
I'd just wait a bit and see if it gets back online.
Related
I have been searching so long for this, and couldn't find a solution.
So, I have developed a pretty basic dialog flow project and deployed it onto firebase using inline editor.
Now the 1st deployment works perfectly fine with the simulator.
However, I changed some content to include suggestion chips and modify the responses as well; this gets reflected fine in dialog flow. And I can see the changes I have made.
But when I update the Draft and try to test it again in simulator/google assistant device, it doesn't load the newer changes. I am not sure if what I am doing is correct or not.
Please help :(
Just now found this - https://discuss.api.ai/t/actions-on-google-integration-agent-updates-do-not-always-publish-correctly/7483
It seems many users are facing this issue.. :/
Dialogflow had a bug causing this issue which should now be fixed.
I've been experiencing an issue with stepping through my code in Visual Studio 2013.
These seems like a fairly serious issue so I'd be surprised if no one has noticed anything like this. As you can see in the screenshot below I, while paused in the debugger both Step Into and Step Over are disabled. However this issue also seems to be temporal as they do come back after about 10 or 20 seconds. It's probably also worth mentioning sometimes it's just Step Over, sometimes just Step Into and sometimes both.
I have a feeling this might be due to a plugin. The main plugins I have installed at the moment are ReSharper 8.1, Reflector and Web Essentials.
I've tried searching around but can't seem to find anything. Is this a know issue anywhere?
The cause of the issue was the Reflector Pro 8.3.2.99 plugin as #faceman suggested. Disabling the plugin corrects the issue.
It looks like there may be a fix:
http://forums.reflector.net/questions/4748/reflector-extensions-breaks-f10-functionality.html
Please can someone help?
I've had facebook integration scripts running on my website for many years already with no problem. However, I am now being flooded with complaints from customers who use INTERNET EXPLORER saying that since an update to IE a week or so ago they are constantly getting the long-running script errors...
"Stop Running This Script.
A script on this page is causing Internet Explorer to run slowly.
If it continues to run, your computer might become unresponsive."
I've worked it out (by disabling scripts) that the problem is with the Facebook scripts.
Nothing has been changed in months on the website so it's not something I can figure out how to fix.
Scripts: Invite your friends, Like, Share page, etc
Please, please help
Thanks
Matt
I've ran into the same issue. I can reproduce the issue not just on my site, but on others as well when using IE 9 or IE 10 (have not tested with older IE versions). The issue seems to be a result of IE's compatibility view feature. If that is enabled for a website, which also has the facebook like button on the page of the site you're trying to load, a long running script error is produced (error from a function called _t). When I disable compatibility view for that website, the error goes away. I'm not sure if the issue is with the IE feature, or with facebook's button...I'm not getting same error from other scripts, nor other social buttons like google+, which makes me think the issue is on Facebook's end. I've been trying different IE setting configs for days now...so far, the only fix I can come up with is turn compatibility view off. And of course resolve issues so that compatibility view are not needed. Though telling your users they have to turn off compatibility view doesn't seem like an appropriate response...so I hope a better fix is found.
I've tried posting this on the Umbraco forums to no avail. Hoping to find some help here.
I thought I upgraded successfully from 4.0.4.2 to 4.5.2 (on my way to 4.8...) as I received no errors and everything seemed to go smoothly. However, in the backoffice, when I click on any section other than Content, I get redirected back to Content. I can manually reach each section by typing in the name of it after the # sign like: #media, but as soon as I click on a tree item, it redirects me back to Content. Any ideas would be appreciated.
2 thoughts:
You're cacheing some of the old javascript in your browser. Try clearing your cache. IE can be stubborn in this regard; preferably try in Chrome.
Personally, if your site is working under 4.5.2, I wouldn't sweat the back office issue and just continue with the upgrade to 4.8.1. There will likely be new problems to solve there anyway :) and the backoffice issue may go away.
Updating the icons via the following script fixed this problem. Links must run off the appIcon field. Not sure why this is not executed when the database is updated via the 4.5.2 upgrade.
update umbracoApp
set appIcon = '.tray' + appAlias
where appAlias IN ('content','media','users','settings','developer','member')
I have deployed and then redeployed a .wsp on a Sharepoint 2010 server (the solution was developed on another 2010 server). The solution contains 2 web parts.
After retracting and removing the old solution, I added and deployed the same solution again, with no errors.
Afterwards, I deactivated and reactivated the feature installed through my .wsp file.
The problem is that whenever I try to add one of those 2 web parts to a page, I get an error saying "The operation could not be completed because the item was removed from the gallery".
Do you have any ideea what's happening? Anu help is greatly appreciated!
Usually this happens if the web part gets orphaned in the web part gallery. Try Deactivating your solution and Retract and Uninstall your wsp. Then check the Web Part Gallery for the site collection. If you still see your web parts there then manually delete them.
Then you can Add and Deploy your wsp and activate your solution. The web parts should then be available in the web part gallery and be able to be added to your pages.
I came across a more simple solution which worked well for me.
Go to the webparts gallery at Site Settings/Galleries/Web parts and delete problematic webpart entry. Then deactivate and reactivate the wsp which contains that webpart and everything should work fine. No need for redeployment or uninstalling.
Source
I have the same issue, but in my case after a thorough search in web part gallery found out that some web parts having the same name, but without assembly's prefix have created.
The solution is just to sort the web parts with the date and you'll get the new web parts.
Some times it happens that every thing is same as before, but SharePoint forgets the settings which are placed in webpart.xml file