Problem in provisioning when using stapling to customize sharepoint 2010 blog template - templates

I'm trying to use stapling to customize sharepoint 2010 blog template. I created a stapling feature and another feature for customizing the the site definition (onet.xml). It's work fine for web parts but if I include List Views it gives an error when I'm trying to activate the "customizing feature" (Not the stapling feature)
Error is,
"Error occurred in deployment step 'Activate Features': Cannot complete this action."
This is the xml snippet which causes this problem. (I couldn't post the xml part here)
http://social.msdn.microsoft.com/Forums/en/sharepoint2010programming/thread/6ba343f3-020b-47e5-938c-aeedcf094adc
BTW I'm trying to customize the default page here and my approach is
1) Get a copy of the existing custom page and rename and include in the feature
2) Change the master page of the above file to custom.master
3) Change the layout of the above page without removing "ContentPlaceHolders"
4) In feature element put module element copied from onet.xml
Appreciate if anyone can provide some insite on this.
Thanks
-Madhawa

Try provisioning the file without the View to make sure that your Url and Path attributes are correct. Once an empty page is displaying, add the View XML back. For the List attribute, try using the relative URL path (ex. Lists/Blog) instead of the template ID.

Related

Creating a custom page template in stencil for bigcommerce

I've installed stencil and all its dependencies locally and was able to create a couple custom component but I can't figure out how to set a custom template for a custom "webpage" in bigcommerce.I thought it would be a matter of creating a custom page template (custom-page.html) in /templates/pages/ but that doesn't seem to hook it up. In the legacy version, you were able to select a page template from a dropdown. Is it a matter of uploading the theme via webDAV first? Is there a JS module required or config.JSON setting to register a template? Any help would be much appreciated.
To create custom template for webpage you need to place the file(e.g _custom-page.html that you have created) in template/pages/custom/pages directory.
To test it locally, you need to assign the custom template to the url in .stencil file. For example,
"customLayouts": {
"products": {},
"pages": {"_custom-page.html":"/{you-webpage-url}/"},
"brands": {},
"categories": {}
}
Currently, this feature is in beta and so you cannot assign the custom template to the desired webpage url in bigcommerce server. However you can do so by requesting bigcommerce customer service to enable this feature for your site and by accepting their condition for beta not supporting many features.
Note: Custom template name should start with _(underscore). Check I have changed your file name custom-page.html to _custom-page.html. Also I have assigned the _custom-page.html to pages directory, since you have created custom template for webpage.
Currently, you cannot set custom templates. This is on the roadmap and would be facilitated through the control panel.
This feature is no longer in beta. It is live the correct path for the custom templates for a custom page is templates\pages\custom\page
Upload a file like custompagetemplate.html into this folder.
There was an issue with manifest.json causing this feature not to work. Once this file was removed it was live and active on Bigcommerce.

Sitecore: InvalidOperationException: Post condition failed

