In umbraco 4.7 installation with uBlogsy 2.0 beta, I tried creating a blog post from the dashboard - in a blog I'd set up beneath my site's home page. This gave the following error:
Server Error in '/' Application.
Year, Month, and Day parameters describe an un-representable DateTime.
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.ArgumentOutOfRangeException: Year, Month, and Day parameters describe an un-representable DateTime.
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.
Same error also arises when changing the date of a post in the date folders to a new date - seems that there's a problem with creating new date folders. When I reload nodes, I have a blank month / day folder where it seems to have aborted part-way through the process.
I did have Auto Sort installed - I've uninstalled that, and now I can create posts from the dashboard (I guess there was a conflict there?), but it still does not work from within the tree and I can't move posts from one date to another.
Still having problems with this - a bit more info though... When creating a post from the dashboard, it all works fine if all the date folders already exist (year, month, day). But if not, then the error arises.
The same is true within the tree - if I manually create the date folders (year, month, day) and then create a post under the day folder, it's fine. But if I try to create a post for a date which doesn't yet have full date folders created, the error arises. The same is true if I try to change the date to a date where the date folders aren't all present.
Creating a new post by either method does actually create a post, and also a date folder - both are visible after reloading the nodes. The datefolder(s) is/are un-named / blank (presumably why the erros is triggered) and the post date in the post is empty (presumably causing the date folder to be blank?).
Just wrote an update on this, which seems to have been lost when I submitted it! Anyway, here goes again...
I did a clean install of uBlogsy 2.0 beta on a fresh installation of Umbraco 4.7 - and everything worked fine. So that would seem to eliminate the regionalised date time.
I then checked the properties on the clean install vs the properties on the installation where I'm having the problems - all the properties were present.
I then went to the landing page / general settings tab and adjusted the month and day format settings to match the site which is giving me problems. And the issue recurred. So it's clearly something to do with these.
I had a look in the database to see if that showed what's going on. It does. In the dbo.csmPropertyData table, for the clean installation before any changes, the month field is set to 30 and the day field is set to 35. That's when it works ok.
When saving the landing page, without changing the month / day format folders (by default neither radio button appears to be selected), the records in the database are cleared and show NULL. That's when the errors start - when both fields are NULL, the month and day folders created are both blank and the error is shown.
When the day and month formats ARE set, the options are 39-40 (day) and 45-48 (month) - but the defaults on installation (which work) are 35 and 30 respectively. So it looks like the settings aren't matched up correctly? Perhaps a result of the recoding for v2.0?
OK - so if I change the database for the main site where I was having this issue originally to show 30 and 35 for the month and day fields, then it seems to work. But of course when I (or a user) edits the settings on the landing page, the error will recur.
It seems that the processes which create the folders are looking for IDs which match 30 and 35 (or presumably other options in that range from where this was originally set up). But when the package is installed on an existing site, the values assigned to the options for the Day Format and Month Format data types will be different. This seems to be the cause of the problem.
I'll disable editing the landing page for now, until this is fixed.
This is due to the radio button list which is an umbraco datatype. I was under the assumption that the values umbraco gave to each item would remain the same when the datatype was installed.
If it is true that they change then that is annoying and i'll have to write my own datatype to do that configuration. Unless you suggest a better way?
I think it's inevitable that the value of the items in the datatype will change for each (existing) installation, as the values seem to be assigned on a sequential basis. So if an installation has a different number of values already set up compared to yours setup, then this difference will arise. In my installation attempts, the numbers vary from case to case, depending on what else is installed.
So yes, a custom datatype is probably needed.
As a short term fix, and rather than preventing any edits to the landing page, I've just replaced the datatypes for the month and day type fields with numeric fields which I've set manually to 30 / 35. Of course, this doesn't look great to users and it doesn't give them the other day/month options, but it does work!
What's changed from beta to beta 2, and what's the safest way to upgrade from one to the other - is it just a case of overwriting some files in the bin? If so, which?
2.0 beta - create post from dashboard error
In umbraco 4.7 installation with uBlogsy 2.0 beta, I tried creating a blog post from the dashboard - in a blog I'd set up beneath my site's home page. This gave the following error:
Server Error in '/' Application.
Year, Month, and Day parameters describe an un-representable DateTime.
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.ArgumentOutOfRangeException: Year, Month, and Day parameters describe an un-representable DateTime.
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:
The same happens when trying to post from the dashboard to the "My Blog" included with the package.
Any idea what's wrong here?
Thanks
Allan
Same error also arises when changing the date of a post in the date folders to a new date - seems that there's a problem with creating new date folders. When I reload nodes, I have a blank month / day folder where it seems to have aborted part-way through the process.
I did have Auto Sort installed - I've uninstalled that, and now I can create posts from the dashboard (I guess there was a conflict there?), but it still does not work from within the tree and I can't move posts from one date to another.
Hope this helps
Allan
Still having problems with this - a bit more info though... When creating a post from the dashboard, it all works fine if all the date folders already exist (year, month, day). But if not, then the error arises.
The same is true within the tree - if I manually create the date folders (year, month, day) and then create a post under the day folder, it's fine. But if I try to create a post for a date which doesn't yet have full date folders created, the error arises. The same is true if I try to change the date to a date where the date folders aren't all present.
Creating a new post by either method does actually create a post, and also a date folder - both are visible after reloading the nodes. The datefolder(s) is/are un-named / blank (presumably why the erros is triggered) and the post date in the post is empty (presumably causing the date folder to be blank?).
Allan
Hi
Have you removed any properties?
Can you show me a screen shot of your content tree.
My only other thought is regionalized date time which I thought I took care of. What region is your computer set to?
Just wrote an update on this, which seems to have been lost when I submitted it! Anyway, here goes again...
I did a clean install of uBlogsy 2.0 beta on a fresh installation of Umbraco 4.7 - and everything worked fine. So that would seem to eliminate the regionalised date time.
I then checked the properties on the clean install vs the properties on the installation where I'm having the problems - all the properties were present.
I then went to the landing page / general settings tab and adjusted the month and day format settings to match the site which is giving me problems. And the issue recurred. So it's clearly something to do with these.
I had a look in the database to see if that showed what's going on. It does. In the dbo.csmPropertyData table, for the clean installation before any changes, the month field is set to 30 and the day field is set to 35. That's when it works ok.
When saving the landing page, without changing the month / day format folders (by default neither radio button appears to be selected), the records in the database are cleared and show NULL. That's when the errors start - when both fields are NULL, the month and day folders created are both blank and the error is shown.
When the day and month formats ARE set, the options are 39-40 (day) and 45-48 (month) - but the defaults on installation (which work) are 35 and 30 respectively. So it looks like the settings aren't matched up correctly? Perhaps a result of the recoding for v2.0?
OK - so if I change the database for the main site where I was having this issue originally to show 30 and 35 for the month and day fields, then it seems to work. But of course when I (or a user) edits the settings on the landing page, the error will recur.
It seems that the processes which create the folders are looking for IDs which match 30 and 35 (or presumably other options in that range from where this was originally set up). But when the package is installed on an existing site, the values assigned to the options for the Day Format and Month Format data types will be different. This seems to be the cause of the problem.
I'll disable editing the landing page for now, until this is fixed.
Nice investigating.
This is due to the radio button list which is an umbraco datatype. I was under the assumption that the values umbraco gave to each item would remain the same when the datatype was installed.
If it is true that they change then that is annoying and i'll have to write my own datatype to do that configuration. Unless you suggest a better way?
I think it's inevitable that the value of the items in the datatype will change for each (existing) installation, as the values seem to be assigned on a sequential basis. So if an installation has a different number of values already set up compared to yours setup, then this difference will arise. In my installation attempts, the numbers vary from case to case, depending on what else is installed.
So yes, a custom datatype is probably needed.
As a short term fix, and rather than preventing any edits to the landing page, I've just replaced the datatypes for the month and day type fields with numeric fields which I've set manually to 30 / 35. Of course, this doesn't look great to users and it doesn't give them the other day/month options, but it does work!
Damn that is really annoying.... i'll have to write my own radiobutton list datatype i guess.
Hey,
I getting this same error. Even when I put in the Month and Day Manually with integers it still occuring. Has anyone got any other work arounds?
Or can I get the source code, so I can manually set for now?
Are you on beta or beta 2?
beta 2 fixes this issue.
oh cheers, I missed that released.
Thanks
FYI, I'm loving uBlogsy it is pretty much exactly what I need :)
What's changed from beta to beta 2, and what's the safest way to upgrade from one to the other - is it just a case of overwriting some files in the bin? If so, which?
Thanks
Allan
Dlls will do it.
It's just bug fixes. Make sure that you have not renamed the month and day format datatype values.
Thanks Anthony - that seems to have cured quite a few things.
Sweet.
Please let me know if you have any more issues. The sooner the bugs get ironed out of 2.0, the sooner it will be in release :)
is working on a reply...