I followed this post:http://blog.mattsampson.net/index.php/2010/12/13/quick-launch-on-new-web-part-pages?blog=1 which edits some 14 hive templates to remove all the code that hides the Quick Launch. I used notepad++ to search all the files when I'd finished and I've definitely deleted the code.
But when I create a new Decision Meeting Workspace I still get no Quick Launch on the page. Oddly enough I do get a quick launch showing on the page when I go into the Site Settings Page showing:
Site Content
Agenda
Attendees
Decisions
Document Library
Objectives
Tasks
Please check the content place holder for the same is not set as hidden in master page
Related
I have just edited my publishing site home page in SharePoint Designer. The page originally contains some web parts.
I am a newbie as far as SharePoint branding is concerned. I did the editing in Advance Mode when I realized that I couldn't edit areas outside my Web Part Zones and since I need to do that, I tried it using the advance mode. I edited the page adding some inline CSS styling and even added some additional Web Part Zones. Everything looked good when I previewed so I saved and thought all was okay. But to my surprise, Only my account (System Account) can see the changes I made. Every other user on the domain are still see the original page without any of my recent changes.
I have done the Check-In and Publish circle over and over again but no luck.
Does any one have any idea as to what I might have done wrong here and what I can do to fix the issue.
Follow below steps for publishing:
Select “Publish a major version,”. When
prompted to approve the master page, click Yes. This automatically
invokes a SharePoint master page approval page, where you
will find your new master page listed at the top of the page.
Click the drop-down menu beside the master page. Select
Approve and select the Approved radio button. Click OK. Your
master page is now saved and approved in SharePoint.
Navigate to your top-level site collection, and click Site Actions -> Site Settings
Under Look and Feel, select the Master Pages link. For both the
Site and System Master Page settings, select your new master
page from the drop-down menu.
Once you click OK, your changes should be available to all users
Right now I have an HTML file and I'm trying to convert it to a master page. I'm using a VM on CloudShare.
So I create a new site collection and go into the site settings. Under “Look and Feel”, Design Manager isn’t there so I’ve found that if I go to “Site Collection Features” under “Site Collection Administration”, and activate “SharePoint Server Publishing Infrastructure” Design Manager will show up. So I go into design manager, but under Edit Master Pages none of the file or folder names will show up, and when I convert the html file the status column doesn’t show up either, so I can’t go to preview it or to the snippets gallery.
The only thing I can find online is to create a new site collection, which I’ve tried a few times. This happened on my old CloudShare VM, and creating a new site collection fixed it, but it’s not working for this. Can anyone help?
Personally when working with new master pages I have found that the best application to use is SharePoint Designer. You should be able to download it for free. Here are the instructions to configure SharePoint designer using it with CloudShare.
http://blog.cloudshare.com/tag/sharepoint-designer/
Figured it out - I made a new site collection and set it to a Publishing site template and it fixed the issue.
Trying this again.
First of all, I apologize for my ignorance-I have never used Netsuite before. I recently started at a company that has been using Netsuite. Their site is already set up and in my job I have to edit the site on a daily basis. The hardest thing I have discovered so far is the lack of instructional information online for Netsuite and the organization. I am trying to change out or delete an rollover image on the side navigation bar. I can find all of the images for the initial navigation and their corresponding rollover image, but cannot find any of the subcategory images that come off these. I cannot find where these are set up either in Netsuite.
If I delete the image, will it disappear from the navigation bar or cause an error?
I've tried looking through the source code of the home page, but no luck there. Any suggestions on how to figure this out on a site already set up?
I have content editor on my team site where I added several links. But today while adding some new links, content editor crashed. so now when I tried to open site containing content editor, browser stop working.
The quick solution is:
I can delete the existing content editor and create a new one (using ?contents=1 in the corrupted team site). But since my content editor contains lot of links, so is there a way where I can roll back content editor to previous version (till yesterday afternoon)?
Any suggestion is appreciated.
Your previous version is probably lost in the mess. You will have to go to the site admin, and close / delete the webpart and start over. You may be able to simply close the web part (from site admin) and then edit the web part properties to salvage it's contents.
Either way, content should not be added directly into a Content Editor Web Part (for this reason.) Instead, use the option to point to a file in a Document Library elsewhere in your SharePoint site, with versioning enabled.
Then, in the case of the CEWP blowing up the page from an edit to the contents, you can revert to the previous version of the document, and the CEWP will immediately be updated, and the page immediately restored.
Stackoverflow is about programming related questions, your question is more of a user question.
You can't roll back a content editor. If you have versioning enabled for the page you have the content editor on, you might be lucky and can retrieve an earlier version. Otherwise you could only check the database for the content editor contents, but that will be a pretty tedious task finding it.
As part of a SharePoint solution, the functionality for users to create new web sites and publishing pages (programmatically) via a button click has been added. I need to ensure that the Description field for the newly created sites and pages is indexed by SharePoint Search. What is the best way to do this?
Please note, I am NOT interested in starting a new crawl. I just want to ensure that whenever the next scheduled crawl occurs, the contents of these fields will be searchable.
Thanks, MagicAndi
I'm guessing you mean how can you ensure the site is indexed immediately?
Generally, crawls are scheduled which means your new site will only be added to the search index after the next crawl is done. So if your incremental crawl happens every hour you may have to wait up to an hour for it to appear in the search index.
However, given that your new sites are being added programatically you could also programatically start an incremental crawl if it is vital for it to start appearing in search results immediately. There are details how to do this in this article.
Update:
The site title and description should be indexed automatically by the next crawl. If this isn't happening, then you don't have a Content Source that covers that site so you need to create/update one to cover the new sites and make sure it has a crawl schedule. If the new sites are created in separate site collections consider putting them on a Managed Path.
In our SharePoint system we have a terrabyte of data with 100,000 site collections and probably 20 new site collections added every day. We only have one content source that points to the root of the site and everything gets indexed automatically.
It sounds like you're missing a content source or a crawl schedule.
It turns out that the site description is included in the crawl by default. I tested the search default properties by creating a new site and assigning a unique text string to the description. After the next incremental crawl, I was able to search and find the unique string via the default SharePoint search.
I have not yet tested if the page description is included in the search scope by default, but I'm prepared to guess that it is. I will update my answer as soon as I get a chance to test this.