Cross-Browser Compatibility and HTML & CSS Validation

Leave a Comment
We all know the importance of checking our web pages with multiple browsers, especially when we are designing a new layout for a website. This is the case even if we are writing validated standards-compliant code. The number of extant browsers we need to check with are enormous: Internet Explorer ("IE") 6 to 11, the current version of Firefox, the current version of Chrome (or Vivaldi, which uses the same code), the current version of Safari, and so on. And then there are the different platforms: Windows, Macintosh (Mac), Linux, etc. The problem for most people is that multiple versions of certain browsers cannot co-exist with each other, the most notable example of this is IE for Windows. Unless you happened to have multiple computers, this presents a certain difficulty for the average webmaster. This article suggests some ways for you to run multiple versions of multiple browsers on one computer.

Note that this article is written primarily from the point of view of a person using Windows (the majority of people reading this article), although it does address the issue of Mac browsers and Linux browsers as well.

Firefox and Seamonkey

It's possible for different versions of Firefox and Seamonkey to all co-exist on the same machine.
If you did not already know, Mozilla Firefox and Seamonkey use the same Gecko rendering engine. As such, if you have one of these browsers, you probably don't need to install the other to test your site.
It is easy to make multiple versions of Firefox and Seamonkey co-exist with each other. Install them into separate directories and create a different profile for each browser you install. (For non-Firefox users, this browser allows you to create different profiles so that you can store different settings for different situations.)
To create a different profile for Firefox, simply start Firefox with the following command line:
"c:\Program Files (x86)\Mozilla Firefox\firefox" -ProfileManager
Once you've finished creating profiles, you will want to create shortcuts (Windows terminology) to run the different versions of the browser. This makes life easier for you: you can simply click the appropriate icon for the different versions, and it will load using the correct profile. To specify which profile the browser is to load, put the profile name after the "-P" option.
For example, if you have created a profile named "currentfirefox", your command for running the current version of Firefox with that profile may look like:
"C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -P currentfirefox
Similarly, your command to run the Firefox with a profile called "oldversion" may look like:
"c:\Program Files (x86)\Mozilla Firefox\firefox" -P oldversion
And so on.
I'm not sure that you really need all the different implementations of the Gecko engine to test, though. I personally only test my sites with latest version of Firefox since my site design tends to be simple.

Chrome, Vivaldi, Opera and Safari

Google's Chrome browser, the Vivaldi browser and the current version of Opera all use the same engine. In general, you can expect that the vast majority of people who uses the Chrome browser will be using the latest version, since that browser automatically updates itself whether you want it or not. As such, I tend not to bother to test my sites with earlier versions of Chrome.
You can get Chrome from Google's Chrome site and Vivaldi from Since these browsers use the same engine, if a site works with one browser, it should probably work with the other.
In addition, the Safari web browser share a lot of code in common with both Chome, Vivaldi and Opera, since all four ultimately derive their engine from yet another browser called Konqueror. This similarity will diverge over time, since the engine for Safari is being developed separately from the other three. If you are feeling lazy, you can probably get away with testing under any one of the four for now, although if you really want to be thorough, you probably should install Safari in addition to one of the other three. All four browsers can coexist with each other on the same computer.

Internet Explorer

For most sites, IE users probably comprise the majority of visitors, despite the inroads made by the other web browsers. Now that Microsoft has made Internet Explorer automatically update to the latest version (via Windows Update), chances are that more and more of your visitors will be using the latest version.
Unfortunately, in spite of this, there are still a few users sitting on old versions of the browser. For example, IE 6 is still being used by some people running Windows XP. Although this number is dwindling rapidly, at the time I write this, there are still enough visitors using it for some websites that webmasters feel obliged to continue to support it. (The actual percentage varies from site to site, depending on the target audience of each site.)
My experience in coding and, both of which depend heavily upon Cascading Style Sheets ("CSS") for layout, is that IE 6 and 7 are very different animals from the other browsers or even the later incarnations of IE. Contrary to what you may expect, what works in IE 11, Vivaldi, Firefox and Safari will not necessarily work in IE 6 and 7. IE 6 has numerous bugs in its engine, causing sites that are correctly coded to break under that browser. In other words, if you want to support IE 6 and 7, you need to have those browsers installed somewhere so that you can test with them. You can't just assume that your site will look fine in those old browsers.
Unfortunately, you can't install more than one version of IE. The bulk of IE's code does not get installed into its own subdirectory (or folder) but into Windows' system directory. Although there have been unofficial solutions available for some time among the webmaster community for installing different versions of IE into the same Windows installation, there are various peculiarities in the end result, and the IE versions you get from that behave slightly differently from the standard versions when installed normally. As such, I don't really recommend those "solutions". Instead, if you feel you really need to test with old versions of IE, you should probably try one of the following methods.

Method 1: How to Run More than One Version of Internet Explorer on a Single Machine: Using a Virtual Machine

