Call for testing: WordPress for Android 11.7

WordPress for Android version 11.7-rc-1 is available for testing on the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. channel.

What to Test:

What’s New:

  • Blog Posts: Added a dialog to help you fix a post with different web and local changes.
  • Site Pages: Refreshed page list layout that includes a timestamp and a featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. thumbnail.

What’s Fixed:

  • We have made lots of small improvements to the stats section including fixing a crash and some visual tweaks.
  • Fixed a bug that could cause some old saved posts to disappear.
  • Fixed a crash that could happen when opening the Media section in the app.
  • There were a lot of other improvements made in this release that aren’t being called out in this post. For the main WordPress Android application you can view the entire list here.

Testing Notes

You can use these guidelines for testing the new blog posts dialog when there are different web and local changes to a post:

Test 1: Confirm the post shows a conflict when there are different local and remote changes

  1. Create and save a draft while online in the app. (This also syncs the draft remotely.)
  2. Go offline.
  3. Make changes to the post and go back. This will save the changes as local draft.
  4. Go to the web and make changes to the post.
  5. Publish the post.
  6. Back in the app, you should be on the posts list. Turn airplane mode off.
  7. Pull to refresh.
  8. You should see now the post has a “Conflicted” state.

Test 2: Keep the local changes

  1. Follow steps 1 to 8 above to create a conflict.
  2. Try to resolve the conflict so that the changing you made in the app are preserved.

Test 3: Keep the remote changes

  1. Follow steps 1 to 8 above to create a conflict.
  2. Try to resolve the conflict so that the changing you made on the web are preserved.


  • Did the three tests have the expected results?
  • Could you tell what was wrong (did the “Conflicted” status make sense) when viewing the post in the posts list?
  • Was the process to resolve the conflict (either to keep your local changes or your remote changes) intuitive?

Bugs & Feedback

Did you find a bug or come up with a feature request while testing? You can discuss it here, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” one of us in the #mobile Slack room or head straight to the Android GitHub repository and open a new issue.

Thanks for testing!