I'm relatively new to Sitecore.
In my Pre-Prod server I'm getting below error whenever I click on Content Editor. Page Editor seems to work fine. Please help.
InvalidOperationException: Post condition failed
Log Details are below:
Exception: System.InvalidOperationException Message: Post condition
failed Source: Sitecore.Kernel at
Sitecore.Diagnostics.Assert.ResultNotNull[T](T result, String message)
at
Sitecore.Web.UI.HtmlControls.Data.DataViewFactory.GetDataViewByName(String
name) at
Sitecore.Web.UI.HtmlControls.Data.DataViewFactory.GetDataView(String
name, String parameters) at
Sitecore.Web.UI.HtmlControls.DataContext.GetItem(String id) at
Sitecore.Web.UI.HtmlControls.DataContext.GetState(Item& root, Item&
folder, Item[]& selected
This sounds like something is not right with the config files in the site.
It's very hard to tell exactly what is the issue with that error message. And finding the issue will more than likely be a process of elimination.
I would suggest the the best course of action is to compare the configuration of the site with a known working version or a basic Sitecore install with no customisations. You can use the ShowConfig tool in Sitecore to show you all the configuration settings after the includes (as the config does not just consist of Web.config). More info on this here: -https://sitecorejohn.wordpress.com/2010/03/11/tool-to-examine-sitecore-web-config-after-accounting-for-include-files/
It's worth checking the App_config/include directory in Sitecore to see if you have any modules in place (E.g. Sitecore.MediaFramework.config) that are not in place where your site is working. You can disable these config settings by renaming the file to be .example.
I know it is an old question but in case it helps someone.
Very likely you are trying to access Sitecore Content Editor from your CD node.
Access Sitecore from CM only.

Can't Open Web forms for marketers Form Designer or Security Manager

I have had WFFM running on a Sitecore instance for a while, but it has recently stopped working. When I go to "Form Designer" on an existing form, I get the standard Sitecore "The requested document was not found" page.
Requested URL: /applications/modules/web
User Name: sitecore\admin
Site Name: shell
If the page you are trying to display exists, please check that an
appropriate prefix has been added to the IgnoreUrlPrefixes setting in
the web.config.
Note that the requested URL is stated as /applications/modules/web instead of /applications/modules/web forms for marketers.
A lot of development has occurred on this site recently, so I'm not sure when exactly this started happening.
Additional: info:
Folder and file permissions are correct.
I've tried reinstalling the WFFM package, and made sure that all the files are in place.
Several processors have been added to the HttpBeginRequest pipeline, but I removed them all to test if they were the cause - they weren't.
I haven't upgraded Sitecore since WFFM was working and the version is correct.
No errors are logged
EDIT
This also seems to be affecting the Sitecore Security Editor:
Requested URL: /appl
User Name: sitecore\admin
Site Name: shell
If the page you are trying to display exists, please check that an
appropriate prefix has been added to the IgnoreUrlPrefixes setting in
the web.config.
EDIT 2
Further investigation with this is making me think it is related to the Requested URL. I originally thought the the "Not found" page was displaying the requested url incorrectly. However, if I attempt to goto mysite.com/sitecore/shell/applications/fake folder with spaces/fake page with spaces I get this error message:
Requested URL: /applications/fake folder with spaces/fake page with
spaces
User Name: sitecore\admin
Site Name: shell
If the page you are trying to display exists, please check that an
appropriate prefix has been added to the IgnoreUrlPrefixes setting in
the web.config.
As you can see the Requested Url is correct in the error message. So in relation to my problem, I think maybe Sitecore is requesting the wrong URL in the first place.
Additionally if I go to the go the following url by typing directly into the browser, then the Security Editor opens as expected:
mysite.com/sitecore/shell/Applications/Security/User-Editor
This is quite old now but I thought I'd provide an update for anyone else who encounters the problem.
Unfortunately, Sitecore support weren't able to help beyond pointing out that setting the addAspxExtension attribute to 'true' in the link provider seemed to solve the problem. This may have been acceptable except that extensionless URLs were important to the customer.
In the end I had to amend my link provider so that addAspxExtension is set to 'true' in the web config, and then I set it to false inside the GetItemUrl method for specified sites only.
So now whenever the context site is 'Shell' or 'Admin' etc, the extensions are added by default, but switched off in my main website.
Of course, this is a work around. I still don't know how to actually fix the problem
So the first thing that I am going to tell you is that I suspect that there is something wrong with your site declaration for Sitecore Modules. In your web.config, there's a site declaration for "modules_shell" and "modules_website". Those are where the code files that run the modules are usually located... a shell folder to run the parts that run in the Sitecore shell and a web folder to run the part that is accessed by the externally facing site. Please check your site declarations (and the form.config file) to make sure that you're not in live mode or something like that. I would definitely say that this is where you should start looking.
The next thing is to say that your comments about Sitecore not serving a url in the /sitecore/shell directory is really not surprising. Sitecore processes all requests unless you specifically tell it to ignore requests (like setting it in the IgnoreUrlPrefixes in web.config), it's going to try processing it. Like going to /sitecore/shell/applications gives me a layout error because it doesn't have anything set to handle that request. Now your error suggests that there is something wrong with Site declarations.. however, even if they were all right, it still wouldn't work.

No administrators were specified

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/

Customizing the SharePoint 2010 Blog Template

I want to apply branding to a sharepoint 2010 blog site which is a sub site of our internet. I'm trying to achieve this by creating a custom blog site template based on the original blog site template. So I followed the following blog post.
http://www.sharepointbits.com/blog/sharepoint-2010-custom-site-templates.html
And I got a copy of the blog template files from "C:...\14\TEMPLATE\SiteTemplates\blog", modified the files and put in to the "SiteTemplates\" folder.
I can see a new site template has been created but every time when I create a web site based on my custom template it uses the original blog template files for provisioning (for ex: default.aspx).
Is this the correct way to achieve this? Please let me know if I'm doing sth wrong here.
Thanks in advance.
-Madhawa
Have you created a custom webtemp file in 14\TEMPLATE\1033\XML that has a custom Template Name with a SetupPath that points to your copied folder in SiteTemplates?
Also, the Blog site definition is tricky. The custom lists are built right into the onet.xml file. I wonder if creating a custom copy of the Blog template will work as well as copying other site types would. I would probably use feature stapling to apply custom branding to the out of the box Blog template within your site collection.