Add Facebook comment box to your WordPress blog

In this article I will teach you how to Add Facebook comment box to your WordPress blog, we need to use a Facebook comment plugin developed by Mr. Alex Moss. This plugin makes it simple to add Facebook comments system to your WordPress powered site without hassle. Here you can insert the comment box as a shortcode in any post, page and template and use your own settings. You can see the demo at Facebook Comment Box, just open one post article to view the comment box.

How To Add Facebook Comment Box In WordPress Blog

Add Facebook Comment Box To WordPress:

  • Get the plugin at this link.
  • Login to your wordpress account.
  • Go to plugins >> add new >> upload and upload the plugin that you’ve downloaded before.
  • Then activate the plugin.
  • Once the plugin installed, go to this link to create Facebook app.
  • Click the create new app button and after that you will see something like:

How To Add Facebook Comment Box In WordPress Blog

App Name: [?]
App Namespace: [?]

  • Then hit the continue button and solve the captcha.
  • Copy the app ID into your clipboard.

How To Add Facebook Comment Box In WordPress Blog

  • Then find the app domains and add your site URL (without http://).

How To Add Facebook Comment Box In WordPress Blog

App Domains: [?]

  • After that find website with Facebook login and add your site URL (with http://).

How To Add Facebook Comment Box In WordPress Blog

Site URL: [?]

  • Then save the changes.
  • Go back to your Facebook comment plugin settings.
  • Scroll down and you’ll find the main settings.
  • Paste your Facebook app ID into the box.

Facebook App ID:

  • Then save, you will see other settings in this plugin, explore and learn the function .
  • You can see the Facebook comment box below your wordpress post and you can place it everywhere using shortcode, just learn the function other info are provided of this plugin, so don’t worry about that. Enjoy!

Hope you found this aticle useful! Subscribe us for more updates directly send to your inbox. Thanks!


Responsive web design


Responsive web design (RWD) is a web design approach aimed at crafting sites to provide an optimal viewing experience—easy reading and navigation with a minimum of resizing, panning, and scrolling—across a wide range of devices (from desktop computer monitors to mobile phones). We explian, If you are in the business of building and designing websites, you cannot ignore the fact that many people are going to be visiting your sites on their smartphones and tablets.

The Web and the mobile browsers remain one of the top ways that users interact with websites and if they have trouble on their smartphone, there is a good chance they are not coming back.In light of this, responsive web design could be the best solution. It offers more than just a simple mobile template; instead, your entire site layout is designed to be flexible enough to fit into any possible screen resolution.

But there are some facts you should keep in mind.

Load Time and Performance

Responsive websites are nearly identical in download size regardless of device or screen resolutions. This means, viewing a responsive website on a smaller screen and displaying less visible content or smaller-sized images, doesn’t mean that the site will load faster.


Mobile devices and browsers will have to deal with a lot of content. Sites should be careful to avoid loading unneeded CSS, running specific scripts and download large images.

A good implementation is possible, but it also means more complexity than developing a fixed width desktop site.

Time and Money

Higher level of complexity means also higher development cost.

The days where a designer’s work is done with a simple mock-up in Photoshop is gone.

Designers, developers and clients have to work together even closer. Design changes by designers or clients can lead to a large amount of development time. A good workflow can help keep costs low.

How Responsive Design Works

When I use the word “responsive” in terms of web design I mean that the entire layout responds based on the user’s screen resolution. Imagine this scenario: you’re reading a website on one tablet, then you switch to another device for one reason or another. The browser window is now re-sized. A responsive web design layout will feature schemes and a layout that gracefully breaks down and reinvents itself. From a usability perspective this is a brilliant technique.

Why Design for Mobile?

It has become evident that more users are going mobile, and not just for on-the-go web browsing either. Tablet PCs have begun to change in context when users are online in the classroom. Designing for mobile is certainly a requirement in modern day web standards. The only problem is choosing your method of development, and targeting your audience appropriately.

When you start coding for specific screen resolutions you end up with too many stylesheets to deal with. Media queries in CSS3 can be used to build iPhone-specific layouts for both portrait and landscape view. Since you can predetermine the pixel density it’s easy to revamp any HTML template for mobile.

Dynamic Image Scaling

Images are another important facet of practically every website. Mobile users may not be looking to stream videos, but photos are a whole different story. These are also the biggest culprits when it comes to layouts breaking out of the box model.

The standard rule for CSS is to apply a max-width property to all images. Since they’ll always be set at 100% you will never notice distortions.



Windows Live Admin Center (changed from Windows Live Custom Domains in November 2007) is a service provided by Windows Live. It enables users with domain names to change their domain MX record (Mail Server) so that they can enjoy the full features of Windows Live Hotmail on their personalized domain.
Email accounts provided by Admin Center are Windows Live IDs and you can use them to sign into MSN Messenger and Windows Live Messenger and all other Windows Live ID enabled services.

One Windows Live ID can be set as the administrator and using that ID new accounts can be created, and old ones can be deleted or edited on that domain. The administrator may also choose to allow anyone to create his or her own account in the domain via a link on the domain’s web site. Administrators can choose from a web-based or Windows-based application to manage all aspects of their domain accounts.
Users with Admin Center accounts can check their emails using Windows Live Hotmail, Windows Live Mail, and Outlook.

This tutorial will show you step by step How to Configure your own domain with Windows Live Admin Center.

Step 4

You will see a page similar to this below. You will work with “MX Server” under Mail Setup category.

Step 5

– See more at:

Read more

Tips for PHP Developer

a) Go OOP

If you have not yet entered the realm of Object Oriented Programming, then you are at a disadvantage, and you are falling behind fast.

OOP is essentially a method of programming with the use of classes, or Objects, which tie like things together, remove the need for repetition of code and perform the basic tasks of production very simply. Objects are essentially classes that collect a bunch of functions together and wrap them in a wrapper that can be reused over and over again without the need to rewrite functionality or procedures every time you need to do something.

Procedural Programming works by following a routine from the top to the bottom of each page as the server reads every file on your server. With OOP, there could be one or two objects being instantiated, which, in turn could instantiate a few, a hundred or a thousand other objects which could all perform certain tasks depending on variables passed into the objects. OOP is faster, simpler, easier to debug, uses less server resources, less code, is faster loading and more logical to work with once you figure out the basic principles. Go OOP – It changed my development style forever.

b) Stay Away from Anything Ending With _once()

