I looked it up various links like these: Link1, Link2, Link3 I am coming to conclusion that, I cannot fix the issue that I am facing. I have an Error page item, which is calling a sublayout to show different error messages for different codes. Need to produce a proper 404 status code while providing an error page in Sitecore. Same question asked here: Sitecore uses "302 found" to redirect users to my custom 404 page - is that legitimate?
Please refer attached image to see what I am talking about:
Thank you for your inputs!
Did you look at the Sitecore Error Manager module which will let you set different pages for different error codes?
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 saved a SharePoint online modern site as a template and tried to install it to a different site collection within the same tenant. Uploading and activating the .wsp solution worked but when I went to select it as a custom template I received the following error message:
Features not activated
I then used PowerShell to activate the hidden features as described here:
https://praveensharepointknowledgebase.wordpress.com/2018/02/28/activate-hidden-site-features-using-powershell/
I'm now getting the following error message:
Sorry, something went wrong
The field specified with name _TopicHeader and ID {d60d65ff-ff42-4044-a684-ac3f7a5e598c} is not accessible or does not exist.
TopicHeader does not exist
I have been searching the forums for similar messages but so far no luck.
Thoughts?
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).
I am very new to facebook platform. I am facing an issue with like button in some of our pages. This is happening on claires.com site
When I test the below URLs through developers.facebook.com/tools/debug page one is working fine and the other one is failing
This URL works fine http://www.claires.com/store/style-files/Leopard-And-Gold/5600037
This one giving me an error http://www.claires.com/store/goods/Teens/cat310104/Drops/p45198/Feather-Fabulosity-Earrings/
When I inspect the source for the both of the pages I am seeing same parameters provided for both pages.
This is the error I am getting for the second url "The page failed to provide a valid list of administrators. It needs to specify the administrators using either a "fb:app_id" meta tag, or using a "fb:admins" meta tag to specify a comma-delimited list of Facebook users."
But I wonder why this error is happening on one page and not happening in the other page, both provides same kind of meta values
Please let me know what went wrong here...
Thanks
-Sujith
You can solve this issue by adding these namespaces to your HTML tag on your website:
<html ... xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml">
Courtesy of: http://blitzkriegconsultant.blogspot.com/