I'm trying to find an official answer to my question:
Can I use DelegateControl in Sharepoint 2013 on Office365?
Does anyone have any Microsoft link or article where they say this is possible or not possible? Or any of you guys know for experience this is possible?
Thansk
Emilio
No it's not possible to use Delegate Control as you can only install Sandboxed solutions in SharePoint 365 and Delegate Controls are not permitted in Sandboxed solutions.
Similar question asked Office365 community
http://community.office365.com/en-us/f/154/t/55979.aspx
Richard diZerega has written a blog about what is possible and not possible on SharePoint 365
http://blogs.msdn.com/b/richard_dizeregas_blog/archive/2013/07/16/app-approaches-to-common-sharepoint-customizations.aspx
Delegate Control
Apps for SharePoint do not support "Control" elements that can be used
with delegate controls in a master page. Delegate controls are a
common mechanism for swapping out functionality of a site using a farm
solutions (particularly useful with the AdditionalPageHead delegate).
As an alternative, the same result can be achieved through the design
in a custom master page (ex: place specific html or server controls in
the master page).
Related
I'm new to SharePoint development and design. Someone recommended using SharePoint Designer as a quicker way to have the site have a specific look that is different from the SharePoint Look Book. We want sections of our page to have borders with rounded edges, and specific color headers. I found several contradicting articles about using SharePoint Designer. Do you recommend using it on the latest version of SharePoint online in 2022? Have you had any success, or have you encountered any issues?
I enable scripting on my site. I tried connecting SharePoint Designer 2013 to my SharePoint online site successfully, but would like to know if it's a good idea to move forward with it.
As you can read from here SP Designer is supported on the latest On-Premises version of SharePoint(2019) on the bare minimum. But as you can see it is a product that is steadily heading to it's end-of-support/deprecation lifecycle.
Also, as you can understand, since it's development was halted since the 2013 version, a lot have changed since then, and many of the new features are not even supported by SP Designer.
If your are trying to make modifications to a SharePoint Online site, I would suggest using more modern tools(PowerApps, Power Automate, Modern UI, SPFx etc) and leaving SP Designer to it's way to deprecation.
You can also, update your question in terms of what you are trying to achieve and we could propose you some ideas :)
We are migrating old SharePoint 2010 On Premise code to SharePoint Online.
Part of the SharePoint 2010 on premise code has custom list forms developed with visual Studio.
Thought of using JSLink for custom forms while migrating the code to SharePoint Online but it seems that JSLink is only supported in classic experience and not in modern new experience.
Is there any way we can develop custom list forms on SharePoint Online with modern new experience? Is it possible with SharePoint Framework?
Note:
Tried by adding forms to list instances on SharePoint Hosted Add In but it targets the AppWeb lists and not the lists on HostWeb.
Well you can use react in modern web part to build any custom form. We can reuse components.
Another option is to use Power Apps similar to info path to design and add validation on list form.
https://abdulazizfarooqi.wordpress.com/
Another option is to use Content Editor webpart and add bootstrap html forms.
I hope it may help u.
Coding in Classic View is the only solution to your query. Once you are done coding in classic, you can switch/migrate to Modern View Experience.
In this way, your form will be visible and lists will also be consumed.
Nope!.. Modern sites are totally different development model So JSLink is not possible but you can use SharePoint framework extension to achieve the customization for the list.
Please follow the link below
JSLink to SPFX extensions
Please mark if accepted as answer
Our Company has just moved to Office 365 and I am working on moving our Sharepoint site to the Cloud.
My question is: if I have multilevel libraries, Can I create an expandable menu on Quick Launch that would provide access to all levels of the Library hierarchy?
This is not the exact answer but it might get you started
http://www.sharepointdiary.com/2013/02/top-navigation-drop-down-menu-quick-launch-flyout.html
I just use completely custom styles for my SharePoint Online sites, the SharePoint master pages are no good to me and the 2013 instance definitely allows more flexibility, hopefully you are running that now.
I have a task that I need to perform for a friend as a favor, to modify some forms on a MOSS/Sharepoint site to add some javascript to each form for some SEO tracking purposes.
I've had a little bit of exposure to Sharepoint, but it is mostly by using the Sharepoint Designer 2007 tool.
I am able to navigate to the site, and I can see the content in Sharepoint Designer. However, I am not able to see the forms, and I'm a bit stuck.
Here is an example of a form that I need to modify:
http://www.MY_SITE_GOES_HERE.com/forms/covg_order.aspx
I've read a little online, but I'm stuck. I don't know if these are infopath forms or what. I just need to modify the forms.
Is there a simple answer to this problem? Or a good resource to get up to speed quickly for this task?
I'm not a sharepoint expert, so thank you in advance for answering a simple question.
While hardly the simplest approach, but since this is a developer site, I would recommend creating a DelegateControl to add to your site. Using DelegateControls has several benefits, for example:
the ability to selectively activate and deactivate the controls through features
no need to modify any out-of-the-box files which would break supportability
ability to output different content on a page-by-page basis
You can opt to use one of the DelegateControls of the default master pages if you need to deploy to an existing site based on one of the default site definitions. The AdditionalPageHead is a favorite among developers, as it allows multiple overrides to be active at the same time.
If you want to create your own master pages you can add DelegateControls as you like.
If you want to learn more about DelegateControls you can check out the first issue of Understanding SharePoint Journal (Disclaimer: I wrote that issue). Also, check out the MSDN article on How to customize a Delegate Control.
.b
you can also check PowerForms which is a silverlight webpart that fully customizes sharepoint forms. You can add business logic in forms using custom assemblies and a lot other advanced tasks. Give it a try, i think it will solve a lot of problems.
http://www.bpc.gr/powerforms
You have a couple of options here:
If you need to add a unique code, like Google analytics you should probably deploy your code to the master page.
In case you need to customize forms for lists you will have to do it with SharePoint designer. In that case you will find EditItem.aspx and NewItem.aspx with SharePoint Designer pages or any other custom page. Open SPD, locate your list, expand it, look for Forms subfolder and you will find all the forms there.
Microsoft Office SharePoint Designer is now free, as of 1-Apr-2009. It's a good tool, not only for modifying individual pages, but for entire sites.
For those using SharePoint or MOSS 2007 specifically. How do you handle forms? Like say you want a form that submits contact information. I don't have this in production yet but I'm currently creating a list for the form that I need and then modifying the list add item form as needed. I'm not sure how this will translate to a public anonymous user environment. Any suggestions?
Thanks,
Curtis Shirley
Forms can be anything from custom lists (lists with your own fields added), custom ASPX pages (ASP.NET development), to InfoPath Forms Services (MOSS Enterprise only).
With lists you can also create your own new and edit forms if you don't like the out-of-the-box look/feel (SharePoint Designer can help you with this).
If you want to prevent spam with anonymous users, I recommend a CAPTCHA approach. Here are 3 to look at (we have implemented the first one recently):
http://nanddeepnachan.blogspot.com/2008/06/captcha-for-sharepoint-blog.html
http://blogs.msdn.com/pranab/archive/2008/12/09/sharepoint-2007-moos-wss-custom-captcha-antispam-field.aspx
http://captcha.biz/doc/asp.net/2.0/asp.net-captcha-sharepoint.html
The issue is really tricky. For a public facing site that must handle spam and usability, it may be best to code a custom form. It is not a major to host a custom form in SharePoint and there is information on getting code behind to work nicely.
Now that I think about it, the Community Kit for SharePoint has had to solve some of the issues for comments on blog posts.