The official Microsoft-sanctioned method of testing with multiple versions of IE on one computer is to install a virtual machine.
Loosely speaking, virtual machine software allow you to run another copy of Windows within your existing version of Mac OS X, Windows, Linux, FreeBSD or whatever. The virtual machine software pretends to be a new computer, and Windows gets installed into a small space on your hard disk which the software uses to mimic an entire drive.
Microsoft provides pre-activated copies of Windows with various versions of IE in virtual machines free of charge to web developers who need to test their sites in Internet Explorer. The pre-activated Windows expires periodically, so you will need to download a fresh copy from time to time.
You will also need to install one of the supported PC virtual machine software that can run those pre-activated Windows machines. For Windows users, this is either Virtual PC, VirtualBox or VMWare Player, all of which are free, and can be found on the Free PC Virtual Machines and Virtual Machines page. Mac OS X users can use either VirtualBox (which is free), Parallels Desktop (a commercial program) or VMWare Fusion (also a commercial program). Linux users can use VirtualBox.  
Once you've installed both the virtual machine software, and the virtual machine from Microsoft, all you have to do is to run it. This will give you a copy of the appropriate version of Windows with a matching version of IE, which you can use to surf to your website to test it.
Note: Microsoft has terminated its support of Windows XP on April 2014, so it's possible that they will stop providing virtual machines containing XP and Internet Explorer 6 eventually. If that's the case, it will no longer be possible for you to test IE 6 unless you have your own copy of Windows XP. I personally hope that when we reach that date, the number of IE 6 users will be so small that it's no longer even necessary for anyone to bother to test with that desperately obsolete version. You will still be able to test with IE 7 and above though, at least until the version of Windows that comes with those versions stops being supported.

Method 2: How to Run Two or Three Versions of IE on One Machine By Dual or Multi-Booting

