Funny experience while using Microsoft Word as an editor

It was with interest that I read some time ago from a blog post that posting directly from Microsoft Word to a blog or Facebook can have unpredictable and undesired funny results.

As many people may be using Microsoft Word for writing articles or editing, probably because the app helps in checking spelling and grammar and also to count the number of words in an article without manual counting, there is a tendency to post the edited articles directly into blogs. In such cases, especially in the visual mode, there is a possibility the article will carry with it the formatting code used by the program along with it and will not be visible.

I did not take it seriously, as I always use the HTML mode and I can always see the coding/ HTML that goes into the blog post. But the writer of the article claimed that even in HTML mode, there will be some codes associated with formatting in Microsoft Word, and carried to the posts and reappearing when re-posting, exporting/ importing, or re-tweeting.

I have noticed it happening while posting to the good old MS FrontPage that I used to use for HTML editing. And today a funny thing happened while I was sharing an interesting article I found on a friend’s blog on poverty in New York City to Facebook. After that I just posted an excerpt that I edited in Microsoft Word as my review to my Facebook post.

The words I posted were only:

Approximately 1.4 million New Yorkers rely on soup kitchens and food pantries. Please don’t make them beg

And what went into the Facebook box was a huge chunk of 17,330 characters/ 1272 words, instead of only 105 characters/ 17 words. See the entire code to format 17 words in the text box below (scroll it down, it is quite huge):

Advice: If you are using Microsoft Word as an editor, before posting to blogs, or other locations, first cut and paste to a plain editor like a Notepad and from there cut and paste to wherever you want so that the embarrassing hidden code like the above will disappear.

How to modify WordPress Themes

If you are using a standard WordPress theme other than a custom theme developed exclusively for you, chances are that you will lose all the modifications that you made to your theme, when the original theme is modified by the theme developer.

As most of you using ready-to-use WordPress must have noted that you always want to make changes in the look and appearance of the theme. The easiest way to do such changes without changing the core design or structure is to edit the CSS style sheet. For example, you do not like the font Verdana and want to replace it with Arial, you simply add Arial as the first font in the appropriate places in the style sheet. And you are done and find your site or blog showing up with your desired font.

In the above way, you can change font sizes, colors, and many other things just by editing the style sheet. With changes in some other files, you can entirely change the look and feel of your site. Some people may love to present their site in the most aesthetic way and experiment with the themes and style a lot. This may be required even in a custom designed theme, as you find something or the other always needing improvements.

So, you have done everything and all on a sudden everything is lost! You feel frustrated. To avoid this create a Child Theme, the original theme remaining as the parent theme. By doing this, when the parent theme is updated by its developer, you can still continue with your own modified theme as your modifications are automatically preserved, as the Child Theme settings override the Parent Theme, as the Child Theme inherits the functionality of the Parent Theme.

To create Child Theme, simply create its own directory named as ‘original theme-child (or anything you like), and place your modified style.css file in it, and you have a child theme of your own! You can do so without modifying the styling and layout of a parent theme, with some understanding of HTML and CSS. Such a Child Theme works as good as your own custom designed theme and it is not affected when the parent theme is updated. Your newly created child theme can have as little as a style.css file to as much as any full-fledged theme contains with the optional additions of functions.php, template files and other files. For a good understanding of creating your own Child Theme and examples of changes and scripting, visit official WordPress Codex for Child Themes.

Harmful Hidden Codes in Free WordPress Themes

After having encountered some unexpected problems like pre-installed AdSense link unit codes, theme supplier’s RSS feeds URLs, and some other codes like multiple URLs of third parties that I could not remove from any visible PHP files, I made a search for the possible reasons, as I knew that some FREE theme suppliers do include such codes as a price or cost for supplying such free themes. One of the most popular WordPress theme developers is transparent enough to declare in his site that certain codes are pre-installed to set off the costs for developing themes and running the site. He frankly instructed to join as a member and get the instructions to remove the codes, of course for a small membership free, and it is worth it.

In the case of another themes supplier, the approach was different. The instructions in the supplier’s site simply said that for free themes no support or guidance is available, and for support (meaning to remove unwanted codes or remove ads or other things not related to you), you should select only premium themes. I even appreciate such an approach.

But what about themes that do not have any visible problems, but have hidden codes that are encrypted and embedded in the theme files, quite often in such a fashion that you cannot detect them? Such codes can even steal your passwords and login details and all that can cause losses and security problems for your business and site. A detailed explanation with examples can be found at www.tech-evangelist.com.

If you are using a free WordPress blog, you are the safest, because everything supplied therein are pre-tested and safe. For those who install WordPress in their own self-hosted WordPress sites too, there are 1,296 themes available for free download, which show 25,066,203 downloads at the time of writing this post. You can go to http://wordpress.org/extend/themes and download FREE themes from there. These are WP-tested themes and hence safe.

The next alternative is to go to the sites of the developers of the same themes offered by WP and download FREE themes, if available (most of them offer both FREE and premium themes).

Also, there are thousands of reliable theme developers who offer free WordPress themes and plugins as a community service for WP. Search around and you will get the preferred theme that is safe too. In the next posts, I will include the addresses/ URL sources of some such reliable theme suppliers. Anyway, my intention is not to say that all themes suppliers and developers are embedding malicious codes, but there are a few who do so.