We all know that include() simply gives us a warning if it fails, while require() kills the script with a fatal error when it fails. What we don’t forget is that include_once() and require_once() is extremely hard on server resources. There is nothing we can do about it, it’s how PHP is set up. Just remember that these things kill your server resources, specially on a huge framework, and if you plan your code properly you won’t even need it anyway.

c) Develop With Error Reporting On

The very first thing you do when starting a new project is to turn error reporting to E_ALL, and you should only turn it off ten seconds before going to production mode. I do this with every project that I build and there is nothing better than running a project in full production mode and not even getting one error. Besides that, with error reporting on, you pick up any small errors that will eventually grow up to bite you in the… well, you get my point.

d) Use A Framework If You Need One

Ok, so Rasmus Lerdorf says you shouldn’t use a framework because he could quite conclusively prove that a framework is much slower than normal PHP code when it came to printing a simple “Hello World” application. Two things to mention here though: you are not Rasmus Lerdorf and I bet you won’t be building a “Hello World” application every time you program something. Frameworks that help you do the tedious things can help, although you will have to learn how the frameworks function first in order to make things simple, but that’s the only real trade-off. Plus you stand less chance of writing bad code when someone else has written most of it for you, but let’s pretend I didn’t say that.

e) Use PHP’s Inbuilt Functions

Ok, you want to count the amount of keys in an array? You can loop through the array and simply increment a value for each iteration, right? Or you can just use the built in PHP function count(), which does just what it should. PHP has many built-in functions that can do what you need them to, so check out the manual to make sure you are doing it in the best way possible.

f) Protect Your Database

The best and safest way is to use mysql_real_escape_string() for all database before it is added to the database. This function makes all strings safe in terms of quotes and other functions that can harm your database or contain malicious code, so use it to be sure you have taken the first step against protection of your data. Another thing you can do is validate all POST and GET strings, never use $_REQUEST, and make sure all form submitted data is of the right type and value before adding it to a database query.

g) Use POST Not GET

Ok, this isn’t always possible, but when its really not necessary, don’t use GET, use POST. The reason is simple – GET is simple to emulate, all I need to do is add something to my address bar and I can hack your project. Obviously GET is the easy way to do pagination and permalinks, but when using form submission especially, stay with POST, it’s safer.

h) Draw Before You Code

A good practice to get into is to wireframe your projects, even if you are just scribbling a few notes on a piece of paper. It is very important to actually give the mechanics of you application some thought before sitting down to start coding,

– See more at:


read more

A Detail Guide about SEO

SEO is just as important for you as creating quality content that inspires engagement and generates leads. After all, if you’re not getting traffic, you’re not getting engaged readers or leads, either.

