When I click on a Joomla article link it shows this error 'Error: 404 - COM_CONTENT_ERROR_PARENT_CATEGORY_NOT_FOUND'. To be specified I have used 'mod_roksprocket' (Mosaic Layout) module to show a list of articles within a category. There are the 'read more' button to navigate through the articles details. Hence, clicking on this button triggered the describing error. I have searched a lot to get out of this riddle and everyone suggest for disabling the SEF url from Global Configuration. However, SEF url is a strict condition from my client.
Related
When a 404 error is thrown in a project that uses Wagtail, I'd like to have the site redirect to a page in the CMS. How do I do this?
I know Wagtail has a redirects feature, but that doesn't seem to do what I want; if I were to use that I'd need to have some kind of wildcard selector that would be superseded by more specific redirects.
I searched around the issues but this was as close as I found. But that seems to be more related to admin 404s if I'm reading it right.
I've just set up a new GitHub Pages page: https://philipnye.github.io/ainfo. I'm not using Jekyll.
My GitHub repo has a web folder that itself contains a number of sub-folders, e.g. web/2044. Within each is an html file, with a name such as Abbey-Academies-Trust.html.
I was expecting to be able to view the relevant page at https://philipnye.github.io/ainfo/web/2044/Abbey-Academies-trust.html, but I'm getting a 404 error.
In that particular folder - web/2044 - I've also created an index.html file, but I'm getting a 404 error for https://philipnye.github.io/ainfo/web/2044/index.html too.
I'm clearly missing something, but I can't see anything in the documentation that suggests why this isn't working.
For the first url, it's a caps problem on Trust : https://philipnye.github.io/ainfo/web/2044/Abbey-Academies-Trust.html.
For the second url everything is ok. The problem was certainly that you have near 2000 pages and that Github page took a while to generate your site.
I've inherited the maintenance of a multi-site instance of Sitecore (v6.5) that we're starting to see some cross-talk of pages. The content is structured as follows:
/sitecore
/content
/Site1
/Metadata
/Nav
/archived pages
/archived page1
/Home Page
/Internal Page1
...
/Site2
/Metadata
/Nav
/archived pages
/Home PAge
/InternalPages
...
For this example, site definitions are patched in such that www.site1.com has a rootPath of /sitecore/content/ and a home item Site1/Home page, www.site2.com has a similar rootPath of /sitecore/content/ and a home item Site2/Home page.
The content owners will move pages out from under the "Home Page" node to a folder called "archived pages" when they don't want them on the site anymore.
What I'm curious is if there is a way to prevent the following URL:
http://www.site2.com/sitecore/content/Site1/Metadata/archived1pages/archived-page1
Rendering.SiteResolving is currently set to true, so neither site should be producing links like this, but I'd like a way to have this sort of URL return a 404 without having to resort to writing a custom pipeline component. Am I missing a simple configuration to prevent this?
Try this, make "archived pages" folder item "un-publishable" on all sites, do a publish site (smart publish), now all of archived pages are not on web database, because the parent folder is not publishable, and you should see a 404 page when hit this URL:
http://www.site2.com/sitecore/content/Site1/Metadata/archived1pages/archived-page1
We're running Sitecore in a multi-site configuration and currently have custom 404 pages for each of our sites.
What we would also like is to have custom 500 pages for each site. I haven't found much on how that works (if it does) in Sitecore, and was hoping the community had some insight into how to set up custom 500 pages in a multi-site Sitecore setup. Currently, we have one 500 page the two sites share. This is fine in development, but in production we don't want to expose the fact that these sites share the same box.
Well as per my knowledge, what you can do is you can directly set a URL to be executed (.i.e. it goes to your common Custom Error Page), where you decide the site-specific error details to be shown.
Considering that you are using IIS 7.0 or 7.5, please follow the steps as below:
Open IIS Manager
Go to your Site, in the Sites Section.
Click on Error Pages in the IIS Section.
Next, you will move to the Error pages set by IIS. Go to Error code 500, select it and click on Edit in Actions Pane.
Now select the option of Execute a URL and select a common page, say /sitecore/MyErrorPage/500ErrorPage.aspx and then, handle site-specific error messages in that particular page.
Hope this Helps!
Regards,
Varun Shringarpure
A 500 error is a server error so Sitecore can't process it. It should be a generic flat HTML file configured is IIS or the web.config
You can override the processor "Sitecore.Pipelines.HttpRequest.ExecuteRequest, Sitecore.Kernel" to handle Sitecore error like item not found, layout not found etc. See more details here: http://www.sitecore.net/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2013/04/Handling-Errors-in-the-Sitecore-ASPNET-CMS.aspx
But when handling 500 errors you should do it outside of Sitecore, think about what happens if you serve your 500 error page in Sitecore but Sitecore is down due to for example sql connection issues or timeouts? Your users will end I a redirect loop.
Take a look at the Error Module on the marketplace. I think it will give you want you want.
I have a large Sitecore site which is working with almost no issues, but there is one particular page which renders as blank. No menus or layout and no errors. No errors are recorded in the database.
When I preview that same page through the CMS, no problem.
The page has been published, as has its layout and template.
Has anyone experienced something like this before?
Well this is a bit embarrassing - actually there is a directory under my website with the same name as the page I am browsing to. Of course IIS doesn't pass the request on to Sitecore, it just says "hey I found that resource" and in my case, returns a blank page.
I would have expected a directory listing or an error message in this case, but a blank page is what I get.
Nothing to do with Sitecore, but it could affect anyone working with a CMS.
(PS this is a pre existing site I've recently started working on).