I keep getting this error when I publish a page. I just upgraded to 6.0.1 form 6.0.0 and had hoped that it would solve my problem, but now I think it has to do with my data.
It was an upgrade from 4,11,4 - my problems started in 4.11.3 - when I ´look at the data I can't see that it's much different from a clean 6.0 installation
In 6.0 I had this problem with instant re-publish and a growing log ffile - 240 mb per day.
I upgraded about a month ago and have been strugling with it ever since. I have giving up and I'm now reinstalling the site in 6.0.2. I like the database design of 6.0 and the release appears to be good in a new install.
I just concluded that my data was sick and I couldn't fix it - had all the problems with continous publishing and the log file grew to 250 mb per day.
Thanks again for all your assistence - really appreciate it.
As I open my site today to start developing again my script failed again. It now turned out that that I had a Descendant().Where - it was supposed to be Descendant.Where.and now it works again.
But it worked yesterday - I just upgraded to 6.0.2 - is there some sort of caching here that's teasing - can I switch it of when developing?
Value cannot be null, Parameter name: attribute
Hi
I keep getting this error when I publish a page. I just upgraded to 6.0.1 form 6.0.0 and had hoped that it would solve my problem, but now I think it has to do with my data.
Any ideas?
/Paul S
Hi Paul
Was your 6.0 installation a clean install? Or was it upgraded from v4.x?
/Jan
Hi
It was an upgrade from 4,11,4 - my problems started in 4.11.3 - when I ´look at the data I can't see that it's much different from a clean 6.0 installation
In 6.0 I had this problem with instant re-publish and a growing log ffile - 240 mb per day.
/Paul S
Hi Paul
When you did the upgrade to 4.11.4 did you then run the path fixup script? You can read about the recommended upgrading approach here http://umbraco.com/follow-us/blog-archive/2013/2/1/umbraco-4114-released.aspx
Not sure how to deal with it when you're already on 6 though...
/Jan
Hi Jan
I upgraded about a month ago and have been strugling with it ever since. I have giving up and I'm now reinstalling the site in 6.0.2. I like the database design of 6.0 and the release appears to be good in a new install.
I just concluded that my data was sick and I couldn't fix it - had all the problems with continous publishing and the log file grew to 250 mb per day.
Thanks again for all your assistence - really appreciate it.
/Paul S
Hi again
As I open my site today to start developing again my script failed again. It now turned out that that I had a Descendant().Where - it was supposed to be Descendant.Where.and now it works again.
But it worked yesterday - I just upgraded to 6.0.2 - is there some sort of caching here that's teasing - can I switch it of when developing?
/paul S
Hi Paul
Yes that seems like the best way to go about fixing the issue.
Hope all is running smoothly now - can't wait to get a chance to play with 6.0.2 myself :)
Hmm, not sure about the caching stuff though...I think I'll have to answer "there might be"...Could seem like it from your description above.
Let us know if you experience something like this again.
/Jan
is working on a reply...