I have a Sitecore solution that is connecting to an external website using FXM.
When I'm trying to add a new placeholder using FXM I receiving next error but in
logs doesn't appear something related to this error. Please see attached picture
As it seems the Sitecore.Services.Client.FXM.Enabler.config was .disabled and it needs to be enable it in order to make FXM work on the instance.
As #sitecore climber mentioned it can be found on the documentation here.
Related
I was trying to install the default Storefront site(powered by Commerce Server). It looks good at the moment, I managed to rebuild all indexes and publish the content. However, I can't reach product detail page - I receive an exception.
Example here.
I had faced with the similar issue when I tried to click on any catalog category.
The log-file contains the same error message without any details. Could you please suggest something to fix this issue?
P.S. After the finishing the installation I didn't have any products on the site. I fixed that issue:
selected the default Adventure Works catalog in the Sitecore tree(using content manager).
Filled in field CategoryDatasource(with the path to categories)
I think it might cause the error which I described above.
Thank you in advance for the help.
You have to set the catalog for the site via a home node property.
I am trying to update (using PUT operation) a sitecore item with a 'Rich Text' field with the Sitecore ItemWebApi 1.2. I am running in to an issue with the server saying
"A potentially dangerous Request.Form value was detected from the client"
I could do the validationRequest=false in the web.config. But that will disable the validation for all requests which is not ideal. Is there a way to save html text using ItemWebApi without using the validationReques=false? Seems for aspx pages you could use #Page. Not sure where something like that could be configured in this case.
May be you have already figured out the answer for yourself, but in interest of our fellow community I posting answer here.
Actually myself get struck into this similar issue from last week, but because of your question i found the solution.
By Default Sitecore nowdays comes with
<pages validateRequest="false">
but it is not effective until or unless we do following
<httpRuntime requestValidationMode="2.0"/>
It is also indicated in Sitecore KB article and in another stack overflow answer.
Regards
Vishal Gupta
I did double escaping on client before sending to server and double unescaped with a custom item web api processor to essentially achieve the same effect for this one ajax call. This way, I did not have to turn off validation application wide and had to add the validateRequest=true on all pages. Turning of default html validation would also mean every other developer on our team needs to be aware that html validation is turned off and they have to add special xml on top to enable it. Someone missing that will make our site insecure.
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'm trying to upgrade our Web Forms For Marketers to the latest available on SDN, however when I come to install I get the follow exception throw:
Could not find configuration node: databases/database[#id='production']
However, this is correct so far as the only databases configured are Core, Master and Web.
I tried adding a production node (pointing to Master) to Databases.config/ConnectionStrings.config however it still throws this error.
Has anyone encountered this and has a solution?
The error is telling you it cannot find a <database> node in your web.config for "production" so you'll need to have that. Something you have must be referencing that.
The problem lies with a bug in Sitecore not correctly cleaning and rebuilding the Links database.
Sitecore Support provided this solution:
Back up.
Truncate the links table in the Core database.
Rebuild Link Database from the Sitecore Control Panel.
This seemed to solve the issue in the short term. I'm sure it'll be addressed in a Sitecore update in the future.
I am working with the new CFBuilder 2 Beta, and I notice that there is a new feature that is supposed to be able to check my CFC's and give me "Intellisense" on them but I keep receiving and error that says unresolved component.
I have all my mappings set up properly in my CF Administrator and I added the server in CFBuilder and I am able to see the DSN's in the RDS Dataview, but it does not appear as if it is pulling in the mappings for example.
var dates = createObject("component","com.utils.dateFunctions");
The com is mapped to C:\Inetpub\com in my Admin mappings, but again I get that warning when I do createObject.
Is there perhaps a step I missed inside of CFBuilder to get this to work?
I was thinking it should be pulling in my mappings already...
Try this link by the ColdFusion Builder Team, explaining CFBuilder and finding CFCs.
http://blogs.adobe.com/cfbuilder/2011/03/where-coldfusion-builder-finds-my-cfcs.html