Even if your writing is top-notch and your content’s amazing, if you don’t publish regularly, you don’t get search traffic. Search engines like Google want to give searchers the very best results for their queries. If you publish infrequently or sporadically, Google assumes your blog is not a good resource for searchers.

Don’t Forget Meta Data

Meta titles and descriptions are an opportunity for you to tell:

  • search engines what a blog post is about
  • your audience why they should click through and read it

Remember to use keywords (but don’t stuff them in) and natural, fluent language.

Vary Content Types & Lengths

Always publishing the same type and length of content gets boring fast for both readers and search engines. So don’t forget about the following blog writing tip: when you vary the types and lengths of your content, not only are readers are more engaged, but search engines love your site and send you loads of traffic. That’s because the mix of lengths and media creates a better user experience and is more likely to be useful to searchers.


Always include at least 1 image with every blog post, and use more if you can. Infographics, videos, and slides are excellent visual supplements to your regular written posts.


For your written posts, 400 to 500 words should be the minimum. That length gives search engines ample text to crawl and plenty of keywords and context clues to help them understand what the article is about. Cap your posts at 5000 words; anything longer should be an ebook.

Custom CMS Development

why web designers and developers feel the need to create custom CMSs for sites that would be better off using an opensource CMS, like WordPress, Drupal or Joomla.

Although I could speculate about why I think developers create custom CMSs, it would be just that – speculation (and it would most likely just anger the designer/developer community). Instead, I asked a web designer I know to help me understand why custom CMSs are even considered anymore, given the easy access to numerous free alternatives. He helped me come up with the following list of reasons for a custom CMS:

  • Security through obscurity – hackers are writing scripts for popular CMSs, not custom CMSs.
  • Custom functionality – sometimes the purpose or function of a site is specialized enough that a custom CMS doesn’t address the site requirements in the most efficient manner.
  • Cleaner code – sometimes a site may be so simple and focused that you don’t need all the bells and whistles of WordPress or Drupal, and the code can be cleaner and less bloated.
  • Any other reasons? Let me know in the comments.

Those are all valid reasons, but to how many sites across the web would they apply? Not many, I think. The kinds of sites that I do see getting custom CMS treatment tend to be of the garden variety business web sites. You know the kind, less than 100 pages, typical online brochures with a home page, about us, products/services, contact, TOS/privacy policy page and not much more.

These are the sites that clearly do NOT need a custom CMS. Yet time and time again, I see business owners that don’t know any better, and they end up with a poorly performing site (especially from an SEO perspective). To give an example, one custom CMS I worked with didn’t even provide the ability to change title tags, meta descriptions, or URLs (all things that are easily done in WordPress, for example).

So, if you’re redesigning your site, here are some things to keep in mind if your design company is pushing a custom CMS:

  • They lock you in – anytime you need an update to the system, you have to go to them. Those updates can get pretty expensive (good for your design company, bad for you).
  • Bugs – if they’re building the CMS from scratch, there will be bugs. Are they willing to fix those? For free? For how long?
  • Fit and Finish – your brand new custom CMS will not be as polished in terms of look and feel or usability, because it hasn’t undergone multiple updates that pass through hundreds of developers with feedback from thousands.
  • Functionality – they may not include critical functionality (like the ability to write custom title tags and meta descriptions for each page, custom URLs, etc.). Even worse, they may charge you extra for this functionality and call it an “SEO package.” Don’t get me started on that one.
  • Documentation – there may not be any well written documentation on how to use it, make changes, etc.
  • Migration – once you realize how much better you would be with an opensource CMS, it can be a nightmare to migrate your site from a custom CMS. (see reason #1)

Here’s some more food for thought. WordPress has five lead developers, three designers, nine contributing developers, two documentation and support specialists, eight developer emeriti and countless testers. It was first released on May 27, 2003 and has since been updated 59 times, averaging a major release every six months or so. That’s nearly 7 ½ years of development (for free). Can your web developer offer that?

Why CMS?


  • A centralized repository that enables easy access, archiving and reuse of content
  • Streamlines content publishing process
  • Cost effective & efficient
  • Control access to data, based on user roles.
  • Secure, flexible and modular architecture
  • Easy to use interfaces
  • Removes dependence on hiring technical support

Additionally, if you need custom functionality for your web site, or you don’t want it to look like a cookie-cutter site, there are endless possibilities for customization. Instead of creating a custom CMS, your designer could create a custom theme, or your developer could write a custom plugin. But even that is often unnecessary when you consider the number of plugins already created for popular opensource CMSs:

  • WordPress: 11,704 plugins
  • Drupal: 6,739 modules
  • Joomla: 6,002 extensions

So, do you need a custom CMS? I think I answered that in the first sentence.