I have created a custom page layout through visual studio 2013 on which there are a large number of controls are registered. The page that I had created through the page layout on that page I faced this max control limit issue. Generally , when working with a SharePoint master page, page layout, forms we might will face this type of issue.
The problem was we have a large number of controls registered. The limit is set in the web.config file. By Default controls limit is set by 200.
To resolve this issue open the web.config file, located in a virtual directory in c drive. Find the safe control block as shown below and increase the "MaxControls" limit and do IISRESET.
I have created a custom page layout through visual studio 2013 on which there are a large number of controls are registered. The page that I had created through the page layout on that page I faced this max control limit issue. Generally , when working with a SharePoint master page, page layout, forms we might will face this type of issue.
The problem was we have a large number of controls registered. The limit is set in the web.config file. By Default controls limit is set by 200.
To resolve this issue open the web.config file, located in a virtual directory in c drive. Find the safe control block as shown below and increase the "MaxControls" limit and do IISRESET.
For publishing site it is recommended to hide "_layouts" pages from crawling by search engines. When you create SharePoint public facing site using "publishing site" template it activates the feature "ViewFormPagesLockDown". This feature prevents users from opening any of pages from &_layouts folder.
For publishing site it is recommended to hide "_layouts" pages from crawling by search engines. When you create SharePoint public facing site using "publishing site" template it activates the feature "ViewFormPagesLockDown". This feature prevents users from opening any of pages from &_layouts folder.
For publishing site it is recommended to hide "_layouts" pages from crawling by search engines. When you create SharePoint public facing site using "publishing site" template it activates the feature "ViewFormPagesLockDown".
For publishing site it is recommended to hide "_layouts" pages from crawling by search engines. When you create SharePoint public facing site using "publishing site" template it activates the feature "ViewFormPagesLockDown".
For a SharePoint public facing website when anonymous users tried to access the site through mobile devices, users were getting authentication prompts.
The public facing site was created based on "Team site" Template.
It has been observed that users were being redirected to a layouts page at /_layouts/mobile/mblwp.aspx. It seemed to be this page that was returning a 401 error and prompting for authentication.
By deactivating "ViewFormPagesLockDown" feature site open up in mobile view.
Disable-SPFeature -Identity "ViewFormPagesLockDown" -URL "your site url"
Once this command is executed, re-apply anonymous setting again and now site accessible through mobile device.
For a SharePoint public facing website when anonymous users tried to access the site through mobile devices, users were getting authentication prompts.
The public facing site was created based on "Team site" Template.
It has been observed that users were being redirected to a layouts page at /_layouts/mobile/mblwp.aspx. It seemed to be this page that was returning a 401 error and prompting for authentication.
By deactivating "ViewFormPagesLockDown" feature site open up in mobile view.
Disable-SPFeature -Identity "ViewFormPagesLockDown" -URL "your site url"
Once this command is executed, re-apply anonymous setting again and now site accessible through mobile device.
To create site column, content type and page layout for multilingual site first we have add resource file in our SharePoint project. The basic mechanism of localizing a SharePoint 2013 feature is same as we have in SharePoint 2010 and in Moss 2007. Resource File To deploy resource file to…
To create site column, content type and page layout for multilingual site first we have add resource file in our SharePoint project. The basic mechanism of localizing a SharePoint 2013 feature is same as we have in SharePoint 2010 and in Moss 2007. Resource File To deploy resource file to…
We can get values of Custom local properties of Term using Client Object Model. Register following files on your page: <SharePoint:ScriptLink ID="spPage" Name="sp.js" LoadAfterUI="true" Localizable="false" runat="server" /> <script type="text/javascript" src="../../../_layouts/15/SP.Taxonomy.js"></script> Js code to get Custom Local Property values: $(document).ready(function () { SP.SOD.executeOrDelayUntilScriptLoaded(loadAllTerms, 'SP.Taxonomy.js'); }); //loads all existing terms function…
We can get values of Custom local properties of Term using Client Object Model. Register following files on your page: <SharePoint:ScriptLink ID="spPage" Name="sp.js" LoadAfterUI="true" Localizable="false" runat="server" /> <script type="text/javascript" src="../../../_layouts/15/SP.Taxonomy.js"></script> Js code to get Custom Local Property values: $(document).ready(function () { SP.SOD.executeOrDelayUntilScriptLoaded(loadAllTerms, 'SP.Taxonomy.js'); }); //loads all existing terms function…
Many times there is requirement for SharePoint 2010 public facing site to use short url. Like http://example.com/BussinessBanking instead of http://example.com/Pages/BussinessBanking.aspx
URL Rewrite is a URLs management component for IIS7. Although it's called URL Rewrite but it allows you to create and manage both URL rewrites and redirects.
Many times there is requirement for SharePoint 2010 public facing site to use short url. Like http://example.com/BussinessBanking instead of http://example.com/Pages/BussinessBanking.aspx
URL Rewrite is a URLs management component for IIS7. Although it's called URL Rewrite but it allows you to create and manage both URL rewrites and redirects.