Sunday, August 23, 2020

HTTPS to HTTP (Wordpress installation)

How to convert back from HTTPS to HTTP ?  (Wordpress installation)

You purchased a domain for yourself. Then somebody told you that SSL certificate is must. You purchased it for a period of one year. You installed it. All your pages started with HTTPS. You feel secure. 



"Anything (including people, software, computers, and devices) who exchange sensitive information on any network, including the Internet and Web, needs to use SSL/TLS. Sensitive information includes things like username and passwords, credit card numbers, or any other data that needs to be kept private."


But after the end of the year the SSL certificate expired and considering your limited use of the site you think that SSL is not necessary - It will be an unnecessary expense. So you don't buy a new certificate. The site shows notices that "It is not secure." Pages are blocked. Site stops functioning properly. 

You check with your web hosting company and they ask you to purchase a new SSL. You don't want to purchase it. 

Your site is not functioning because links to all your pages in the database were converted to HTTPS. Now you have to reverse that.

In that case simply implement the following steps:-  (From WordPress forum post)

  1. Access the database connected to your Wordpress site.
  2. Create a backup.
  3. Download the backup.  Normally it is an SQL file.
  4. Open the SQL file in some really sophisticated text editor like Sublime Text.
  5. Search for https://yoursitename.com.
  6. Replace it with http://yoursitename.com
  7. Save and upload it to the folder where you keep your database backups.
  8. Restore database with the uploaded file.
Your site will start functioning smoothly.

Friday, October 10, 2014

About placing cookie script in php file





The top part of the script, that retrieves and sets the cookie, needs to be placed at the very top of a page to work. The rest of this script can run anywhere on your site that you want to welcome a user.

Link - Creating Cookie

Wednesday, September 26, 2012

WebM Files

WebM

From Wikipedia, the free encyclopedia

WebM
WebM logo.svg
Filename extension .webm
Internet media type video/webm,
audio/webm
Developed by Initial developments by On2, Xiph, and Matroska, later developments by Google
Initial release 19 May 2010; 2 years ago[1]
Type of format Media container
Container for VP8 (video)
Vorbis (audio)
Extended from Matroska
Open format? Yes[2]
Website www.webmproject.org
WebM is an audio-video format designed to provide royalty-free, open video compression for use with HTML5 video. The project's development is sponsored by Google Inc.
A WebM file consists of VP8 video and Vorbis audio streams, in a container based on a profile of Matroska.[2][3][4] The project releases WebM related software under a BSD license and all users are granted a worldwide, non-exclusive, no-charge, royalty-free patent license. Despite this, some in the industry have called upon Google to provide indemnification against patent suits.

Wednesday, September 19, 2012

Sunday, September 16, 2012

Saturday, September 15, 2012

NoFollow links

"Nofollow" provides a way for webmasters to tell search engines "Don't follow links on this page" or "Don't follow this specific link."
Originally, the nofollow attribute appeared in the page-level meta tag, and instructed search engines not to follow (i.e., crawl) any outgoing links on the page. For example:
 <meta name="robots" content="nofollow" />
Before nofollow was used on individual links, preventing robots from following individual links on a page required a great deal of effort (for example, redirecting the link to a URL blocked in robots.txt). That's why the nofollow attribute value of the rel attribute was created. This gives webmasters more granular control: instead of telling search engines and bots not to follow any links on the page, it lets you easily instruct robots not to crawl a specific link. For example:
 <a href="signin.php" rel="nofollow">sign in</a>

How does Google handle nofollowed links?

In general, we don't follow them. This means that Google does not transfer PageRank or anchor text across these links. Essentially, using nofollow causes us to drop the target links from our overall graph of the web. However, the target pages may still appear in our index if other sites link to them without using nofollow, or if the URLs are submitted to Google in a Sitemap. Also, it's important to note that other search engines may handle nofollow in slightly different ways.

What are Google's policies and some specific examples of nofollow usage?

Here are some cases in which you might want to consider using nofollow:
  • Untrusted content: If you can't or don't want to vouch for the content of pages you link to from your site — for example, untrusted user comments or guestbook entries — you should nofollow those links. This can discourage spammers from targeting your site, and will help keep your site from inadvertently passing PageRank to bad neighborhoods on the web. In particular, comment spammers may decide not to target a specific content management system or blog service if they can see that untrusted links in that service are nofollowed. If you want to recognize and reward trustworthy contributors, you could decide to automatically or manually remove the nofollow attribute on links posted by members or users who have consistently made high-quality contributions over time.
  • Paid links: A site's ranking in Google search results is partly based on analysis of those sites that link to it. In order to prevent paid links from influencing search results and negatively impacting users, we urge webmasters use nofollow on such links. Search engine guidelines require machine-readable disclosure of paid links in the same way that consumers online and offline appreciate disclosure of paid relationships (for example, a full-page newspaper ad may be headed by the word "Advertisement"). More information on Google's stance on paid links.
  • Crawl prioritization: Search engine robots can't sign in or register as a member on your forum, so there's no reason to invite Googlebot to follow "register here" or "sign in" links. Using nofollow on these links enables Googlebot to crawl other pages you'd prefer to see in Google's index. However, a solid information architecture — intuitive navigation, user- and search-engine-friendly URLs, and so on — is likely to be a far more productive use of resources than focusing on crawl prioritization via nofollowed links.

How does nofollow work with the Social Graph API (rel="nofollow me")?

If you host user profiles and allow users to link to other profiles on the web, we encourage you to mark those links with the rel="me" microformat so that they can be made available through the Social Graph API. For example:
<a href="http://blog.example.com" rel="me">My blog</a>
However, because these links are user-generated and may sometimes point to untrusted pages, we recommend that these links be marked with nofollow. For example:
<a href="http://blog.example.com" rel="me nofollow">My blog</a>
With rel="me nofollow", Google will continue to treat the rel="nofollow" as expected for search purposes, such as not transferring PageRank. However, for the Social Graph API, we will count the rel="me" link even when included with a nofollow.
If you are able to verify ownership of a link using an identity technology such as OpenID or OAuth, however, you may choose to remove the nofollow link.
To prevent crawling of a rel="me nofollow" URL, you can use robots.txt. Standard robots.txt exclusion rules are respected by both Googlebot and the Social Graph API.
updated 03/14/2012

Related