I just added the new macro container to one of my documenttypes. When I choose a macro and try to save and publish the page, I get the following error. What could be wrong?
Server Error in '/' Application.
Conversion failed when converting the nvarchar value '<?UMBRACO_MACRO macroalias="ucOlav" />' to data type int.
Description: An unhandled exception occurred during
the execution of the current web request. Please review the stack trace
for more information about the error and where it originated in the
code.
Exception Details: System.Data.SqlClient.SqlException:
Conversion failed when converting the nvarchar value
'<?UMBRACO_MACRO macroalias="ucOlav" />' to data type int.
Source Error:
An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.
I endend up re-installing the entire solution. That fixed the problem. Looks like there were something messed up in the old document types I imported from 4.0.2.1.
Macro container issue
Hi!
Version 4.5.1
I just added the new macro container to one of my documenttypes. When I choose a macro and try to save and publish the page, I get the following error. What could be wrong?
Server Error in '/' Application.
Conversion failed when converting the nvarchar value '<?UMBRACO_MACRO macroalias="ucOlav" />' to data type int.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Data.SqlClient.SqlException: Conversion failed when converting the nvarchar value '<?UMBRACO_MACRO macroalias="ucOlav" />' to data type int.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
I endend up re-installing the entire solution. That fixed the problem. Looks like there were something messed up in the old document types I imported from 4.0.2.1.
I have this problem with a fresh install of 4.5.2.... anyone else?
I ended up changing the datatype via SQL manager.
In table cmsDataType, you can find the ID, and change field dbType.
Then everything works like a charm.
Still dunno why it changes to int :-S
is working on a reply...