I am making a fully customized Sharepoint, and I want to hide the breadcrumb. I tried placing visibility="false" within the Content Placeholder for the breadcrumb, but it only disables the Title and leaves the breadcrumb intact.
There were some fixes for this in 2010, etc. This required adding some CSS to the div containing the breadcrumb, but the breadcrumb is now contained in a Content Place Holder so it changes up the way to do things.
Does anyone have insight into this?
Thank you in advance!
SharePoint 2013 has its breadcrumb hidden by default, so I'm a little confused as to why it's visible in your solution (did you migrate from 2010?).
Anyway, settting .ms-breadcrumb-dropdownBox to { display:none; } with css (which is the out-of-the-box seattle.master way of hiding the breadcrumb) should do the trick.
I ran into the same issue. We did update 2007->2010->2013, and many sites maintained the breadcrumbs. However the CSS entry Kimzter noted didn't work. The one that worked for us was:
.ms-pagebreadcrumb { display:none; }
This is actually one of the few places I use the Script Editor webpart, as we have a lot of sites that want to maintain the breadcrumbs, so changing the master page or master CSS wouldn't work for us.
Related
This relates to an Xpages project using openNtf's Extension Library for Domino 9.0.1 V 16 (2016-01-28). There is a custom theme applied that extends extLib's Bootstrap3 theme.
Now I also applied Mark Leusink's debugToolbar Plugin (V 4.0.1, 2014-03-10).
Unfortunately all tables that are display inside the toolbar are partially "destroyed", as in this example:
Debugging the resulting html I see that the "label" cells of the debug table are assigned class="label" or class="label wide". Unfortunately bootstrap.css applies a display: inline style to a .label selector.
Currently I solved this by applying my own custom css file to reset toolbar styling; but I wonder whether there might be a more elegant way, maybe some kind of property that I simply missed out here. Or is this something that have to be done within the toolbar's source code?
Please add this as a defect on the project, so the contributor is aware and can resolve.
Alternatively, download the source code from https://github.com/OpenNTF/DebugToolbar, contribute the fix and make a pull request.
Hopefully Paul's and my entries at github and within the openntf.org project will help resolving this issue. Meanwhile my workaround seems to be the only option here;
As I mentioned above I created a custom styleSheet with just one line in it:
div.dBar table.grid td.label{display:table-cell;}
Then I created a cusom control as a container for the debug toolbar so that I could link my custom style sheet as a resource. The debug custom control finally is added to all the xpages where I want to have the toolbar.
Maybe this can help others, too.
I know you can use layout filters for normal pages with urls, but upon errors the view changes while keeping the url the same, so I can't utilize a new layout based on the path. Any help would be appreciated. Thank you!
Off the top of my head:
If you look in Core > Shapes > Views, you will see two files - one called ErrorPage.cshtml and one called NotFound.cshtml. Simply copy these files and paste them into your theme's view folder.
I have not tested this method with these particular pages, but I did do something similar with the LogOn widget.
Something to bear in mind is that the contents of these files will be rendered in the Content zone of your current theme.
How can I style the background of a content query webpart in SharePoint 2010?
I have been having a look around, and can't seem to figure it out. I am able to edit the individual item styles using the ItemStyle.xsl file in SharePoint designer, but I need a background image on the container.
I have referenced the class that is generated by SharePoint - 'WebPartWPQ4' - in CSS, and made it work that way, but that changes the styles for all web parts in the system. (This also feels like a bit of a hack)
Any help would be greatly appreciated.
It is totally okay that you try to override custom styles in your css (although 'WebPartWPQ4' is not the best choice). However, to get what you need, just ensure that the web part you want to style has some wrapper around it and change selector in your css to .wrapper > .WebPartWPQ4 so that only this instance of the web part gets styled.
The way I have solved this is to wrap the webpart zone in a div in the .aspx page file.
You can then reference this div in a css file.
The Situation:
I have customized the Bug Database template for SharePoint 2007 using SharePoint Designer. Specifically, I have edited the additional .aspx pages included with the template that are located inside the Bugs list. These are just simple edit forms and my customizations are very minor.
I have verified that the Supporting Files are correctly selected (New, Edit, Display). These forms have all been edited as well. I have the following .aspx pages (Non Views) in the Bugs List:
Activate.aspx
Close.aspx
DispForm.aspx - Supporting Display Form
EditForm.aspx - Supporting Edit Form
NewForm.aspx
ResolveForm.aspx
NewIssue.aspx - Supporting New Form
Resolve.aspx
The Problem:
On any of the views, the view dropdown contains 3 non views that correspond to the Activate, Close, and Resolve forms in addition to the actual view choices. Choosing these "views" just opens these forms.
Obviously, SharePoint is picking up any .aspx pages in the List that aren't supporting files and assuming they are views. Strangely, this was NOT the case for these files before I modified them using SharePoint Designer. Additionally, The NewForm.aspx page was NOT modified (I just created a new form that is now a supporting file), and even though it is not marked as a supporting file, it does not incorrectly show up in my views list.
The Conclusion:
There must be some setting to mark these files as non views without them being supporting files. I have looked through the NewForm.aspx and compared it to my modified forms and can find no obvious difference that should have any bearing on this.
Perhaps you have had this problem before or are aware of how to fix this issue? If so, here are some easy points! Thanks in Advance!
If they have been setup as a view (which it sounds like they have been), try making the <View> hidden to remove it from the view list
http://msdn.microsoft.com/en-us/library/ms438338.aspx
<View BaseViewID="1"
Type="HTML"
WebPartZoneID="Main"
DisplayName="Activate"
RowLimit="100"
ImageUrl="/_layouts/images/generic.png"
Hidden="TRUE"
Url="Activate.aspx">
I dont think you can make them <Form> elements, as it only accepts DisplayForm, EditForm, or NewForm
http://msdn.microsoft.com/en-us/library/ms478121%28v=office.12%29.aspx
Currently I'm having trouble adding custom/my own css files to my SharePoint site. I add the custom/my own css files via the c# files (CssLink) as a web part and have them applied to my site's javascript files. Trouble is, whenever the css files were applied, my site goes back to the default blue-ish SharePoint theme color.
Is there any quick and simple way to avoid that from happening?
Thanks.
You can use this method to register a css file from a WebPart
Microsoft.SharePoint.WebControls.CssRegistration.Register("/.../mystyles.css")
or you can add the css file to the content place holder with the id "PlaceHolderAdditionalPageHead" which is present in the master page like this
var placeholder= Page.FindControl("PlaceHolderAdditionalPageHead");
var cssLink = new Literal();
cssLink.Text = "text";
placeholder.Controls.Add(cssLink);
Why don't you use, Site Settings, Master page and use the option "Specify a CSS file to be used by this publishing site and all sites that inherit from it." to specify your own CSS.
(Also, I have no idea what you mean with "via the c# files (CssLink) as a web part and have them applied to my site's javascript files". Are you missing some words in that sentence?)
You should have a very good reason to be adding CSSLink via C#. Have you considered packaging your CSS as your own theme?
SharePoint themes are easy to create and have many benefits such as:
a) Supported by Microsoft
b) Easy to create
c) Manageable by the end users.
d) You can apply different themes to different parts of the site.
e) etc etc...
The process of creating the theme can be found here:
http://sharepoint.microsoft.com/blogs/GetThePoint/Lists/Posts/Post.aspx?ID=122
I would recommend adding your theme via a feature only for adding and removing the theme. This would add a great deal of options for future tweaking.
Here is an example:
http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/
I'm going to blog about this later this week so keep an eye out of you like. http://blog.zebsadiq.com
Upload your css in the syle library folder(or any library in side your site)
go to -->site actions-->site settings-->modify all site settings-->under look and feel tab-->click master page-->there is one option called alternate css url-->browse your custom css and click Ok.