Also, Blog pages in WordPress are generated on the fly whenever a page is requested, so you do not have multiple archive pages clogging up your web space. Waiting for pages to rebuild is a thing of the past because template changes are made in scant seconds.
WordPress is built following W3C standards for XHTML and CSS, ensuring that your site is more easily rendered across standards-compliant browsers. Other browsers are supported with a few hacks; it’s a reality of the web that hacks are necessary.
Aggregator support is built-in with a number of standard RSS configurations already done for you, as well as Atom. Following standards makes your WordPress site easier to manage, increases its longevity for future Internet technology adoption, and helps give your site the widest audience possible.
Here at WordPress.org, you can download WordPress, the web software that WordPress.com runs on. Once you’ve downloaded it, you can upload it to a web server and run your own WordPress website.
There is useful information about this distinction on the WordPress.com website.
The only time you would modify your WordPress website with PHP would be when integrating some of the plugins. There are a small number of plugins that still require manual edits to your files. In most cases, clear instructions are usually given within a text file with the plugin.
Other than that, you would not be changing any of the PHP files.
For advanced information check out Know Your Sources.
Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have.
Your site being “hacked” is not a security issue. The security issue will involve knowing how the attacker got in and hacked the site. If you have details on the attack, then email us. If not, then the Support Forums are a better place to report such an issue.
You forgetting your password or losing access to your site is not a security issue. If you lost access through a bug in the WordPress code, then that might be a security issue.
Generally, security issues are complex problems. If you are wanting to report a security issue, then that’s great! You’re in the right place. However, be sure that what you’re reporting is actually a security issue. The experts that you are reporting it to are very busy, and don’t usually respond to non-security issues.
In other words, the security mailing addresses are NOT for support. Don’t send general problems to them.
If you’re having an issue with your own self-hosted WordPress.org site that is not a security issue, then please use the WordPress.org support forums.
For security issues with WordPress plugins, email the information to plugins [at] wordpress.org, including as much detail as possible.
For security issues with the self-hosted version of WordPress, then you should send an email with the details to security [at] wordpress.org. Include as much detail as you can.
In all cases, you should not publish the details.