After installation of the Starter kit for a personal site on a local environment I have created a revisions of this installation. After transfer and installation of the revision to an development environment I get an error:
An error occurred during a call to extension
function 'GetCommentsForPost'. See InnerException for a complete
description of the error.....Invalid object name 'comment'.
Its really not a bug, more of a limitation to courier. It cannot in anyway detect your site needs the comment database table, so it doesn't transfer it.
Initially we thought of having a sql table transfer provider, but it basicly gives you too many problems, how do you merge data? how do you handle different dbs / schemas, etc etc, its a can of worms.
So things like that, will most likely never be supported, as it is not something you would need to sync daily anyway
But yes, I agreee, seeing this error after a transfer, does make it seem like a error
Table Comment missing in revision
After installation of the Starter kit for a personal site on a local environment I have created a revisions of this installation. After transfer and installation of the revision to an development environment I get an error:
An error occurred during a call to extension function 'GetCommentsForPost'. See InnerException for a complete description of the error.....Invalid object name 'comment'.
After some research I have found the sollution with some help in this topic: http://our.umbraco.org/forum/developers/xslt/13735-Cannot-find-a-script-or-an-extension-object-associated-with-namespace-
It seems like the revision doesn't create the required table Comment. Looks like a bug to me. Are there more people who have had the same problem?
Hey Tim
Its really not a bug, more of a limitation to courier. It cannot in anyway detect your site needs the comment database table, so it doesn't transfer it.
Initially we thought of having a sql table transfer provider, but it basicly gives you too many problems, how do you merge data? how do you handle different dbs / schemas, etc etc, its a can of worms.
So things like that, will most likely never be supported, as it is not something you would need to sync daily anyway
But yes, I agreee, seeing this error after a transfer, does make it seem like a error
/per
is working on a reply...