Call for Testing: WordPress for Android 14.8

WordPress for Android version 14.8-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. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

To test with an apk, you can download wpandroid-14.8-rc-1-universal.apk.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, 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 room on Slack, or head straight GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. and open an issue—please see “Where to Report” below.

Release Notes

  • Added reblog functionality
  • BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor: You can now crop, zoom in/out and rotate images from the device that are being inserted in a post.
  • Block editor: New block: Buttons. From now you’ll be able to add the individual Button block, only inside the Buttons block
  • Block editor: Fix bug where buttons in page templates were not rendering correctly on web
  • Block editor: Add support for upload options in Cover block
  • Block editor: Fix bug where whitespaces at start of text blocks were being removed
  • Block editor: Prefill caption for image blocks when available on the Media library
  • Block editor: Fix titles in the media picker
  • Block editor: Floating toolbar, previously located above nested blocks, is now placed at the top of the screen
  • Block editor: Fix the icons in FloatingToolbar on RTL mode
  • Block editor: Add alignment options for heading block
  • Block editor: Update quote block to visually reflect selected alignment

What to Test

To prepare:

  • Go to Account > App Settings > Privacy settings and turn on the “Collect information” and “Crash reports” options.
  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.
  • Switch to Dark Theme when testing Android 9.0+ devices for this release. On the device, go to Settings > Display > Advanced > Device theme and choose “Dark”.
  • If you are comfortable testing in a language other than English, please test in that language.

To test:

  1. 11800 Go to the Reader and test the reblog functionality on posts with and without 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..
    1. Test reblogging from an account with many sites, verify the site picker is presented and works as expected.
    2. Test from a An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. and a Jetpack site.
    3. Test reblogging from an account with only one site.
    4. Test reblogging from an account with no sites.
    5. Verify the reblog button is not available for posts on private sites.
  2. 11742 Create a new post or page, add an image, verify you can crop, zoom in/out, and rotate images from the device that are being inserted in a post. Note: related updates are listed under the Media Editing label.
  3. 1933 Create a new post or page and add the Buttons block. Complete the 22 test cases for the Buttons block.
  4. 1933 Try to think of a scenario that would break the buttons block and test it out. For example, try adding and removing buttons successively.
  5. 2190 Create a new page, apply one of the page templates (about, blog, portfolio, services, team), make some edits, publish the page, verify the button block from the page looks correct on the web.
  6. 2174 Create a new post, add a Cover block, test each of the upload options (Choose from device, Take a Photo, Take a Video, WordPress Media Library, Free Photo Library, Other Apps), and make sure each option works as expected.
  7. 2127 Create a new post, add a paragraph block, type some spaces, then tap the toolbar bold button and verify the cursor stays in place.
  8. 2127 Create a new post, add a paragraph or verse or pre-formatted block, type some spaces and then text, highlight the text portion, tap any of the formatting options on the menu at the bottom of the editor area, verify the whitespace does not get removed. Compare this to the web editor, does it work the same way?
  9. 2156 Go to Media, upload an image, and save a caption for that image. Create a new post, add the image from before, verify that if there was a caption saved in the media library that it is pre-filled when that image is added in the editor.
  10. 11757 Open a post or page in the editor and complete the 4 test cases noted in 11757 to verify the titles in the media picker are correct for each scenario.
  11. 2118 Create a post or page, add a block that allows nested blocks (Columns, Buttons, Media & Text), navigate through the nested blocks and verify the FloatingToolbar is rendered on top of the screen on Android and that the Navigate-Up button is clickable.
  12. 2118 Open a post or page that contains a block with nested blocks and verify the icons in FloatingToolbar are correct for RTL mode.
  13. 2006 Create a new post; add heading, paragraph, pullquote, verse, and quote blocks, change the alignment for each, publish the post, verify the alignments look correct in the editor, Reader, and web.

If you are able to complete the entire list above, please continue testing by looking at all the related PRs targeting WordPress-Android 14.8 and gutenberg-mobile 1.27, specifically any that you are able to and that aren’t already represented above.

Where to Report

  • WordPress-Android on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Instructions for Reporting Issues

  • Search the GitHub repository first to see if the bug is a known issue.
  • For known issues, please leave a comment on the issue saying you were able to replicate the problem and include device name, iOSiOS The operating system used on iPhones and iPads. version, app version, and type of site you used for testing.
  • For new issues, please follow the template GitHub repository that shows up when creating a new issue.
  • Please be aware that a bot will ask for labels but you won’t have rights to add them. Know that labels will be added by someone on the triage team. 👍
  • If you would like to send Activity Logs to help with debugging (this can be very useful!), you should first trigger the bug and then go to Profile > Help & Support > Application log and use the copy icon at top right to copy the logs. Next, go to Help & Support > Contact us, add a short note mentioning the bug report link, and paste the logs below the note. Please be aware that the Application log may contain tokens which should not be shared publicly, and that’s why logs should be sent through the Contact us form.

Thanks for testing! ❤️

#14-8, #android, #call-for-testing, #mobile