I'm using Sitecore.NET 8.1 (rev. 160302), Everything seems to work fine but the Layout Switcher ribbon in experience editor mode is disabled. There is no client error or server error.
The application was updated from Sitecore 8 to 8.1.
Assuming this is a multi-site solution, this blog post states that setting Preview.ResolveSite to true from within the Sitecore.config settings file will resolve the problem. If this property doesn't exist there, your SLN may have a patch for Sitecore settings elsewhere under /App_Config/Include.
I recently set up an 8.1 instance that had this setting set to false by default.
Also, set "SiteResolvingMatchCurrentLanguage" to false for multi-lingual sites where the content editor is using a different language than the site's language. If the sc_site parameter contains the wrong site, the layout buttons get disabled.
Related
I have the latest version of WFMM (Web Forms For Marketers) for Sitecore. When I try to define the restricted placeholders from Desktop -> All Applications -> Web Forms for Maketers -> Restricted Placeholders everything freezes, including IIS.
I have no errors in the browser console or Sitecore's log.txt.
I has same issue with Sitecore 8.0 rev. 150621 (Update-4) and Web Forms for Marketers 8.0 rev. 150625. Sitecore Support helped me:
The //*[contains(#Allowed Controls, '{0}')] query runs on all items from the database. We apologize for any inconvenience this issue may have caused.
I changed the query to search items only under the root item: .//*[contains(#Allowed Controls, '{0}')]
Could you please follow the steps below to address the issue:
Copy the attached Sitecore.Support.406505.dll assembly to /bin folder.
Change the implementation class for forms:selectplaceholders command in forms.config file:
from
<command name="forms:selectplaceholders" type="Sitecore.Forms.Core.Commands.RestrinctingPlaceholders,Sitecore.Forms.Core" />
to
<command name="forms:selectplaceholders" type="Sitecore.Support.Forms.Core.Commands.RestrinctingPlaceholders,Sitecore.Support.406505" />
Here is the linked to the mentioned dll: Sitecore.Support.406505.dll
Restricting Placeholder dialog is an quick way to add WFFM sublayout form and view form to Allowed Controls field in placeholder settings. Selection of placeholders is maintained on last step of installation of module. Everything is already installed, you just need to follow manual poststeps(attach DB, etc). You can continue without solving this problem.
And if you don't have a huge amount of placeholders then it is quicker to do it using Allowed Controls field rather than trying to find root of the problem.
I am working on multisites and I want to open experience editor for the context site, but sitecore doesn't resolve the context site and it always takes me to the default website, there is a setting in sitecore.config file i set it to "true", but still it takes me to the default website :
http://mywebsite.local/?sc_mode=edit&sc_site=website
here is the setting in sitecore.config, my sitecore version is 8.1 (Update 2)
<!-- PREVIEW - RESOLVE SITE
If false, the Preview.DefaultSite setting specifies the context site to use when a user previews an item.
If true, when a user previews an item, Sitecore tries to resolve the root item and the context site based on the current content language
and the path to the item. If Sitecore cannot resolve the context site, it uses the site that is specified in the Preview.DefaultSite setting.
Default value: false (use the value of the Preview.DefaultSite setting)
-->
<setting name="Preview.ResolveSite" value="true"/>
I have also face this issue before and it is known bug in sitecore. I have tried approach mentioned in below article. (However I am still facing this issue intermittently whenever I copy new dll in sitecore website.)
https://kb.sitecore.net/articles/382913
I have already placed all the files at my one drive link. Please take a backup of your existing file ("WebEditRibbon.aspx ) before replacing
https://1drv.ms/f/s!AotVzR-_yI5ObO5-Pzq02mcx-EU
This Reported as bug in Sitecore 8.1 (Update 2), and this is the fix from support team :
Open the “/sitecore/client/Applications/Launchpad/PageSettings/Buttons/ContentEditing/ExperienceEditor” item in the core database
Change the “Link” field value to:
/?sc_mode=edit&sc_resolvelanguage=0
Updated Answer :
For multi-sites, you need to apply anothor fix I did not find its number on https://kb.sitecore.net/ so i uploaded the required files on dropbox :
Download Sitecore.Support.88883.zip, from this Link
Copy the attached Sitecore.Support.88883.dll file to the /bin folder of your website;
Copy the attached Sitecore.Support.88883.config file to App_Config/Include folder of your website;
Open the "/sitecore/client/Applications/Launchpad/PageSettings/Buttons/ContentEditing/ExperienceEditor" item in the core database
Change the “Link” field value to: /?sc_mode=edit&sc_resolvelanguage=1
Clear the browser cache.
So I'm just starting to work in sitecore and for some reason none of menu options are working in Page Editor mode for the site that I'm working on. We pretty much have the sitecore website and add some extra page content (MVC app files) to it. I'm getting a variety of javascript errors.
In content Editor, if I click the Sitecore logo and click on Properties I get
TypeError: contentIframe.dialog is not a function
In page editor if I click on the blue components button I get:
TypeError: i.widget is not a function
I'm guessing maybe it's a conflict between jquery that we're using for this website and whatever Sitecore is using. I think it's 7 - but I can't see it via the menu option :)
That guess could be wrong - it could in fact be a browser issue, but I've ensured Firefox is not blocking popups. It doesn't work in Firefox, IE or Chrome though.
The weird thing is that no one else on the project is having this issue it's only on my computer.
Edit - I've also just tried re-installing (7.2) without any local code changes I still can't click on a page and go to Presentation, Details (Layout) - I get a TypeError: contentIframe.dialog is not a function
Edit 2 - I've noticed that I can use sitecore in the QA environment and the dialogs work fine there. So it's something specific to my local build of the site we have (sitting on top of sitecore). But the dialogs just throw jquery errors when I do stuff locally. I was hoping it would be a browser setting but doesn't look like it.
Edit 3 - What I've tried this morning.
Same thing happens in all browsers (FF, IE, Chrome) and I’ve cleared
my browser cache I can access the QA site and the dialog appears as
expected
Copied across the QA site files, pointed my local Digital
site in IIS to the new folder – dialogs don’t work
Team member tried accessing the site from his machine (pointing to my IP address) and
dialogs work for him
I tried seeing if another local sitecore site dialogs were working – but the menu items for that are opening as new windows (so I’m guessing it’s a sitecore 7.2 feature that they appear as jquery dialogs??)
So after googling for rejected-by-urlscan it turns out there's a program called UrlScan from microsoft that was blocking my dialogs. Uninstalled that and I now have dialogs appearing for sitecore. Very exciting :)
I guess it is a problem with some browsers plugin. Sitecore is sensitive to scripts that are used(different versions of jquery or prototype.js). Plugins can inject scripts to HTML source of pages and it can cause errors.
Try to switch off all plugins at least at one browser and check the results.
I have a bit of a weird bug on a website I'm working on. I have multiple themes configured in the Forms Folders in Web Forms For Marketers. No matter what theme or color I select, all of my forms use the theme and color selected for the Website folder. I tested this with a clean install and it worked fine, this is a bug on my specific website.
Here's what I'm working with:
CMS 6.5.0 rev. 120427
DMS 2.0.1 rev.120427
Web Forms for Marketers-2.3.0 rev. 120216
Any ideas?
This is by design. From Sitecore Support, when I raised the same issue a while back:
Edited by Alexander Yaremenko on Thursday, November 18, 2010 at 2:10
PM
Hi Mark,
This is expected behavior. The Theme and Color defined for all forms
for the current site. If you run site (For example Site1) all web
forms will have themes from forms folder that defined in formsRoot
attribute for current site instead of theme from forms folder that
stored this form.
I have registered a wish that we can change this behavior in future.
I can't find the easier way to change this behavior now. I see only
one workaround: Create you custom control which will be insert link to
needed .css on the page. Note: the link to your .css should be defined
below then standard .css.
The Sitecore Support case reference is 336904.
In essence, WFFM assumes themes to be "per site", not multiple themes in the same site.
When we set the addAspxExtension web.config setting to true for our website, debug mode stops working for all pages of our site except for the homepage. When I say that it stops working I mean that it displays the actual page but without the Sitecore ribbon and profiling information.
I guess we could apply this setting only in our content delivery environments and leave it on (addAspxExtension="true") for our content entry environment but I was wondering if anyone has managed to get around this issue?
Update
Until Sitecore resolves this issue I have decided to only set the addAspxExtension setting to "true" in our Preview and Production environments. That way the debug mode will still work in our development environment.
As of right now, this issue is a bug that Sitecore is aware of and should hopefully be fixed by the next update. There are basically 2 workarounds for it:
Set the addAspxExtension attribute to “false” value.
Manually write the .aspx extension to other URLs which are different from the home page.
Hope that helps..