Blog: error on creating or editing posts

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
6/29/2014 2:13:23 AM
CrispinF
Gravatar
Total Posts 128
View Posts

Blog: error on creating or editing posts

Using latest source code I get an error ("parameter's type doesn't match cached parameters") on creating or editing a blog post (in debug). The problem is the incorrect data type in this line in DBBlog.UpdateBlog:

sph.DefineSqlParameter("@IncludeImageInExcerpt", SqlDbType.NVarChar, 255, ParameterDirection.Input, includeImageInExcerpt);

Stored proc mp_Blog_Update has @IncludeImageInExcerpt bit

This didn't prevent the overall save from working, but we get no error if the above line changes to

sph.DefineSqlParameter("@IncludeImageInExcerpt", SqlDbType.Bit, ParameterDirection.Input, includeImageInExcerpt);

6/29/2014 2:14:04 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Blog: error on creating or editing posts

Thanks for the bug report. This is now fixed in the source code repository.

SQL Server is pretty forgiving about these things as long as the passed data can be coerced to the expected type. So it may not produce an error in production environments, but by design they do throw errors under debug compilation to help us find and fix mistakes like this.

Thanks,

Joe

You must sign in to post in the forums. This thread is closed to new posts.