Sorry, there was a hiccup with the site, can you delete the double posting please, thank you.

Hi guys

Any chance of adding half a dozen posts with images? Really useful for testing and demoing things like featured post sliders.

thanks

Chris

Remove personal email addresses from test data and replace them with test email addresses, which will need to be hooked into a Gravatar account.

http://wptest.io/demo/category/shortcodes/

Just check that it not work: [wpvideo tFnqC9XQ w=680]

Something like this:
curl -O https://raw.github.com/manovotny/wptest/master/wptest.xml
wp import wptest.xml --authors=create
rm wptest.xml

I am not setting them intentionally, so WordPress must be doing this at some point (on insert, export, etc).

This makes responsive testing really difficult.

Requested by @Japh via email.

Mucking up history... Oops!

Error:

Still sticking with science and Isaac Newton's E = MC², which should lift the 2 up.

Should be:

Still sticking with science and Albert Einstein's E = MC², which should lift the 2 up.

Suggested by @saddington.

Like how the Further theme suggests doing pull quotes using built-in WordPress classes.

I just got the following note in the CLI:

Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package manovotny/wptest could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.

Read <http://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Reported by a user:

http://wptest.io/demo/post-format-video-videopress/ appears to be broken.

The import process stop with the following message:

Processing post #976 ("Eddy - Need (Remix)") (post_type: attachment)
-- 35 of 198
-- Fri, 21 Nov 2014 02:20:22 +0000
PHP Fatal error: Maximum execution time of 60 seconds exceeded in C:\wamp\www\s
ubdomains\sarc\web\cms\wp-includes\class-http.php on line 1044

What should I do to solve this

I'm just testing the HTML / HTML5 form elements while building the theme. But, There is no post in theme review, Which contain all the HTML / HTML5 form elements.

So, I'm not able to see how all HTML / HTML5 form elements looks in theme review.

The Title With Special Characters ~!@#$%^&*()-_=+{}[]/;:’”?,.>` needs to be updated to have spaces in-between each special character.

Spaces help flush out bad JavaScript and minification issues.

Similar to Bootstrap, is there a way to download only the pieces of the test that you want to cover?

Say for example that I'm creating a theme without the blog, I wouldn't need to test sticky posts but I should test for alignment, image resizing, etc.

This would also enable developers to create tests for specific plugins. I use Features by WooThemes & Testimonials by WooThemes which I would love to test but it seems silly to make everyone test for them.

Any thoughts on how this would be possible? I should be able to contribute a little bit. :)

Add a CONTRIBUTING.md file, and link to it from the readme, so potential contributors can be guided as to how they can make changes for PRs. It should cover how to export the updated XML file.

There is a typo on the Captain America image title.

The vertical image in the Featured Image post has the alt text of "Horizontal Featured Image" instead of "Vertical Featured Image"

To all the people that might have issues getting wptest.io's WP test data into current version WP 4.5 ->> give this new separately developed WP Importer a shot.

https://github.com/humanmade/WordPress-Importer

More about this new WP Importer here

http://wptavern.com/help-test-the-new-wordpress-importer-plugin-in-development

and here.

https://make.wordpress.org/core/2015/11/18/wordpress-importer-redux/

Hope this works and hope this info helps people that have had no luck with the old WP Importer that can be found here.

Requested by @Japh via email.

There is slight issue with the Scheduled post.

The maximum date in 32 Bit PHP Systems (which would probably be most Windows server users) is 2038-01-19 04:14:07

The publish date seems to default to:

// Line 9275
Sat, 01 Jan 2050 18:00:18 +0000

// Line 9284
2050-01-01 12:00:18

//Line 9285
2050-01-01 18:00:18

Getting the following error on import:
Notice: wp_get_http is deprecated since version 4.4.0! Use WP_Http instead. ..../wp-includes/functions.php on line 3831

Version 4.8.1

Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0

Everything seems to work ok. Images loaded. Maybe WP core is just a notice and it still uses wp_get_http from deprecated list.

On the Markup and Formatting post and equivalent comment, the "Header one" thru "Header six" should be "Heading One" thru "Heading Six".

Header changed to Heading (and capitalised second word).

When I look at the bash script, then why is it fetching the exact same file again (from this repository)? Doesn't seem to make any sense.

Can you update this to also include the oembed of WP sites?https://make.wordpress.org/core/2015/10/28/new-embeds-feature-in-wordpress-4-4/

Great idea – Hope to use it on my next project. However, the feature described in the title would be really neat. One of the WordPress test data plugins does this, and it's really helpful. I can look up which one if you need to see how they do it.

Tons of <span style="line-height:1.714285714;font-size:1rem;> in the test data.

Using WordPress Importer Redux I am getting an almost 100% import. Well one "term" is missing.

It tells me that it could not find the post parent for various posts.

What does this mean please?

Currently there are two problems with the import shell script:

1. It does assume that wp is installed and available. That can easily be checked up front and if not, abort gracefully, informing the user what to do.
2. It does not allow to run as root. In a Docker install, we have the problem that Docker containers in nearly all cases run as root, so the --allow-root flag should be used for the wp command. Maybe the best would be to allow running the script with one additional argument. That could simply be a yes/no flag that is prompted and read.
3. When the "WP Importer" is not present or active, it's hard to install. Maybe there should be a check if the plugin is installed. wp ${ROOT} plugin is-installed wordpress-importer and then prompt if the user wants to install and activate it: wp ${ROOT} plugin install wordpress-importer --activate.
4. The prompt for the WordPress path could slightly be improved. As the relative directory/path might be unknown, it might be better to ask for an "absolute" path.
5. When automating this, the prompt is not really nice. It would be nice to either take the argument as flag or argument, and if not present: ask for the argument during processing.

