What version of Umbraco do you experience this on? And have you made any custom stuff using the API like hooking in to a Save event or something? And are you using MNTP, which is perhaps having a startnode ID that does no longer exist?
I think you should check to see if there is a weird character in on of your document type aliases. In my experience this happens when for some weird reason an alias somehow contains _ or - if I remember correctly. So try looking for this and see if it helps to change the alias.
Thanks for reply.my umbraco version is 4.7.1.1 .The same method and document type are used in local and staging and its working fine.The issue happen in our live site.We take backup of our live site and restored in our local then we can publish it and working fine.But our problem is its an ecommerce site we cannot backup and restore it in Live.
Please see the below error which shows on stack trace.
Ok, but try checking the aliases of all your document types and see if something looks weird in one or more of them. I've seen the # issue when the aliases somehow have been messed up for some weird reason.
The bug means that when you move/delete some nodes, the paths arent updated correctly and you get this error. I actually had the same problem and shannon solved the problem in the core for version 6.0 and 4.11.4 (I think).
I still think you're dealing with the described bug.
If I were you I'd try upgrading.
But you should do this on a copy of your site. E.g, copy your site and database, set it up on another site or locally. Then try the upgrades to at least 4.11.4
Possibly to v. 6 if you'd like, each time testing thorougly if all the packages work as expected. Also read up on breaking changes in each release's release notes. It should help you see if anything breaks. If something breaks, then check for a never and compatible version of the package that breaks and try an update.
I recently updated a few sites form 4.7 to 6.0 (taking one version at the time), and I had no problems. But the sites were small and only a few packages.
"Value cannot be null. Parameter name: attribute" when publishing the node
Hi,
when publishing the node it shows error "Value cannot be null.Parameter name: attribute" I tried all method in " http://our.umbraco.org/wiki/reference/api-cheatsheet/publishing-and-republishing" but again it showing the same errors.The Conent node property "Link To document" always shown #.Please help guyz .
regards
mithun
Hi Mithun
What version of Umbraco do you experience this on? And have you made any custom stuff using the API like hooking in to a Save event or something? And are you using MNTP, which is perhaps having a startnode ID that does no longer exist?
I think you should check to see if there is a weird character in on of your document type aliases. In my experience this happens when for some weird reason an alias somehow contains _ or - if I remember correctly. So try looking for this and see if it helps to change the alias.
Otherwise please ellaborate a bit more :)
/Jan
Hi Jan,
Thanks for reply.my umbraco version is 4.7.1.1 .The same method and document type are used in local and staging and its working fine.The issue happen in our live site.We take backup of our live site and restored in our local then we can publish it and working fine.But our problem is its an ecommerce site we cannot backup and restore it in Live.
Please see the below error which shows on stack trace.
Hi Jan,
Creating document type and property are added through Manually,No custome methods or API is using.
regards
mithun
Hi Mithun
Ok, but try checking the aliases of all your document types and see if something looks weird in one or more of them. I've seen the # issue when the aliases somehow have been messed up for some weird reason.
/Jan
Hi jan,
The Same udt is used in staging site it is working fine.Is there any node limit for umbraco ,currently the error creating node has id 16948
copying the database and App-Data from live site to staging will not recreate the issue.
regards
mithun
Hi Umbraco team,
Please help to solve this issue,Any document type create manually and node is publish it shows error
"Value cannot be null. Parameter name: attribute"
eg:-create document type "testdocument " manually as in setting section
and create node in content section and publish it shows error.
regards
mithun
Hi ,
Find solution ,just replace the App_Data contain umbraco.Config file with old one ,its work fine .
regards
mithun
On RC6 I am receiving the same error on publish:
"Value cannot be null. Parameter name: attribute"
Have a look here: http://our.umbraco.org/forum/using/ui-questions/37750-4113-Publish-exception-Value-cannot-be-null
Looks like there is a new 6.0 stable release today.. I'll upgrade and hopefully fix the problem.
Hi
Again causing this issue.This time umbraco.config replaces doesn't solving the issue.guys please help
regards
mithun
Hi mithun,
are you still on 4.7.1.1 or did you upgrade?
Matthias
This is a bug, has been reported and solved here:
http://issues.umbraco.org/issue/U4-1491
The bug means that when you move/delete some nodes, the paths arent updated correctly and you get this error. I actually had the same problem and shannon solved the problem in the core for version 6.0 and 4.11.4 (I think).
He published a package that fixes these issues here; http://our.umbraco.org/projects/developer-tools/path-fixup
You should read through the issue-tracker, it explains it fully.
I think installing the above package and running the pathfix in the backend (it adds a tab to the dashboard) should fix your problem :)
Cheers,
Niels
Hi ,
Can i install this package on 4.7.1
There is lots of other packages running in my site ,Is upgrading to v6.0 may cause other packages not running ?
regards
mithun
Hi Guys
Please help ...
we are in critical situation...
Advance thanks and regards
mithun
I see we have 2 topics now ;)
http://our.umbraco.org/forum/ourumb-dev-forum/bugs/38574-Value-cannot-be-null-Parameter-name-attribute-
I still think you're dealing with the described bug.
If I were you I'd try upgrading.
But you should do this on a copy of your site. E.g, copy your site and database, set it up on another site or locally. Then try the upgrades to at least 4.11.4
Possibly to v. 6 if you'd like, each time testing thorougly if all the packages work as expected. Also read up on breaking changes in each release's release notes. It should help you see if anything breaks. If something breaks, then check for a never and compatible version of the package that breaks and try an update.
I recently updated a few sites form 4.7 to 6.0 (taking one version at the time), and I had no problems. But the sites were small and only a few packages.
Hope you solve this!
/Niels
Hi Niels,
Thanks ,we are trying to upgrade
One think i found in umbraco is umbraco.config is not updating when it has 20k nodes.we deleted 6k nodes it is working properly.
Thanks & Regards
mithun
20 K nodes... wow.
Hopefully you will be succesfull in your upgrades.
is working on a reply...