I have recently come back to a previous employer where I implemented Umbraco with uBlogsy. I've come back, and it appears somehow there are two installations of uBlogsy in Umbraco. Both are package 1.32, and umbraco v 4.7.0 (Assembly version: 1.0.4090.21631)From Developer / Packages / Installed packages, hovering over each uBlogsy node uncovers "javascript:openInstalledPackge('6')""javascript:openInstalledPackge('7')" I want to uninstall one, but, when I attempted it in our staging environment, it failed quietly, hung forever, removed the blog node from the content tree, and links to a blank white page on the front end, yet still shows both in the Installed Packages tree.Is there a way to manual remove an installed package from the database and file tree?
apologies, but there may be more to it than that. I removed one of the duplicate xml nodes, and now the tree does not load at all. Is there perhaps an extra step afterwards?
Now there is another error, when we go to save or publish, we get an object not set to instance exception during the savesettings routine of uTagsy. I have perused the forums for similar situations, and I have verified the JSON format of the settings file.
[NullReferenceException: Object reference not set to an instance of an object.]
uTagsy.Web.usercontrols.uTagsy.datatypes.uTagsy.SaveSettings() in D:\_PROJECTS\uBlogsy\Branches\1.32_bugs_search\uBlogsy\uBlogsy\usercontrols\uTagsy\uTagsy.ascx.cs:103
uTagsy.Web.usercontrols.uTagsy.datatypes.uTagsy.OnLoad(EventArgs e) in D:\_PROJECTS\uBlogsy\Branches\1.32_bugs_search\uBlogsy\uBlogsy\usercontrols\uTagsy\uTagsy.ascx.cs:39
System.Web.UI.Control.LoadRecursive() +74
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Control.LoadRecursive() +146
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207
That is normally because either the json file got corrupted and is no longer correct json. Or some other javascript on the page is crashing, which is causing non-correct json to be sent to the server.
// get tags json text for this document type var jsonText = uTagsy.uTagsy_hfAllTags.val().toString().trim(); if (jsonText != '' && jsonText != '""') { uTagsy.document = JSON.parse(jsonText.toString()).document;
The exception says JSON is undefined, and doesn't seem to have a problem with jsonText. I validated the JSON at JSONLint.com, and it is valid. My guess is because the uTagsy.document never gets defined, that's why it's throwing a null exception on the server during subsequent operations.
To clarify, in the code I submitted above, it's the all caps JSON object that is not set, not the actual json being read from the file - that comes through just fine. In the tinymce scripts I see instances of it being declared within a function scope, this particular function expects JSON to be defined at a higher scope and it does not appear to be happening. The settings json is being read just fine, it's the other object that's the offender. In the Javascript, I do not see a declaration for JSON anywhere within the execution scope.
Two unique uBlogsy engines installed somehow?
I have recently come back to a previous employer where I implemented Umbraco with uBlogsy. I've come back, and it appears somehow there are two installations of uBlogsy in Umbraco. Both are package 1.32, and umbraco v 4.7.0 (Assembly version: 1.0.4090.21631)From Developer / Packages / Installed packages, hovering over each uBlogsy node uncovers "javascript:openInstalledPackge('6')""javascript:openInstalledPackge('7')" I want to uninstall one, but, when I attempted it in our staging environment, it failed quietly, hung forever, removed the blog node from the content tree, and links to a blank white page on the front end, yet still shows both in the Installed Packages tree.Is there a way to manual remove an installed package from the database and file tree?
The package probably isnt installed twice.
The umbraco package list is controlled by the \App_Data\packages\installed\installedPackages.config
Just remove the extra xml.
apologies, but there may be more to it than that. I removed one of the duplicate xml nodes, and now the tree does not load at all. Is there perhaps an extra step afterwards?
if you're talking about the developer tree not loading then either you need to restart the app, and/or the xml is now broken.
Figured it out - I think the problem was with Notepad++. Reopened it in a different editor and resolved the issue. Thanks!
Now there is another error, when we go to save or publish, we get an object not set to instance exception during the savesettings routine of uTagsy. I have perused the forums for similar situations, and I have verified the JSON format of the settings file.
That is normally because either the json file got corrupted and is no longer correct json. Or some other javascript on the page is crashing, which is causing non-correct json to be sent to the server.
Check the console for js errors.
You are correct, it crashes here:
// get tags json text for this document type
var jsonText = uTagsy.uTagsy_hfAllTags.val().toString().trim();
if (jsonText != '' && jsonText != '""') {
uTagsy.document = JSON.parse(jsonText.toString()).document;
The exception says JSON is undefined, and doesn't seem to have a problem with jsonText. I validated the JSON at JSONLint.com, and it is valid. My guess is because the uTagsy.document never gets defined, that's why it's throwing a null exception on the server during subsequent operations.
Settings.config
{"documents":[{"documentType":"uBlogsyPost","tags":["a","air conditioning","alternative energy","alternative fuels","another tag","appliance rebate programs","bge","california","cfl","chevy volt","clp","cng vehicles","comed","con ed","connecticut","consumer appliances","consumer electronics","critical care programs","educational","electricity consumption","electricity deregulation","emergency preparedness","energy efficiency","energy efficient light bulbs","energy star","epa","ercot","fuel efficient vehicles","fun stuff","government subsidies","heat wave","helping a hero","home energy audits","hurricanes","hydraulic fracturing","insulation","it needs","led light bulbs","natural gas","natural gas vehicles","new year\u0027s resolutions","nissan leaf","ohio","online energy calculators","outage numbers","peco","ppl","programmable thermostats","pseg","renewable energy","safety tips","saving energy","saving money","slamming","smart grid","smart meters","smart thermostats","solar energy","solar powered car","switching electricity suppliers","tag","technology","ui","water conservation","wind power"]}]}
JS Runtime:
"{\"document\":{\"documentType\":\"uBlogsyPost\",\"tags\":[\"a\",\"air conditioning\",\"alternative energy\",\"alternative fuels\",\"another tag\",\"appliance rebate programs\",\"bge\",\"california\",\"cfl\",\"chevy volt\",\"clp\",\"cng vehicles\",\"comed\",\"con ed\",\"connecticut\",\"consumer appliances\",\"consumer electronics\",\"critical care programs\",\"educational\",\"electricity consumption\",\"electricity deregulation\",\"emergency preparedness\",\"energy efficiency\",\"energy efficient light bulbs\",\"energy star\",\"epa\",\"ercot\",\"fuel efficient vehicles\",\"fun stuff\",\"government subsidies\",\"heat wave\",\"helping a hero\",\"home energy audits\",\"hurricanes\",\"hydraulic fracturing\",\"insulation\",\"it needs\",\"led light bulbs\",\"natural gas\",\"natural gas vehicles\",\"new year\\u0027s resolutions\",\"nissan leaf\",\"ohio\",\"online energy calculators\",\"outage numbers\",\"peco\",\"ppl\",\"programmable thermostats\",\"pseg\",\"renewable energy\",\"safety tips\",\"saving energy\",\"saving money\",\"slamming\",\"smart grid\",\"smart meters\",\"smart thermostats\",\"solar energy\",\"solar powered car\",\"switching electricity suppliers\",\"tag\",\"technology\",\"ui\",\"water conservation\",\"wind power\"]}}"
That's a lot of tags.
Is it possible to just remove them all to see if it still crashes?
Tried that last week with the same result.
{
"documents": [
{
"documentType": "uBlogsyPost",
"tags": []
}
]
}
Same error is yielded.
To clarify, in the code I submitted above, it's the all caps JSON object that is not set, not the actual json being read from the file - that comes through just fine. In the tinymce scripts I see instances of it being declared within a function scope, this particular function expects JSON to be defined at a higher scope and it does not appear to be happening. The settings json is being read just fine, it's the other object that's the offender. In the Javascript, I do not see a declaration for JSON anywhere within the execution scope.
You're not using IE are you? If so, try chrome.
Chrome does not crash like IE does. I had our users install chrome. Is there a way to make it work in IE?
Someone came up with a fix related to IE but I cant remember what it was, and I'm not sure if it's the same problem.
My stance on IE is that it sucks. Chrome all the way!
is working on a reply...