19 Jun 09 Umbraco : No node exists with id ‘1040′

When Umbraco 4 was first released I had issues with 2 of the upgrades from v3 in that the templates disappeared from the UI and clicking on any of the DocumentTypes resulted in an exception taking the form of “No node exists with id ‘1040′”. Today I was working on the site again and it was bugging me so I checked the forums and found this post however it wasn’t resolved as far as I could tell.

I did a little digging around in the database and found some references in the cmsTemplate table to template master documents with the id 1040…bingo! I changed all references to a suitable master template that did exist and all of the above issues magically went away.

I thought it was too much of a coincidence for the node id in the exception to be the same for others as it was for me so I looked for a pattern in where this reference existed and they all seemed to be templates for what I think was the original Creative Website Starter (CWS) package. Would be interested in comments from others that might be able to confirm this.

31 Mar 09 Umbraco : Locate nearest node with specific property

In an ongoing project I am working on I needed to adapt a custom user control that was being used as a DataType in Umbraco. I needed to locate the nearest node that had a specific property set and default the selected value of my control to the value of the property in the parent document.

Here is the final piece of code:

//- Get the current document as our starting point
Document currentDoc = new Document(Convert.ToInt32(Request.QueryString["id"]));

//- Climb the tree looking for a parent node with the property set
while (currentDoc.getProperty("myProperty") == null)
{
currentDoc = new Document(currentDoc.Parent.Id);
}
//- Set the value in the list if it exists
if (this.myDropDownList.Items.FindByValue(currentDoc.getProperty("myProperty").Value.ToString()) != null)
{
this.myDropDownList.Items.FindByValue(currentDoc.getProperty("myProperty").Value.ToString()).Selected = true;
this.myDropDownList.Enabled = false; //-Disable the control so the branch can't be changed
}

Thanks again to Tim Geyssens for the tip that led me to my final solution.

15 Feb 09 Invalid object name ‘umbracoUser’

Yet another problem on an Umbraco v4.0 site I am working on currently. The site will be hosted on a VPS with Plesk as mentioned in an earlier post, I needed to restore a backup of the remote database locally but after restoring it my local development copy throws the exception “Invalid object name ‘umbracoUser”. After an hour or so of frustration and searching for a solution I realised that the table owner and schema belong to a user on the remote data source which didn’t exist locally.

The Solution:

Run the following SQL statement and output to text and it will generate all of the ALTER statements need to change ownership of the object to DBO(Database Owner):

SELECT 'ALTER SCHEMA dbo TRANSFER ' + s.Name + '.' + p.Name
FROM sys.tables p INNER JOIN
sys.Schemas s on p.schema_id = s.schema_id
WHERE s.Name = 'EXISTING_OWNER_USERNAME'

What you should find is that you are presented with a list of alter statements similar to those below which if you execute will change owner of all tables owned by the owner you specified in the first step and assign ownership to DBO:

ALTER SCHEMA dbo TRANSFER oldowner.cmsContent
ALTER SCHEMA dbo TRANSFER oldowner.cmsContentType
ALTER SCHEMA dbo TRANSFER oldowner.cmsContentTypeAllowedContentType
ALTER SCHEMA dbo TRANSFER oldowner.cmsContentVersion
ALTER SCHEMA dbo TRANSFER oldowner.cmsContentXml
ALTER SCHEMA dbo TRANSFER oldowner.cmsDataType
ALTER SCHEMA dbo TRANSFER oldowner.cmsDataTypePreValues
ALTER SCHEMA dbo TRANSFER oldowner.cmsDictionary
ALTER SCHEMA dbo TRANSFER oldowner.cmsDocument
ALTER SCHEMA dbo TRANSFER oldowner.cmsDocumentType
ALTER SCHEMA dbo TRANSFER oldowner.cmsLanguageText
ALTER SCHEMA dbo TRANSFER oldowner.cmsMacro
ALTER SCHEMA dbo TRANSFER oldowner.cmsMacroProperty
ALTER SCHEMA dbo TRANSFER oldowner.cmsMacroPropertyType
ALTER SCHEMA dbo TRANSFER oldowner.cmsMember
ALTER SCHEMA dbo TRANSFER oldowner.cmsMember2MemberGroup
ALTER SCHEMA dbo TRANSFER oldowner.cmsMemberType
ALTER SCHEMA dbo TRANSFER oldowner.cmsPropertyData
ALTER SCHEMA dbo TRANSFER oldowner.cmsPropertyType
ALTER SCHEMA dbo TRANSFER oldowner.cmsStylesheet
ALTER SCHEMA dbo TRANSFER oldowner.cmsStylesheetProperty
ALTER SCHEMA dbo TRANSFER oldowner.cmsTab
ALTER SCHEMA dbo TRANSFER oldowner.cmsTagRelationship
ALTER SCHEMA dbo TRANSFER oldowner.cmsTags
ALTER SCHEMA dbo TRANSFER oldowner.cmsTemplate
ALTER SCHEMA dbo TRANSFER oldowner.umbracoApp
ALTER SCHEMA dbo TRANSFER oldowner.umbracoAppTree
ALTER SCHEMA dbo TRANSFER oldowner.umbracoDomains
ALTER SCHEMA dbo TRANSFER oldowner.umbracoLanguage
ALTER SCHEMA dbo TRANSFER oldowner.umbracoLog
ALTER SCHEMA dbo TRANSFER oldowner.umbracoNode
ALTER SCHEMA dbo TRANSFER oldowner.umbracoRelation
ALTER SCHEMA dbo TRANSFER oldowner.umbracoRelationType
ALTER SCHEMA dbo TRANSFER oldowner.umbracoStatEntry
ALTER SCHEMA dbo TRANSFER oldowner.umbracoStatSession
ALTER SCHEMA dbo TRANSFER oldowner.umbracoStylesheet
ALTER SCHEMA dbo TRANSFER oldowner.umbracoStylesheetProperty
ALTER SCHEMA dbo TRANSFER oldowner.umbracoUser
ALTER SCHEMA dbo TRANSFER oldowner.umbracoUser2app
ALTER SCHEMA dbo TRANSFER oldowner.umbracoUser2NodeNotify
ALTER SCHEMA dbo TRANSFER oldowner.umbracoUser2NodePermission
ALTER SCHEMA dbo TRANSFER oldowner.umbracoUser2userGroup
ALTER SCHEMA dbo TRANSFER oldowner.umbracoUserGroup
ALTER SCHEMA dbo TRANSFER oldowner.umbracoUserLogins
ALTER SCHEMA dbo TRANSFER oldowner.umbracoUserType
ALTER SCHEMA dbo TRANSFER oldowner.cmsContentTypes
ALTER SCHEMA dbo TRANSFER oldowner.umbracoContent
ALTER SCHEMA dbo TRANSFER oldowner.umbracoContentAll

After executing the above everything started working again as expected.

Thanks to a blog post by Steve Schofield that led me to the solution.

09 Feb 09 Umbraco v4 Upgrade Problem with Plesk Hosting

A project I am working on currently is hosted on a VPS with a Plesk control panel. When attempting to upgrade from RC3 to the final release the process kept getting stuck on the database check stage as it was trying to write to the web.config but it appears it needs to write a temporary file to the root of the hosting environment. At this point an exception was being thrown because within a Plesk hosted environment you can’t set write permissions on the root only on files and folders within it.

The following post led me to a solution that gets you past the step in the upgrade process that requires you to manually update the web.config, no hardship but just a bit of a PITA and will hopefully be addressed in future upgrades.