Deployment:-
WordPress can be deployed using various methods on a hosting environment. Users have the option to download
the current version of WordPress from WordPress.org. From there, they can upload the source code and its
dependencies to their hosting environment.
WordPress can also be installed via package management system or deploying a ready-to-use TurnKey
WordPress appliance, which does not require any manual setup or configuration.[9]
WordPress can also be installed via the Microsoft Web Platform Installer which installs WordPress on Windows
and IIS. The Web PI will automatically detect any missing dependencies such as PHP or MySQL then install and
configure them before installing WordPress.
A lot of web hosting firms offer one-click script auto installer program such as Fantastico in their packages.
Users can simply install WordPress through such program.
Advanced users have the option to have WordPress downloaded to their server and consistently updated using
SVN. This will allow users to remain updated easily.
Free hosting services such as WordPress.com offer users an easy way to deploy a WordPress blog on-line without
having to install WordPress on their own web server. A subdomain account (e.g. yourname.wordpress.com) will
be created upon the sign up of free hosting service. Many shared web hosting services also offer automated
WordPress installation through their control panel.
Future:-
After the release of WordPress 3.0, Matt Mullenweg updated the WordPress blog letting the community know that his team will be taking a release cycle off from the WordPress software to focus on expanding and improving the WordPress community. The release of WordPress 3.1 and 3.2 will be due early 2011 and in the first half of 2011, respectively. Upon the release of 3.2 version, the minimum requirement PHP version and MySQL will be raised as well.
Vulnerabilities:-
Many security issues were uncovered in the software, particularly in 2007 and 2008. According to Secunia, WordPress in April 2009 had 7 unpatched security advisories (out of 32 total), with a maximum rating of "Less Critical".Secunia maintains an up-to-date 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.[48] 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 were exploitable because they were running outdated and unsupported versions of the software.
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 made it unnecessarily difficult to write code that is secure from SQL injection vulnerabilities, as well as some other problems.
Multi-blogging:-
Prior to WordPress 3.0, WordPress supported one blog per installation, although multiple concurrent copies may be run from different directories if configured to use separate database tables. WordPress Multi-User (WordPress MU, or just WPMU) was a fork of WordPress created to allow multiple blogs to exist within one installation that is able to be administered by a centralized maintainer. WordPress MU makes it possible for those with a website to host their own blogging community, as well as control and moderate all the blogs from a single dashboard. WordPress MU adds eight new data tables for each blog.
WordPress MU merged with WordPress as part of the 3.0 release.
Key developers:-
Matt Mullenweg and Mike Little were co-founders of the project. The core contributing developers include Ryan Boren, Mark Jaquith, Matt Mullenweg, Andrew Ozz, and Peter Westwood.
WordPress is also developed by its community, including WP testers, a group of volunteers who test each release. They have early access to nightly builds, beta versions and release candidates. Errors are documented in a special mailing list, or the project's Trac tool.
Though largely developed by the community surrounding it, WordPress is closely associated with Automattic, the company founded by Matt Mullenweg.
No comments:
Post a Comment