I have created my gravatar profile and added websites from websites tab.
Now I want to delete some of my websites but I can't.
Please see the attached screenshot.
when I click on delete button on left of the website, it removes from the list but when I again come to my website page, it remains the same.
Please help me remove unwanted websites from my profile.
The gravatar information (as most of the content on large web sites, also the content on Wordpress.org/.com) is cached.
It may take a while the information to be refreshed. However this is not Wordpress specific question, if you experience the issue after a while (usualy a couple of hours), consult the gravatar FAQ/support.
Related
I am trying to create a dashboard via SharePoint and I would like to create a section beneath a displayed document where users can type and submit a description of what is going on in the document above. I don't want the users to be able to edit the site page in order to add text to the page so I believe the best solution would be the creation of a web part where a user can create and submit their desired description. The only web parts that I've come across to do something like this are the Note Board web part and the Microfeed web part. The Microfeed part seems too much like a social media page. My problem is I would like to try the Note Board web part but whenever I insert it on the page it never displays an area to type in, just the title "Note Board".
So it seems that this problem came up because of the way my account is related to this particular SharePoint site that I am editing. My account doesn't have a profile attached to it essentially and the way that these notes are shared and stored directly relates to having one of these profiles. The Note Board Web Part turned out to be working perfectly fine my account is just not capable of posting within it. (I figured I'd answer incase anyone else comes up with this problem.)
Whenever I browse my blog which I created via Azure marketplace for Ghost with completely default settings, I get redirected to a login page.
If I log in then I get taken back. I can click my post and be taken to the content. If I then go back, then click the heading again, it takes me to the edit area.
The problem I have is that readers of the blog are being prompted to login. I don't want this. I just want my content to appear when they click a post.
Anybody else experienced this or know what I can do about it?
It would appear this is only the behavior on the default post that is created once you have activated the service.
Once you start making posts and unpublish the initial one, it behaves as expected. Hopefully this helps clear up any confusion for someone else.
Running WSS 3.0 and I've been given full access to sharepoint. I'm working on a lean initiative to clean up SP and delete old/outdated libraries from the site or at least from the main page. I've been able to get into quicklaunch where it gives me the option to remove it from quicklaunch but it's still showing on the front page. I've also found the button that lets me delete the document library but all it does is delete all the content. The link is still on the front page but when you click on it says something about the link being broken.
I'm on my own with this project and I'm not part of the IT team but I need to be able to delete document libraries and the content. Or at least edit the front page to remove these links.
I've found a lot on the internet about powershell and sharepoint designer but I don't have either of those and I'm not sure if I'd be tech savvy enough to use them. Please tell me there is some secret button I can hit to remove the useless libraries.
I am using Microsoft SharePoint Search (MOSS) to search all pages on a website.
My problem is that when you search for a word that appears in the header, footer, menu or tag cloud section of the website, that word will appear on every page, so the search server will bring you a list of results for that search term: every page on the website.
Ideally I want to tell the search server to ignore certain HTML sections in its search index.
This website seems to describe my problem, and a guy says "why not hide those sections of your website if the User Agent is the search server.
The problem with that approach is that most of the sections I hide contain links to other pages (menu's and tag clouds) and so the crawler will hit a dead end and won't crawl very far.
Anyone got any suggestions on how to solve this problem?
I'm not sure if i'm reading this correctly. You DON'T want Search to include parts of your site in the index, but you DO want it to go into that section and follow any links in it?
I think the best way is to indeed exclude those section based on user agent (i.e. add them to a usercontrol and if the user agent is MS Search you don't render the section).
Seeing as these sections would be the same on every page, it's okay to exclude them when the search crawler comes by.
Just create ONE page (i.e. a sitemap :-D). that does include all the links a normal user would see in the footer / header / etc. The crawler could then use that page to follow links deeper into your site. This would be a performance boost as well, seeing as the crawler only encounters the links once instead of on every page.
occasionally when hitting the landing page after signing in, the users personal space is displayed instead of the default guest page. This is does not happen often, but my boss does not want it happening. I am hard pressed for an explanation.
This is not really programming related - the liferay forums would help a lot better with that problem.
Other than that liferay tends to remember your last visited page - which bit me more than once when one part of the site was included in an iframe portlet - the iframe content was the remembered "last" visited page, not the one containing the iframe. After Login, that was the target.
As far as I know the personal pages are shown after login if the desired landing page (or the last visited page) was not found.
You can disable the redirect to the last visited page after login by setting auth.forward.by.last.path=false in portal-ext.properties