In Word Press blog, timestamp?

Question

How do I add a timestamp to my Word Press blog? I see how to change the timestamp, but not how to make it appear.

Answer 1

It should be appeared on your post in default setting(or have you disabled it unknowingly?), try to load another theme and see is that something wrong with your current theme.

Answer 2

you sell products on line or WordPress is used by small business or professional. Therefore, you can provide them WordPress installation and customisation services at lower cost. You can also offer wordpress design template with unique theme. there are lot of opportunities - have a detailed study for wide openings Let us now understand what is WordPress Blog....here it is......... (get yourself familiar with PHP and MYSQL without which you cannot do anything -- also understand the vulnerabilities)) WordPress is a blog publishing system written in PHP and backed by a MySQL database. WordPress is the official successor of b2\cafelog, developed by Michel Valdrighi. The name WordPress was suggested by Christine Selleck, a friend of lead developer Matt Mullenweg. The latest release of WordPress is version 2.3.3, released on 5 February 2008. It is distributed under the GNU General Public License. Vulnerabilities BlogSecurity currently maintains a list of WordPress vulnerabilities. In January 2007, many high profile Search engine optimization (SEO) blogs, as well as many low-profile commercial blogs featuring Adsense were targeted and attacked with a WordPress exploit. A separate vulnerability on one of the project site's web servers allowed an attacker to introduce exploitable code in the form of a back door to some downloads of WordPress 2.1.1. The 2.1.2 release addressed this issue; an advisory released at the time advised all users to upgrade immediately. In May 2007, a study revealed that 98% of WordPress blogs being run are exploitable. In a June 2007 interview, Stefen Esser, the founder of the PHP Security Response Team, spoke critically of WordPress's security track record, citing problems with the application's architecture that make it unnecessarily difficult to write code that is secure against SQL injection vulnerabilities, as well as other problems. first understand where you will fail - secure yourself and then proceed