I am experiencing an odd thing on one of our client's site. Some nodes on different levels have lost their references and they have no URL when you view the "Properties" tab.
After republishing the node it has now an URL and is visible on the site. But after refreshing the site the node is suddenly gone and when I check in the umbraco UI it has no URL anymore.
I've doublechecked all permissions, and they seem fine.
I can think of three things that might create this situation...
1. Can't create/read/update to the /data/umbraco.config file. To test, manually delete the file. Then right-click the top Content node and select the 'republish entire site' menu. The file should reappear.
2. You have some 'unpublish at' fields set on some of your nodes and they auto-unpublish as you'd asked?
3. You have an event handler that forces some nodes to become unpublished. You'd have had to create this yourself as I don't know of any pre-built packages that would do this.
Nodes has no URL's
Hi guys!
I am experiencing an odd thing on one of our client's site. Some nodes on different levels have lost their references and they have no URL when you view the "Properties" tab.
After republishing the node it has now an URL and is visible on the site. But after refreshing the site the node is suddenly gone and when I check in the umbraco UI it has no URL anymore.
I've doublechecked all permissions, and they seem fine.
What may cause this, any ideas?
/ Patrik
I can think of three things that might create this situation...
1. Can't create/read/update to the /data/umbraco.config file. To test, manually delete the file. Then right-click the top Content node and select the 'republish entire site' menu. The file should reappear.
2. You have some 'unpublish at' fields set on some of your nodes and they auto-unpublish as you'd asked?
3. You have an event handler that forces some nodes to become unpublished. You'd have had to create this yourself as I don't know of any pre-built packages that would do this.
Let us know what you find out.
cheers,
doug.
Yes, it was the "Remove at" field that was filled with a date and caused this.
Thank you Douglas!
/ Patrik
is working on a reply...