Obviously the node ID changes, depending on the node selected. This seems to happen on any number of nodes, not just one specific node.
I click again on the node and it works okay. I then click on another node, which works fine, then on another node and I get back to the same cycle of the 2 errors above, and then one the 3rd click if works okay.
Having gone away from this and then back to it (on the same computer and with the same login), it's now not happening at all. I've tried clicking on content nodes dozens of times and it's not giving any errors at all.
I'm convinced it's something to do with the server (maybe a permissions error since I've seen something similar when I forgot to set up the permissions when copying a whole site from one server to another), but whether it's that, or not, I need to find a solution for the clients sake.
yesterday afternoon, last night, and very early this morning, this issue did not occur at all, having clicked on the different nodes dozens of times.
Now the issue is back
What's more, some other odd behaviour occurs at the same time:
document properties which are in the content tab were initially appearing in another tab, though this has now sorted itself out the other errors are happening as before.
I'm wondering if this is the result of some corrupted files on the server (I can't replicate it on the development server). If this was a v4 site, I'd republish the the entire site, but there doesn't seem to be an equivalent command in v3.
I will re-upload the Umbraco and bin directories to see if that makes any difference.
Input string was not in a correct format - when clicking a content node in v 3.0.5
Sorry, but I couldn't find a better place to put this post.
Has anyone else come across this error when clicking on a content node in v3.0.5 (logged in as admin at the time).
What actually happens is that I click on a content node and I get the error:
I click again on the same node and I get:
Obviously the node ID changes, depending on the node selected. This seems to happen on any number of nodes, not just one specific node.
I click again on the node and it works okay. I then click on another node, which works fine, then on another node and I get back to the same cycle of the 2 errors above, and then one the 3rd click if works okay.
Having gone away from this and then back to it (on the same computer and with the same login), it's now not happening at all. I've tried clicking on content nodes dozens of times and it's not giving any errors at all.
I'm convinced it's something to do with the server (maybe a permissions error since I've seen something similar when I forgot to set up the permissions when copying a whole site from one server to another), but whether it's that, or not, I need to find a solution for the clients sake.
Any ideas?
TIA
Tom Madden
Quix Ltd
Some more info on this issue:
yesterday afternoon, last night, and very early this morning, this issue did not occur at all, having clicked on the different nodes dozens of times.
Now the issue is back
What's more, some other odd behaviour occurs at the same time:
document properties which are in the content tab were initially appearing in another tab, though this has now sorted itself out the other errors are happening as before.
I'm wondering if this is the result of some corrupted files on the server (I can't replicate it on the development server). If this was a v4 site, I'd republish the the entire site, but there doesn't seem to be an equivalent command in v3.
I will re-upload the Umbraco and bin directories to see if that makes any difference.
Tom
is working on a reply...