I was working on my sharePoint 2007(MOSS) Portal. I accessed a site and did my reguler task. After some time when I check the webparts from the site page are missing. The Whole page is empty.. While I can see the navigation links only on site tab.. Please let me know Y this issue has occurred And I need to find a solution.
Is the page published? Are you using the same user account for edit/display? Try adding ?contents=1 at the end of the URL and see if the parts are ACTUALLY on the page.
Also check the logs - ULS Log specifically.
David Sterling
davidmsterling.blogspot.com
www.sterling-consulting.com
Related
I'm trying to get my subsites to inherit the look I configured (under site settings > look and feel > change the look) on the rootsite. How do I do this? Thanks in advance!
I'm using Office365 (Sharepoint online).
Generally, according to the article below, the subsites will inherit the theme from the parent site. Here is the article link:
look and feel inheritance
By the way, may I know whether your subsite is from another template? If so, please follow the instruction below:
1) Since the link of Master page setting is hidden, you can change the URL to the setting page by two steps.
Copy your site URL and remove the target of URL after the default URL. See the example below:
Root URL : https://XXX.sharepoint.com/SitePages/Home.aspx
Change to : https://XXX.sharepoint.com/
Add the ‘_layouts/15/ChangeSiteMasterPage.aspx’ behind the URL from step a. See the example below:
Root URL: https://XXX.sharepoint.com/
Change to : https://XXX.sharepoint.com/_layouts/15/ChangeSiteMasterPage.aspx
Note: if you get the error message, please go to check the publishing featureon Team Site.
Per my test, you need to enable SharePoint Server Publishing feature if the subsite is not a publishing site.
Then when changing the look of rootsite, the look of subsite will get changed too.
I'm having quite a hard time figuring out this problem and I need your help. Here's the scenario:
I have a sharepoint 2010 web application on my port 80. This has 2 site collections, the root, and the /sites/official. My problem is: The root site is empty, but in the future it will be my something (I don't know what yet), but my other site collection is ready to go and I already have an Internet address for it.
What I want to do is configure everything in way that I can type http://contoso.com and get as response my sub-site (yes, its a kind of redirect)...
how can I do it? What and where should I configure it?
add content editor webpart on your root site collection and put this javascript in that webpart
<script type="text/javascript">
window.location = "http://contoso.com/sites/official"
</script>
Open IIS manager
Right click on your SharePoint website -> Properties
Go to tab Home Directory
Choose A redirection to a URL
fill the URL for redirection. for example: http://contoso.com/sites/official
Notes:
Make sure to check A Directory below URL entered to avoid redirect loop
Link to another thread might interest the reader - immediate redirect page in sharepoint
Screenshot:
Add alternate access mapping for the sub-site collection from the central administration.
Central Administration > Application Management > Web Applications > Configure alternate access mappings
I want to put a secret page in my website (www.mywebsite.com). The page URL is "www.mywebsite.com/mysecretpage".
If there is no clickable link to this secret page in the home page (www.mywebsite.com), can search engines still find it?
If you want to hide from a web crawler: http://www.robotstxt.org/robotstxt.html
A web crawler collects links, and looks them up. So if your not linking to the site, and no one else is, the site won't be found on any search engine.
But you can't be sure, that someone looking for your page won't find it. If you want secret data, you should use a script of some kind, to grant access to those, who shall get access.
Here is a more useful link : http://www.seomoz.org/blog/12-ways-to-keep-your-content-hidden-from-the-search-engines
No. A web spider crawls based on links from previous pages. If no page is linking it, search engine wouldn't be able to find it.
I am define my contact list, and the made it serachable trough SSP-> serach settings. Now, I add the people search Webpart which is out of box web part. ok? but when I go to search any keyword it redirect me on peopleresults.aspx page. with message
"404 NOT FOUND" Or some times before it was showing me "page cannot find" error. So what is the reason? How to configure "peopleresults.aspx" with People Search box? please guide me its too urgent.
you need to create my site and under configuration of userprofile -> setup my site enter my site host location
Please refer following location
http://social.technet.microsoft.com/Forums/sharepoint/en-US/bf19ece2-6846-47d1-91fe-69162417d788/people-search-not-working-peopleresultsaspx-page-does-not-exist-and-people-search-webparts-missing?forum=sharepointadminprevious
Did any of guys run into this error where the search crawler is ignoring an aspx page? I am getting the following warning message for these page: "Content for this URL is excluded by the server because a no-index attribute".
Any help will be appreciated.
Thanks.
Check the search visibility of the site using the following settings page.
http://[mywebsiteurl]/_layouts/srchvis.aspx
A value of "Never index any aspx pages on this site" will result in the log message.
Note: individual lists can also be "turned off" with regards to the search crawl.
http://[mywebsiteurl]/_layouts/advsetng.aspx?List=[list GUID] (or more simply go List Settings -> Advanced Settings
Thanks for your response Nat. I figured out the issue.
We have two version of the site in question, win auth and forms auth. After some digging around a little bit I found out that one of the user controls was breaking in the win auth version - hence the page as well. It was working fine in forms auth. I forgot to add an appsettings entry in the win auth's web.config. So I am guessing when the crawler went to the page, saw the page was broken - it didnt crawl it and recorded the warning message in the crawl log.
After fixing the user control, the page was crawled as expected.