This method is not recommended unless you have special reasons (other than testing websites) for needing to dual-boot or multi-boot. It is more technically demanding, disruptive, time-consuming and uses more hard disk space.
For the technically inclined, another way to run two versions of IE on a single machine is to install multiple versions of Windows on that machine, each in its own partition. In plain English, this means that you need to divide your hard disk into (at least) two sections, called "partitions". Then install different versions of Windows into different partitions. You may have to modify your Windows boot menu to support all of them, or use a third party boot manager. (Sorry for the vagueness in this paragraph, but I don't envisage many people to actually need to use this method, and those who do, already know how to do all this.)

How to Test Mac Browsers

Nowadays, you don't actually need a Mac to test Mac browsers, since the default Mac web browser, Safari, and alternative browsers like Firefox and Vivaldi have Windows equivalents.
Having said that, I'm not 100% sure if browsers display things exactly the same way in Windows as in Mac OS X, even if they are the same brand. That is, I'm not sure if (say) Safari for Windows displays things identically with Safari for Mac OS X. However, I think that for the most part, where my sites are concerned, the way they render things is sufficiently alike that I don't need to bother with specially getting a Mac just to test the sites.
Before you ask, although there are things such as free Mac emulators, which are software that run in Windows but pretend to be a Mac and thus can run Mac software, they are not particularly useful from a webmasters' point of view. The working Mac emulators tend to emulate the old obsolete Macs, not modern ones.
In any case, as I said earlier, you shouldn't need a Mac to develop a website that works on it. Just check that your website has valid code and test your website in the Windows versions of Safari, Firefox and Vivaldi, and you'll probably be fine. If, however, your site requires absolute precision in the positioning of its text, images and other elements, and you want to make sure it looks correct on a Mac, you will have no choice but to get a real Mac to test it on.

Testing Linux Browsers

One of the easiest ways to test your site under Linux is to run Linux from a CD or DVD. There are numerous Linux "live" CDs around; see the Free Linux LiveCD Distributions page for a list of them. These allow you to simply boot your machine from the DVD/CD directly into Linux without having to install anything onto your hard disk. Essentially, all you have to do is to download an ISO (which is just an image of the DVD or CD) of the Linux distribution, burn it to your CD or DVD, put it in your CD or DVD drive, and restart your computer. The computer boots from the media and runs Linux without installing anything on your hard disk. From the DVD (or CD), you can run many Linux applications, including the Linux version of Firefox and Konqueror.
If you are feeling lazy, and you have installed an emulator or a virtual machine, as mentioned above, you don't even need to burn the ISO to a CD. You can simply use the virtual machine to boot the ISO — your copy of Linux will then run in the virtual machine. Or, if you prefer, you can also directly install Linux into the virtual machine.
Yet another alternative is to install Linux on your hard disk, using one of the many free Linux distributions around. You can set it up so that it co-exists with Windows (ie, dual-boot). Make sure you have space for a new partition on your hard disk, install it and you're done.
The default browser that comes on many Linux distributions is Firefox (although not necessarily so). However, you will find that even though Firefox tries to render your page the same way under all platforms, the fonts available under Linux are different from those available on Windows. If you don't code your fonts in a cross-platform compatible way, your site may end up being rendered with an ugly font. For example, if your site only specifies "Arial" or "Impact" or some Windows-specific font, since these fonts are not available by default under non-Windows systems, your site will be rendered using either the default font or some other font that the browser thinks matches what you've specified.
If you don't want to bother to run Linux to test, be sure that you at least:
  1. Test your pages under Firefox for your platform.
  2. Specify alternative fonts for your web pages. For example, don't just select a font like "Arial" in your design. Specify alternatives as well, should Arial not be available, like "Helvetica" and a final fallback, something generic like "sans-serif". If you don't know how to do this, please see my article on choosing fonts for more information.

Whether you design your web page using a visual web editor 
 like Dreamweaver or KompoZer, or you code HTML directly with a simple text editor, the generally recommended practice is to validate it after you finish designing it.
This article discusses what validation means, points you to some of the free tools that you can use, and deals with its limitations and the problems that a new webmaster may face.
Note: if you are not sure what HTML and CSS mean, please read What are HTML, CSS, JavaScript, PHP and Perl? Do I Need to Learn Them to Create a Website? before continuing. Otherwise you'll be completely lost here since I assume you at least know what these terms mean.

What does Validating HTML or CSS Mean?

For those unfamiliar with the term, "validating" a page is just a jargon-filled way of referring to the use of a computer program to check that a web page is free of errors.
In particular, an HTML validator checks to make sure the HTML code on your web page complies with the standards set by the W3 Consortium, the organisation ("organization" in US English) that issues the HTML standards. There are various types of HTML validators: some only check for errors, while others also make suggestions about your code, telling you when it might lead to (say) unexpected results.
The W3 Consortium has its own online validator which you can use for free. It may be found at:
CSS validator checks your Cascading Style Sheet in the same manner. That is, it will check that it complies with the CSS standards set by the W3 Consortium. There are a few which will also tell you which CSS features are supported by which browsers (since not all browsers are equal in their CSS implementation).
Again, you can get free validation for your style sheets from the W3 Consortium:
There are numerous other validators around, both free and commercial, focusing on different aspects of your web page. You can find a list of free ones (including specialised validators like those that check your code for accessibility) from the Free HTML Validators, CSS Validators, Accessibility Validators page at

Why Validate Your HTML and CSS Code?

There are a number of reasons why you should validate your page.

It Helps Cross-Browser, Cross-Platform and Future Compatibility

  1. Although you may be able to create a web page that appears to work on your favourite browser (whatever that may be), your page may contain HTML or CSS errors that do not show up with that browser due to an existing quirk or bug. Another person using a different browser that does not share that particular bug will end up viewing a page that does not show up correctly. It is also possible that later versions of your browser will fix that bug, and your page will be broken when people use its latest incarnation.
    Coding your pages so that it is correct without errors will result in pages that are more likely to work across browsers and platforms (ie, different systems). It is also a form of insurance against future versions of browsers, since all browsers aim towards compliance with the existing HTML and CSS standards.

Search Engine Visibility

  1. When there are errors in a web page, browsers typically try to compensate in different ways. Some may ignore the broken elements while others make assumptions about what the web designer was trying to achieve. The problem is that when search engines obtain your page and try to parse them for keywords, they will also have to make certain decisions about what to do with the errors. Like browsers, different search engines will probably make different decisions about those errors, resulting in certain parts of your web page (or perhaps even the entire page) not being indexed.
    The safest way to make sure the search engines see the page you want them to see is to present them an error-free page. That way, there is no dispute about which part of your page comprises the content and which the formatting code.

Limitations: What Validation Does Not Do

Validating your web page does not ensure that it will appear the way you want it to. It merely ensures that your code is without HTML or CSS errors.
If you are wondering what the difference is, an analogy from normal human language will hopefully make it clear. Let's take this sentence "Chris a sandwich ate" which is grammatically incorrect when used in a non-poetic context. It can be fixed by simply reversing the order of the last two words so that the sentence reads "Chris ate a sandwich".
But what happens if you write a sentence that says "Chris ate a pie" when you meant that he ate a sandwich? Syntactically, the sentence is correct, since all the elements of the sentence, subject ("Chris"), verb ("ate") and object ("a pie") are in the right order. Semantically, however, the sentence describes a different thing from what you meant.
HTML and CSS validators are designed to catch the first type of error, exemplified by the grammatical error of my first sentence. So if you write HTML code that has (say) the wrong order, the HTML validator will spot it and tell you. However, it cannot catch errors of the second kind, where you get the spelling and order and all other technical aspects correct, but the code you used does not match the meaning you intended.
Ensuring that your code does what you want it to do requires you to actually test it in a web browser. Depending on the complexity of your code, you may even want to test it with different browsers to make sure that your site looks the same in all of them, since it's possible that you are using features of HTML and CSS that are only implemented in some browsers but not others.

What to Do If You Don't Know HTML and CSS

If you have designed your site using a visual web editor, and are not familiar with HTML and CSS, you will face an additional problem.
While running the validator and getting it to validate your page itself will not be an issue (since the W3 Consortium's validator is not only free, it doesn't even have to be installed to be used), the problem comes when the validator checks your page and tells you that there are errors.
If you have no knowledge of HTML and CSS, you will probably have some difficulty figuring out what those errors mean, whether they are serious, and how to fix them.
Although there is no perfect solution to this, you are not completely without resources.
  1. If you are using an editor like Dreamweaver, Microsoft's Expression Web, KompoZer or BlueGriffon, you can usually assume that the code they produce on their own is valid. From my limited experience (mainly creating demo sites for the purpose of writing tutorials or reviews for, these four editors seem to create correct HTML and CSS code.
    This means that if you get errors when you validate your page, the problems must come from elsewhere. If you have inserted code that you obtained from a website (such as if you have added a Youtube video to your page), it's possible that the code is the source of the error message.
    Alternatively, if you have modified the code on the page manually, the error may have crept in there.
    Having said that, sometimes the error is benign. For example, if you have added XHTML code to a page that has HTML, you may or may not get validation errors since you are mixing 2 different HTML families that have slightly different conventions. As far as I can tell, for the most part, this kind of error does not cause any problem for either browsers or search engines.
  2. Another way is to search the Internet for the solution. For example, you can copy and paste the error message given by the validator into a search engine, and see if there are any websites out there that talk about this particular error. This may not be as fantastic an idea as it first appears, since their solution may be too general to be helpful for your specific problem, unless the error message is the result of your pasting code from some popular source (like Youtube or something of that level of popularity).
  3. A third way is of course to ask someone, whether it's someone you know personally, or someone on the Internet. This solution also has its own issues, since you may get a solution that creates a bigger mess of your page than it had in the first place. It all boils down to their competence and willingness to spend enough time figuring out the problem.
  4. Finally, you can also ignore the problem. If you want to do this, you should test your web page in as many web browsers you can to make sure the error message does not diagnose a problem that causes visible issues. If you find that your site seems to work fine in spite of the error, you may decide to just ignore it and hope for the best.
    Although this solution is not ideal, you may be forced to take it if you can't find an alternative. It's not ideal because the error may bite you later when you least expect it, for example, when there's a new version of some web browser that chokes on the bad code. It may also cause problems in a non-visible manner, such as in the way the search engines index your page.

How Often Should I Validate?

Some people validate every time they make a modification to their pages on the grounds that careless mistakes can occur any time. Others validate only when they make a major design change.
I always validate the template for my pages when I make a major design change. I try to validate my pages each time I make modifications, although I must admit that I sometimes forget to do so (with the occasional disastrous consequence; Murphy's Law doesn't spare webmasters).
I find that having an offline validator helps to make sure that I remember to validate: having to go online just to validate my pages tends to make me put off validation till later, with the result that it'll occasionally get overlooked. For those not familiar with the terminology I use, when I say "offline validator" I simply mean a validator that I can download and install in my own computer so that I can run it on my pages without having to go to the W3 Consortium's website. You can find offline validators on the free validators page I mentioned earlier, that is,
The HTML Tidy validator (listed on that page) is available for numerous platforms (including Linux, Mac, Windows, etc) and has proven helpful to many webmasters the world over.

Final words: 

It's a good idea to test your site with multiple versions of multiple browsers, particularly if you plan to do anything fancy with style sheets on your site. This doesn't mean that you have to support all browsers — for example, the pages on do not work with very old browsers. However, when you are able to test your pages this way, you can at least reduce the number of problems your pages have with the different browsers. The tips in this article allow you to test with multiple browsers even if you have only one machine. As I mentioned above, it's generally a good idea to validate your web page. It will point you to errors that may affect how your website is understood by web browsers and search engines. Even if you are not familiar with HTML and CSS, there are still some ways you can deal with the errors that you discover from validating your page.
Read More

Easier Methods to Get PerfectTech Resume for Entrepreneurs

Leave a Comment
The era is based on technology and global market depends overcome of technology. There are plenty of examples online, and some built into word. Pick something that is a single page- you are writing a resume, not a CV, and recruiters don't have the time or patience to hear your whole life story.

Get PerfectTech Resume for Entrepreneurs 

 “A powerful resume should leap off the page saying, ‘Me! I’m the one you want to hire!’” advises software engineer Gayle Laakmann McDowell in her book The Google Resume: How to Prepare for a Career and Land a Job at Apple, Microsoft, Google, or Any Top Tech Company. She says that every line in these documents should have value and contribute to convincing the employer to hire you. That said, below are 15 tips from McDowell and others on creating the perfect tech resume.

1. Focus on accomplishments: Focus less on your job duties in your last job and more on what you actually accomplished, with an emphasis on tangible results (increased app sales revenues by 20 percent, developed software that reduced costs by 10 percent, etc.).

2. Quantify results: Avoid saying general things like “improved customer satisfaction,” “increased company profits,” or “reduced number of bugs.” Instead, provide quantifiable metrics that demonstrate how your work helped your company save money, reduce costs, improve customer service, etc.

3. Target your resume: Gone are the days of sending one generic resume to hundreds of companies. You should target each resume to the specific job listing and company.

4. Don’t get too technical: Technical terms, sales and marketing slang, and acronyms that are commonly used at one company may be like a foreign language to recruiters or hiring managers at other companies. Make your resume universally understood by using industry-recognized terminology and explaining anything that recruiters might find confusing.

5. Be concise: We’ve all heard the stats about hiring managers tossing resumes that have just one typo. Although tech companies tend to be more forgiving, that’s no reason to submit a grammatically incorrect, misspelled, and otherwise poorly presented resume.

6. Be clear, and structure your resume well: Try to think like a recruiter when creating your resume. Provide the information recruiters want so that they don’t throw your resume in the trash pile. For example, if you worked as a software engineer at a top company such as Microsoft or Intel, stress the company name rather than your job title, since that will impress the recruiter the most.

7. Ditch the “objective”:  Use an Objective in your resume only if you are straight out of college or want to bring attention to the fact that you want to transition to a new role (for example, moving from a position in software engineering to one in sales). An Objective can also be a drawback because your stated job interest (mobile software developer) might convince the recruiter that you’re not interested in other lucrative and rewarding positions (user interface engineer, Web developer, etc.) he or she needs to fill.

8. Don’t be vague in your “summary”:  If you use a Summary section, be sure that it’s filled with key accomplishments (backed up by hard numbers), not vague pronouncements about your detail-oriented personality, strong work ethic, etc. Some people rename this section “Summary and Key Accomplishments.”

9. Think accomplishments over duties: Work experience is a key component of your resume, but it should not feature a comprehensive list of all the jobs that you’ve held (especially if you’ve worked in the industry for years or had many jobs). List the most important positions that will show the hiring manager that you’re qualified for the new job. Provide the largest amount of detail for your current or most recent job (or the one that is most applicable to showing that you’re qualified for the new position). Be sure to list your accomplishments, rather than just job duties. Again, think about what the hiring manager wants to see to convince him or her to call you in for an interview.

10. Minimize your “education” as you gain experience: Professional experience matters more than education in the tech industry, but it’s important that the Education section effectively conveys your educational background. If you have a nontraditional degree that recruiters may not be familiar with, be sure to offer a one- or two-sentence description of the major. Recent graduates should list their GPA only if it’s at least 3.0 on a 4.0 scale (of course, omitting your GPA may raise a red flag with the recruiter). Recent graduates should also list any college activities or awards that they believe will help them land the job, but they shouldn’t list everything they did while in school. Finally, the rule of thumb is that the Education section shrinks as you gain experience. Eventually, it will simply list the bare essentials such as university name, location, dates attended, degree earned, etc.

11. Don’t forget the skills: Tech workers should be sure to include a Skills section on their resume. This section should list software expertise, programming languages, foreign languages, and other applicable skills, but it’s a good idea to skip basic skills (such as Microsoft Word) that many applicants have. The key is to list skills that will help you land the job.

12. Go big, and keep the little for later: When considering what to include on your resume, focus on the “big,” and save the “little” for the job interview. This means you should detail big, eye-catching accomplishments such as new products and technologies that you helped develop, major employers (such as Google or Amazon) that you worked for, major customers that you interacted with, and increases in sales, profits, or productivity that you contributed to. Be ready to provide the details regarding these accomplishments and background information during the actual interview.

13. Use keywords: At its employment web site, Microsoft advises applicants to detail on their resume how their experiences (leadership roles, work duties, school activities, etc.) helped them to grow as a person and as a professional. This is a good approach, since you always want to show that you are evolving as a person and eager to learn new skills. Also, use keywords that match those listed in the job announcement. For example, if you’re applying for a position in e-marketing and search engine optimization, then your resume should include these terms. This will help you get noticed by resume-scanning software and advance past the first screening stage.

14. Use your name: If you send your resume as an attachment, don’t name it “resume.doc” or “resume.pdf.” That’s the surest way for your resume to get lost among the thousands of other submissions. Instead, name the file starting with your last name, then your first name, then the date. And add the job identification number if one is available.

15. Use tools and follow the directions: Some companies such as Microsoft offer resume-building tools for job applicants at their web sites. These tools will help you determine what you should and should not include in your resume. Be sure to use these tools, if offered. And follow instructions to the letter. Google, for example, requires applicants to submit their resumes in PDF, Microsoft Word, or text formats. It also requires that all application materials for U.S. jobs be submitted in English.

Final Words: 

My final suggestion, just get somebody super honest to review your resume. Or better yet, get more than one somebody to review your resume. They should check for relevance, spelling, syntax, etc. It's preferable that you choose somebody who also knows you fairly well, because they can sometimes remember gems that you've forgotten to include. Take their feedback as a gift; if they are tough than they probably want to help you succeed. So, don't forget to say thank you!
Read More

Instantly fix Feedburner feeds as not updating issue in WordPress Website

Leave a Comment
We have discussed more Feedburner on how to setup Feedburner feeds for WordPress and the importance of Feedburner for SEO.  For verifying Technorati claim token a few days back when we checked our Feedburner feed it seemed like our feeds were not updated for several posts and it gave as a big shock. After several types of research we found out the solution for Feedburner feeds not updating issue in WordPress and we are here to help with that problem.

How to fix Feedburner feeds not updating issue in WordPress

Step 1 Check for errors

Login to your Feedburner account and you will see Feed medic alerts which monitors the health of your feed and notifies you if anything bad with your source feed. Click on that link and check whether your feed has problems. In our case it’s clear which says “your source feed is now working fine”
Fix Feedburner feeds not updating issue in wordpress
We suggest you to check your feeds with Feed validator. Is it a valid RSS. Fix Feedburner feeds not updating issue in wordpress

Step 2 Activate Ping Shot and Ping Feedburner

Have you followed this article on how to setup Feedburner feeds for WordPress then you might be activated Ping Shot. Go to your Feeds publicize tab and you will see Ping Shot, open and activate Ping Shot.
Fix Feedburner feeds not updating issue in wordpress
Feedburner usually takes 30-minute interval to update your feeds instead of that you can manually ping your blog feeds which updates immediately. Use this link ping Feedburner and enter your blog address and Ping Feedburner. Check your feeds whether the problem is resolved and if not proceed to step 3.

Step 3 – Is your Feed size is less than 512k

Usually, Feedburner will not process if the blogs original feed size is greater than 512k which applies to actual feeds and not for media files. To know the size of your feed use this service Web-Sniffet and enter your feed address.
Try this: Reduce the number of feeds in your WordPress reading settings. Check whether the problem is resolved if not proceed to step 4.
Fix Feedburner feeds not updating issue in wordpress

Step 4 Resync your Feeds

For most people doing this step will solve the problem with Feedburner feeds not updating issue, but for us this too didn’t help.
In your Feedburner dashboard go to Troubleshootize tab and you can see some most common problems with Feedburner and solutions. Just scroll down and you can see “The nuclear option: Resyncing Your Feed” click Resync now button which clears the cached version and refreshes the original Feed.
Fix Feedburner feeds not updating issue in wordpress
Check out your feeds! Hope your problem is resolved on Feedburner feeds not updating issue. Still not then proceed to the final step.

Step 5 Are you using cache plugin for WordPress

All the above steps didn’t help us and we finally found out that cache plugin is not updating the feeds. We use W3TC and in W3TC page cache options uncheck the box that says “cache feeds: site, categories, tags, comments”
Fix Feedburner feeds not updating issue in wordpress
Once done now again Resync your feeds which should fix the Feedburner feeds not updating issue in WordPress.
If you followed some other methods that resolved your problem then please let us know by commenting below.
Read More

Easiest Ways to insert .htaccess redirect http to https with Re-write Rules

Leave a Comment
The Apache module mod_rewrite allows you to rewrite URL requests that come into your server and is based on a regular-expression parser. The examples presented here show how to:
Direct requests for one subdirectory to a different subdirectory or the primary directory (document root)
Example: becomes or just

Direct requests to a subdirectory

Example: becomes
Add www to every request
Example: becomes Or, convert http:// to https://.
Convert URL to all lowercase using Rewrite Map
Example: becomes
This will help prevent typos from producing http errors.
When implemented correctly, modrewrite is very powerful. There are many other applications for modrewritethat you can learn about at Please reference their website for other possible rewrite scenarios.
These examples are provided as a courtesy - (mt) Media Temple does not design custom rewrite rules for individual customer websites.
Create a plain text .htaccess file (click the link for details on this type of file), or add the lines from the example to the top of your existing .htaccess file.
Add the lines from the appropriate example to your file. Note that you should replace example text with your own information. Replace with your own domain, folder1 with your own folder name, file.htmlwith your own file name, etc. Save your changes.
Use or to upload the file to the document root of the appropriate domain. If your domain is, you should upload the file to:
That's it! Once you've uploaded the file, the rewrite rule should take effect immediately.
Some Content Management Systems (CMSs), like WordPress for example, overwrite .htaccess files with their own settings. In that case, you may need to figure out a way to do your rewrite from within the CMS.
Direct requests for one subdirectory to a different subdirectory or the document root becomes or just
domains/ must exist and have content in it for this to work.
This .htaccess file will redirect to Choose this version if you don't have the same file structure in both directories:
Filename: .htaccess
Options +FollowSymLinks
RewriteEngine On
RewriteRule ^folder1.*$ [R=301,L]
This .htaccess file will redirect to plain Choose this version if you want people redirected to your home page, not whatever individual page in the old folder they originally requested:
Filename: .htaccess.
Options +FollowSymLinks
RewriteEngine On
RewriteRule ^folder1.*$ [R=301,L]
This .htaccess file will redirect to Choose this version if your content is duplicated in both directories:
File name: .htaccess
Options +FollowSymLinks
RewriteEngine On
RewriteRule ^folder1/(.*)$$1 [R=301,L]
Upload this file to folder2 (if you followed the first or third example) or your html folder (if you followed the second example) with FTP:
Filename: index.html
Mod_rewrite is working!
Then, if you followed the first or second example, visit in your browser. You should see the URL change to or and the test page content.
If you followed the third example, visit You should be redirected to and see the test page content.
Code explanation
Options +FollowSymLinks is an Apache directive, prerequisite for modrewrite.
RewriteEngine On enables modrewrite.
RewriteRule defines a particular rule.
The first string of characters after RewriteRule defines what the original URL looks like. There's a more detailed explanation of the special characters at the end of this article.
The second string after RewriteRule defines the new URL. This is in relation to the document root (html) directory. / means the html directory itself, and subfolders can also be specified.
$1 at the end matches the part in parentheses () from the first string. Basically, this makes sure that sub-pages get redirected to the same sub-page and not the main page. Leave it out to redirect to the main page. (It is left out in the first two examples for this reason. If you don't have the same content in the new directory that you had in the old directory, leave this out.)
[R=301,L] - this performs a 301 redirect and also stops any later rewrite rules from affecting this URL (a good idea to add after the last rule). It's on the same line as RewriteRule, at the end.
Note: The directory folder1 must be unique in the URL. It won't work for The directory folder1 must exist and have content in it.
This .htaccess file will redirect to
Filename: .htaccess
Options +FollowSymLinks
RewriteEngine On
RewriteCond %{HTTPHOST}$ [NC]
RewriteCond %{HTTPHOST} !folder1
RewriteRule ^(.*)$$1 [R=301,L]
Upload this file to folder1 with FTP:
Filename: index.html
Mod_rewrite is working!
Then, visit in your browser. You should see the URL change to and the test page content.
Code explanation
Options +FollowSymLinks is an Apache directive, prerequisite for modrewrite.
RewriteEngine On enables modrewrite.
RewriteCond %{HTTP_HOST} shows which URLs we do and don't want to run through the rewrite.
In this case, we want to match
! means "not." We don't want to rewrite a URL that already includes folder1, because then it would keep getting folder1 added, and it would become an infinitely long URL.
[NC] matches both upper- and lower-case versions of the URL.
RewriteRule defines a particular rule.
The first string of characters after RewriteRule defines what the original URL looks like. There's a more detailed explanation of the special characters at the end of this article.
The second string after RewriteRule defines the new URL. This is in relation to the document root (html) directory. / means the html directory itself, and subfolders can also be specified.
$1 at the end matches the part in parentheses () from the first string. Basically, this makes sure that sub-pages get redirected to the same sub-page and not the main page. Leave it out to redirect to the main page of the subdirectory.
[R=301,L] - this performs a 301 redirect and also stops any later rewrite rules from affecting this URL (a good idea to add after the last rule). It's on the same line as RewriteRule, at the end.
ADD WWW OR HTTPS becomes Or, becomes
This .htaccess file will redirect to It will also work if an individual file is requested, such as
Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^ [NC]
RewriteRule ^(.*)$$1 [R=301,L]
This .htaccess file will redirect to It will also work if an individual file is requested, such as
Filename: .htaccess
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$$1 [R,L]
Visit in your browser. You should see that the same page is displayed, but the URL has changed to (first example) or (second example).
Also, will become or
Code explanation
Options +FollowSymLinks is an Apache directive, prerequisite for modrewrite.
RewriteEngine On enables modrewrite.
RewriteCond %{HTTP_HOST} shows which URLs we do and don't want to run through the rewrite.
In this case, we want to match anything that starts with
[NC] matches both upper- and lower-case versions of the URL.
RewriteRule defines a particular rule.
The first string of characters after RewriteRule defines what the original URL looks like. There's a more detailed explanation of the special characters at the end of this article.
The second string after RewriteRule defines the new URL. This is in relation to the document root (html) directory. / means the html directory itself, and subfolders can also be specified.
$1 at the end matches the part in parentheses () from the first string. Basically, this makes sure that sub-pages get redirected to the same sub-page and not the main page.
[R=301,L] - this performs a 301 redirect and also stops any later rewrite rules from affecting this URL (a good idea to add after the last rule). It's on the same line as RewriteRule, at the end.
This .htaccess rule will make sure that all characters entered into a url are converted to lowercase. This helps prevents errors caused by typos. becomes
Note: Because this rule requires an edit to a server level configuration file, Grid and Managed WordPress users will not be able to implement this rule.
In order for this to work properly, you must also add a directive to your vhost file (httpd.conf):
RewriteMap lc int:tolower
For Plesk: Navigate to Domains > > Web Hosting Settings > Additional Apache Directives, and place the above code.
Next, open your .htaccess and add the following lines:
RewriteEngine On
RewriteCond %{REQUESTURI} [A-Z]
RewriteRule . ${lc:%{REQUESTURI}} [R=301,L]
Note: Instead of using RewriteMap to convert URLs to lowercase, it is recommended by Apache that mod_spelling be used to ignore case sensitivities.
Navigate to your domain using a combination of uppercase and lowercase letters.
Code Explanation
RewriteEngine On enables modrewrite.
RewriteCond %{REQUESTURI} [A-Z] - Grabs the entered address.
RewriteRule . ${lc:%{REQUEST_URI}} - Uses the 'lc' variable that was added to the vhost file to convert all characters to lowercase.
[R=301,L] - Performs a 301 redirect and also stops any later rewrite rules from affecting this URL (a good idea to add after the last rule). It's on the same line as RewriteRule, at the end.
Regular expressions
Rewrite rules often contain symbols that make a regular expression (regex). This is how the server knows exactly how you want your URL changed. However, regular expressions can be tricky to decipher at first glance. Here's some common elements you will see in your rewrite rules, along with some specific examples.
^ begins the line to match.
$ ends the line to match.
So, ^folder1$ matches folder1 exactly.
. stands for "any non-whitespace character" (example: a, B, 3).
* means that the previous character can be matched zero or more times.
So, ^uploads.$ matches uploads2009, uploads2010, etc.
^.$ means "match anything and everything." This is useful if you don't know what your users might type for the URL.
() designates which portion to preserve for use again in the $1 variable in the second string. This is useful for handling requests for particular files that should be the same in the old and new versions of the URL.
See more regular expressions at
Examine the new URL in your browser closely. Does it match a file that exists on the server in the new location specified by the rewrite rule? You may have to make your rewrite rule more broad (you may be able to remove the $1 from the second string). This will direct rewrites to the main index page given in the second string. Or, you may need to copy files from your old location to the new location.
If the URL is just plain wrong (like - note the two /s) you will need to re-examine your syntax. (mt) Media Temple does not support syntax troubleshooting.
If you notice that your URL is ridiculously long, that your page never loads, or that your browser gives you an error message about redirecting, you likely have conflicting redirects in place.
You should check your entire .htaccess file for rewrite rules that might match other rewrite rules. You may also need to check .htaccess files in subdirectories. Note that FTP will not show .htaccess files unless you have enabled the option to view hidden files and folders. See our .htaccess article for details.
Also, it's possible to include redirects inside HTML and PHP pages. Check the page you were testing for its own redirects.
Adding [L] after a rewrite rule can help in some cases, because that tells the server to stop trying to rewrite a URL after it has applied that rule.
.htaccess redirect inserted by Really Simple SSL
Really Simple SSL has an option which inserts the detected .htaccess redirect rules. There are several server configurations, which each require their own .htaccess redirect. The plugin tries to detect which rule applies, and then tests the result. In some cases the test fails, or the .htaccess was not writable. In that case, you’ll have to insert the .htaccess redirect yourself. I would always recommend to redirect with .htaccess, as this is a slightly faster redirect than the default interal 301 redirect.
Enable “stop editing htaccess”
If the plugin can’t test the .htaccess redirect rule, it writes an empty set of rules to the .htaccess when you load the settings page. To prevent overwriting your manually added .htaccess, enable this setting.
SSL test page
If you go to (use https, not http), you will see a page with some test results. This will look something like this:
This page is used purely to test for ssl availability.




In this case, you can see ssl is functioning, and the server variable server[“https”]=on.
Depending on this output, you should add a corresponding redirect rule to your .htaccess file
If this page is not working for your for some reason, you’ll have to find out by trial and error.
If this page shows “successfully detected SSL”, but you do not see any detected variables, no server configuration I know about was found, so none of the below may apply. You’ll just have to try.
If you find another redirect rule which works for you, please let me know so I can improve the plugin and this documentation.
Where do I find the .htaccess file?
Open your FTP client (filezilla, or any other), go to your webroot (where you can see the WordPress files like wp-admin, wp-content), and look for the .htaccess file. Be sure to check that your ftp client shows hidden files as well.
What codesnippet do I need to add?
Add every codesnippet above the WordPress .htaccess lines. If Really Simple SSL added any rules which caused a redirect loop, remove them and set the Really Simple SSL settings to “stop editing the .htaccess file”.
If you see #SERVER-HTTPS-ON# (on), add
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteRule ^(.)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
If you see #SERVER-HTTPS-ON# (1), add
RewriteEngine on
RewriteCond %{HTTPS} !=1
RewriteRule ^(.)$ https://%{HTTPHOST}%{REQUESTURI} [R=301,L]
If you see #SERVERPORT443#, add
RewriteEngine on
RewriteCond %{SERVERPORT} !443
RewriteRule ^(.*)$ https://%{HTTPHOST}%{REQUEST_URI} [R=301,L]
If you see #LOADBALANCER#, add
RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTPHOST}%{REQUESTURI} [R=301,L]
If you see #CDN#, add
RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-SSL} !on
RewriteRule ^(.*)$ https://%{HTTPHOST}%{REQUESTURI} [R=301,L]
If you see #Cloudflare#, add
RewriteEngine on
RewriteCond %{HTTP:CF-Visitor} ‘”scheme”:”http”‘
RewriteRule ^(.*)$ https://%{HTTPHOST}%{REQUESTURI} [R=301,L]
If you see #ENVHTTPS#, add
RewriteEngine on RewriteCond %{ENV:HTTPS} !=on
RewriteRule (.*) https://%{HTTPHOST}%{REQUESTURI} [R=301,L]
On the bottom of the ssl test page, you will see HTTP HOST. This should be the same as your domain. If not, you might need to hardcode your domain to prevent redirect issues, like this:
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteRule ^(.*)$$1 [R=301,L]

Read More
Next PostNewer Posts Previous PostOlder Posts Home