Requested by email from Matt Beall:

If somehow you could build in a customization tool that would allow for testing of custom post types and custom taxonomies, that would be awesome.

Hi
You have many bad img url
https://github.com/poststatus/wptest/blob/master/wptest.xml
For example
http://wptest.io/demo/wp-content/uploads/2011/01/canola2.jpg
http://wptest.io/demo/wp-content/uploads/2011/01/dsc20050315_145007_132.jpg

Hi,
This is no issue with your test data, but I think it would be a good place to document the issue. Maybe some other users will hit the Bug when importing the test data. The bug is in the current WordPress importer plugin when using it with PHP 7.0
During the Import of the XML there is no error message displayed and the importer finishes without problems. Everything is imported, including the menus them self, but they are empty!
The Bug is documented here https://core.trac.wordpress.org/ticket/36281 and https://wordpress.org/support/topic/fails-to-export-or-import-menu-items-when-using-php7/

To fix it you have to change the file wp-content/plugins/wordpress-importer/wordpress-importer.php at line 884

from

$$meta['key'] = $meta['value'];

to

${$meta['key']} = $meta['value'];

Just add the two brackets and you are good to go.

I tested this on my wordpress 4.8.2 running on Ubuntu 16.04 with php 7.0

Hope this will help any future user to save some time searching for a solution

Regards,
Andreas

I want to include this in a build script but I can't load it in via Composer currently. You might want to update the vendor name in the composer.json and submit it

https://packagist.org/

After following the instructions, this was the output:

Should I move the uploads folder to my WP site first? Did not find any mention of such step in README.

OCR of the message:

Import WordPress
Failed to import Media “canola2”
Failed to import Media “dsc20050315_145007_132”
Failed to import Media “dsc20050727_091048_222”
Failed to import Media “dsc20050813_115856_52”
Failed to import Media “dsc20050831_165238_332”
Failed to import Media “dsc20050901_105100_212”
Failed to import Media “Bell on Wharf”
Failed to import Media “Golden Gate Bridge”
Failed to import Media “Sunburst Over River”
Failed to import Media “Boardwalk”
Failed to import Media “Yachtsody in Blue”
Failed to import Media “Rain Ripples”
Failed to import Media “Sydney Harbor Bridge”
Failed to import Media “Wind Farm”
Failed to import Media “Antique Farm Machinery”
Failed to import Media “Orange Iris”
Failed to import Media “Rusty Rail”
Failed to import Media “Sea and Rocks”
Failed to import Media “Big Sur”
Failed to import Media “Windmill”
Failed to import Media “Huatulco Coastline”
Failed to import Media “Brazil Beach”
Failed to import Media “Huatulco Coastline”
Failed to import Media “Boat Barco Texture”
Failed to import Media “dsc20040724_152504_532”
Failed to import Media “dsc20050604_133440_3421”
Failed to import Media “OLYMPUS DIGITAL CAMERA”
Failed to import Media “I Am Worth Loving Wallpaper”
Failed to import Media “Image Alignment 150x150”
Failed to import Media “Image Alignment 300x200”
Failed to import Media “Image Alignment 580x300”
Failed to import Media “Image Alignment 1200x4002”
Failed to import Media “Triforce Wallpaper”
Failed to import Media “Unicorn Wallpaper”
Failed to import Media “Eddy - Need (Remix)”
Failed to import Media “Horizontal Featured Image”
Failed to import Media “Vertical Featured Image”
Failed to import Media “Fight Club”
Failed to import Media “Iron Man 2”
Failed to import Media “Man Of Steel”
Failed to import Media “The Amazing Spider Man”
Failed to import Media “The Dark Knight Rises”
Failed to import Media “Static Pages”
Failed to import Media “Captain America”
All done. Have fun!

Remember to update the passwords and roles of imported users.

I started with a clean database and re-installed my theme, but after importing the test data, the Media Uploader no longer works when trying to view media from All Dates. Every folder will display except for July 2011. I've tried waiting several minutes, but it shouldn't take that long?

I'm developing locally on MAMP, if that matters any.

Suggested via email by Christian Zumbrunnen.

After importing I get a hint to not forget to change the passwords and roles of the imported users.

What roles should they have?

Is anything in the test specifically testing against roles and/or rights (private posts)?

If not, this could be a point missing ;-)

Would be great if this users had different roles and posts in the state of "review" there...

We have links to categories, but menu links to the homepage, a date archive, a tag template, etc, would be useful.

Is there or can there be a way to easily delete all imported content from WP Test? It'd be helpful to use on a site in development and just as easily remove it all before launch.

As the shell script is pointing to the file location in the repo instead of the real/raw file contents, it fails hardly.

Plugins like WordPress SEO have the ability to remove the word category from URL of a category slug.

Since some of WP Test's posts and categories have the same slugs, this can cause conflicts.

We should consider changing / renaming category or post slugs to prevent conflicts.

Offer more than just the Twitter embed.

If possible I would like to see wptest.io default to HTTPS, this can be done with CloudFlare.

Reported by a user:

http://wptest.io/demo/post-format-audio/ is broken

Reported via Twitter.

Seems to be an issue with WordPress import / export.

Will either need to discuss with Automattic or work around the issue when WP Test becomes a plugin.