Wordpress

History

Boone Gorges 1ee4d99972 In `wp_get_attachment_url()`, convert to HTTPS when possible. `wp_get_attachment_url()`, via `wp_upload_dir()`, uses 'siteurl' to generate attachment URLs. When a site is SSL-optional on the front end - ie, 'siteurl' is non-HTTPS, but SSL is available - a number of situations can arise where non-HTTPS attachment URLs cause browser mixed-content warnings: a) SSL is forced in the admin and `wp_get_attachment_url()` is used to generate the `<img>` tag for an inserted image. In these cases, the post content will contain non-HTTPS. Viewing/editing this post in the Dashboard will result in non-HTTPS images being served in an SSL environment. b) `wp_get_attachment_url()` is used in a theme to generate an `<img>` `src` attribute on a public page. When viewing that page over SSL, the images will have HTTP URLs. This changeset switches attachment URLs to HTTPS when it's determined that the host supports SSL. This happens when 'siteurl' is non-SSL, but the current page request is over SSL, and the host of the current request matches the host of the URL being generated. Props joemcgill, boonebgorges. Fixes #15928. git-svn-id: https://develop.svn.wordpress.org/trunk@31614 602fd350-edb4-49c9-b593-d223f7449a82		2015-03-05 02:38:59 +00:00
..
data	Repair the `seems_utf8()` tests that use Big5 encoding.	2014-11-22 20:56:23 +00:00
includes	Ensure that a request URL is always set in `WP_UnitTestCase::go_to()`.	2015-02-23 01:07:18 +00:00
tests	In `wp_get_attachment_url()`, convert to HTTPS when possible.	2015-03-05 02:38:59 +00:00
build.xml
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

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.