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.
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 :)
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).
Could someone point out the differences between Sharepoint Designer and the new Design Manager within Sharepoint 2013 ? I searched on the web but haven't found a concrete answer.
Thanks !
1) SPD can still be used to edit SharePoint pages, but the visual Design view and Split view were removed so you need to do all your editing in a code view. You can also still use it for the other things you mentioned.
2) Design Manager is free and included with SharePoint Server. It only works on Publishing sites so its not included with Foundation.
3) Its part of the base installation of the product. You don't need to do anything to procure it.
4) Not really. Design manager provides functionality for Importing/Exporting HTML and CSS that can be edited in any Web Design platform. For example Dream Weaver. Since SPD no longer has a WYSIWYG editor there is not real connection between the two.
5) Most of the customization you've already done will be brought across when you do a content database upgrade. I'm sure there will be some things that need to be upgraded after you do the database attach.
totally sharepoint newbie here, was asked to create a sharepoint collection which mimic the exisiting look and feel for another website, how can i archieve this? thanks
With a SharePoint foundation it is quite difficult to do cause you are limited in options. The server version is customizable from A to Z: master pages, page layouts etc...
When you work with SP foundation the only option is to work with themes which are built in SharePoint and which can be customize. You can create your own theme. See here to for more information about how to customize SP site.
I can advise you to see these examples...
Hope it helps,
Andrew
I'm a developer with 5 years of MCMS development and without a single know how with SharePoint.
I want to use the CMS capabilities of Sharepoint to migrate my applications but I DONT KNOW HOW TO START!!!!!!
In my actual projects i have a Visual Studio solution with all my code, my templates and my usercontrols...
I cannot see how can i do the same thing with Sharepoint :(
I want to customise my site like i did before, i want to create pages based on templates like i did before.
Anyone knows where i can find a walkthrough that explains me that?
Thank U All.
Unfortunately I think you are going to have to learn SharePoint. Even the WCM features are a big topic, and probably the best book is Andrew Connell's "SharePoint 2007 Web Content Management Development" - I don't think a 2010 version is available yet. The good news is that I think the MCMS product had a big influence on how the SharePoint WCM features were architected, so the underlying principles will be similar.
SharePoint 2010 has a Visual Web Part that will encapsulate a user control which might make the transition easier. Also see my answer to this question about converting an ASP.NET site to SharePoint which might have some relevant information.
Most of the information about converting from MCMS to SharePoint is for the 2007 version of the product. This two-part article on MSDN seems to be the best starting point.
I cannot see how can i do the same thing with Sharepoint :( I want to customise my site like i did before, i want to create pages based on templates like i did before.
Problem is, SharePoint is not MCMS, no matter how Microsoft tries to brand it as its successor.
Creating sites in SharePoint is almost opposite of how things we were done in MCMS were you build from the ground up using ASPX templates, user controls and placeholders. In SharePoint, you'll have to strip out most of the OOB stuff you don't need. The recommended approach to custom development is through web parts, CAML, and the SharePoint APIs.