As you say, it is showing a 404. First, I'd check each and every ancestor page, including the homepage, to ensure the "Link to document" on the "Properties" tab is the correct URL. That means you should check the properties tab of each of these pages:
I find that sometimes (for whatever reason) ancestor pages can become unpublished, which causes all descendant pages to become unpublished. Usually, this manifests by the "Link to document" appearing as "#" (i.e., a hash character) rather than the correct URL.
You might also confirm that the "Template" is set on the properties tab for each of those pages. And confirm that whatever template they are set to exists in the developer section and on the file system. Additionally, confirm that all of the layouts used by your templates exist on the file system.
Also, confirm that when you publish a content node, an entry is created in the Umbraco log that says a content node was published, in addition to confirming no other errors are added to the Umbraco log when you perform that publish.
I would also recommend you add any extra information here that may be useful in troubleshooting. For example, the Umbraco version you are using, and if you are using any custom URL providers or content finders. Also, can you create new pages and do they also show up as a 404? A screenshot of the back office content tree could be useful too (e.g., to confirm that the pages are actually published and not just saved).
Yes it seems that if the domain (http://roldskov.sp34k.dk/) is removed from the Culture and Hostnames (forside node), all the subpages works, but then the frontpage doesn't work.
How do I tell umbraco that the default.aspx page should be the frontpage/forside node? I have always done this through the Culture and hostnames.
Oh and thank you once again for diggin' into this issue and helping me out :)
Why would you want the homepage to use the default.aspx file? For one, Umbraco has never worked with aspx files. It now defaults to CSHTML and previously used MASTER files, I believe.
Here, we can clearly see the problem is that the homepage is using the "Master" template:
And in the settings section, we can clearly see that the "Master" template should only be used as a layout and not as a view:
Based on the naming, I'd guess you would want to use the "Frontpage" template (also shown in the above screenshot).
Furthermore, you appear to have created the homepage node with the "Master" document type, whereas I suspect you should have created it with the "Frontpage" document type:
If that's true, you will likely want to create a new homepage node, move all the old pages under the new homepage, then delete the old homepage.
No umbraco document matches the url
Hi everyone,
I need a superhero to rescue me right now.
Online and locally I can't access any pages beside my frontpage at roldskov.sp34k.dk
What am I missing?
Let's take this page for example: http://roldskov.sp34k.dk/produkter/tilbehoer/pedaler/look/
As you say, it is showing a 404. First, I'd check each and every ancestor page, including the homepage, to ensure the "Link to document" on the "Properties" tab is the correct URL. That means you should check the properties tab of each of these pages:
I find that sometimes (for whatever reason) ancestor pages can become unpublished, which causes all descendant pages to become unpublished. Usually, this manifests by the "Link to document" appearing as "#" (i.e., a hash character) rather than the correct URL.
You might also confirm that the "Template" is set on the properties tab for each of those pages. And confirm that whatever template they are set to exists in the developer section and on the file system. Additionally, confirm that all of the layouts used by your templates exist on the file system.
Also, confirm that when you publish a content node, an entry is created in the Umbraco log that says a content node was published, in addition to confirming no other errors are added to the Umbraco log when you perform that publish.
I would also recommend you add any extra information here that may be useful in troubleshooting. For example, the Umbraco version you are using, and if you are using any custom URL providers or content finders. Also, can you create new pages and do they also show up as a 404? A screenshot of the back office content tree could be useful too (e.g., to confirm that the pages are actually published and not just saved).
Hi Nicholas,
Thank you for reading my post and helping me out, I appreciate that!
Alrighty, first thing first, the details:
Since there's nothing to hide on my side, you are more than welcome to login:
I'm heading off to bed now. Perhaps somebody else can hop on and assist in the meantime.
By the way, those credentials don't seem to work.
Seems to work now, in terms of no longer being a 404. And I was able to log in. However, looks like you've got another error:
Hey Nicholas! :o)
Yes it seems that if the domain (http://roldskov.sp34k.dk/) is removed from the Culture and Hostnames (forside node), all the subpages works, but then the frontpage doesn't work.
How do I tell umbraco that the default.aspx page should be the frontpage/forside node? I have always done this through the Culture and hostnames.
Oh and thank you once again for diggin' into this issue and helping me out :)
Why would you want the homepage to use the
default.aspxfile? For one, Umbraco has never worked with aspx files. It now defaults to CSHTML and previously used MASTER files, I believe.Here, we can clearly see the problem is that the homepage is using the "Master" template:
And in the settings section, we can clearly see that the "Master" template should only be used as a layout and not as a view:
Based on the naming, I'd guess you would want to use the "Frontpage" template (also shown in the above screenshot).
Furthermore, you appear to have created the homepage node with the "Master" document type, whereas I suspect you should have created it with the "Frontpage" document type:
If that's true, you will likely want to create a new homepage node, move all the old pages under the new homepage, then delete the old homepage.
And that my friend, was the answer! I created a "Frontpage" node at the Content Root with all it's children pages, and it worked!
I guess I did it wrong using the Master at content root. I have always done this because of the "footer" content which should be used on all pages.
Thank you Nicholas, for being so patient with me and helping me out here! I really appreciate it!
is working on a reply...