Publishing an empty post is allowed

[SoapOperaTester]

Expected behavior

The system should prevent publishing an empty post or prompt the user to add content before publishing.

Actual behavior

The empty post is published.

Steps to reproduce the behavior

1. Click the 'Create a post or page' icon
2. Click the 'Blog post' button
3. Click the 'Body' section without typing anything
4. Click the 'PUBLISH' button

Tested on [device], Android [version], JPAndroid / WPAndroid [version]

Galaxy S21 5G, Android 12, Jetpack 25.2.1 (1444)/WordPress 25.2.1 (1444)

Screen_recording.mp4

[dangermattic]

Thanks for reporting! 👍

[SoapOperaTester]

@nbradbury Sorry, could you please clarify why this issue was closed directly? Is it not a bug?

[nbradbury]

@BSIAssist We received a flurry of issues from you that seemed to be reported too quickly to have been submitted by an actual person.

The same occurred from another account, which like you only belongs to the "BugRewriting" repo.

Based on this info we assumed the issues were being submitted by a bot.

[SoapOperaTester]

Sorry for any confusion!

Another account is also mine.

I conducted extensive exploratory testing in WordPress to identify bugs and areas for enhancement to try to help improve the amazing app.

I chose to report all the bugs at once to save time.

The issues were documented personally, not by a bot. Given the time invested in both testing and screen recording, could you please review these issues instead of just closing them?

Thank you!

[nbradbury]

@BSIAssist Apologies if that was the case, it really did seem that the issues were being filed by a bot!

Could I ask, though, why the issues were filed from two separate accounts that belong to a single GitHub repo, and a simple summary of what the BugRewriting repo is about?

[SoapOperaTester]

I apologize for any confusion caused and understand how it might have seemed unusual.

I used two accounts to report issues to prevent any misinterpretation that these reports might be from a bot, but I now realize this approach was counterproductive. 😭

The BugRewriting repo was created to assist with rewriting bug summaries. I noticed that crafting concise and effective summaries is challenging for bug reporters, and developers often spend time rewriting them. The repo aimed to develop a tool to help generate clear and useful summaries based on bug descriptions. However, with the advancement of LLMs, tools like ChatGPT have largely taken over this role.

These issues were documented personally by me and are unrelated to the BugRewriting repo. I hope you can review these issues, as I believe the bugs I identified could contribute to improving WordPress.

Sorry again for the confusion, and thank you for your understanding!

[nbradbury]

@BSIAssist Thank you for the explanation, and thank you especially for submitting so many detailed issues. I will reopen them! 🙇

[SoapOperaTester]

Thank you for your understanding and for taking the time to address the issue I caused.

I really appreciate your willingness to reopen the reports. I’m happy to contribute to improving WordPress in any way I can.

If there’s anything else you need from me, just let me know! 😊