Wordpress

History

Boone Gorges 0adb6877b2 Improve validation of `user_login` and `user_nicename` length. The `user_login` field only allows 60 characters, and `user_nicename` allows 50. However, there are no protections in the interface, and few in the code, that prevent the creation of users with values in excess of these limits. Prior to recent changes in `$wpdb`, users were generally created anyway, MySQL having performed the necessary truncation. More recently, the `INSERT`s and `UPDATE`s simply fail, with no real feedback on the nature of the failure. This changeset addresses the issue in a number of ways: * On the user-new.php and network/user-new.php panels, don't allow input in excess of the maximum field length. * In `wp_insert_user()`, throw an error if the value provided for `'user_login'` or `'user_nicename'` exceeds the maximum field length. * In `wp_insert_user()`, when using `'user_login'` to generate a default value for `'user_nicename'`, ensure that the nicename is properly truncated, even when suffixed for uniqueness (username-2, etc). Props dipesh.kakadiya, utkarshpatel, tommarshall, boonebgorges. Fixes #33793. git-svn-id: https://develop.svn.wordpress.org/trunk@34218 602fd350-edb4-49c9-b593-d223f7449a82		2015-09-15 22:13:51 +00:00
..
data	Remove `svn:executable` from test files.	2015-07-26 09:40:58 +00:00
includes	In `WP::parse_request()`, don't add query vars of non-viewable post types to `WP::public_query_vars`. In `register_post_type()`, don't add query vars of non-viewable post types to `WP::public_query_vars`.	2015-09-15 18:53:12 +00:00
tests	Improve validation of `user_login` and `user_nicename` length.	2015-09-15 22:13:51 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Move tests for ms_files_rewriting to separate group, ms-files	2014-11-08 21:07:05 +00:00
README.txt	Update tests/README.txt to reflect the new tests directory structure. props jdgrimes. fixes #25133 .	2013-08-31 13:42:56 +00:00
wp-mail-real-test.php	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00

README.txt

The short version:

1. Create a clean MySQL database and user.  DO NOT USE AN EXISTING DATABASE or you will lose data, guaranteed.

2. Copy wp-tests-config-sample.php to wp-tests-config.php, edit it and include your database name/user/password.

3. $ svn up

4. Run the tests from the "trunk" directory:
   To execute a particular test:
      $ phpunit tests/phpunit/tests/test_case.php
   To execute all tests:
      $ phpunit

Notes:

Test cases live in the 'tests' subdirectory.  All files in that directory will be included by default.  Extend the WP_UnitTestCase class to ensure your test is run.

phpunit will initialize and install a (more or less) complete running copy of WordPress each time it is run.  This makes it possible to run functional interface and module tests against a fully working database and codebase, as opposed to pure unit tests with mock objects and stubs.  Pure unit tests may be used also, of course.

Changes to the test database will be rolled back as tests are finished, to ensure a clean start next time the tests are run.

phpunit is intended to run at the command line, not via a web server.