wordpress-mobile / wordpress-mobile/AztecEditor-iOS

Adding images to a Gutenberg post can break blocks.

Open
#1,110 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Bug
Dominant language
Swift
Stars
669
Forks
153
Avg merge
11h 27m
Merged PRs (30d)
4

Description

Description:

Adding images to a Gutenberg post through Aztec can break their containing blocks, causing images not to render properly when reopening the post in the web (Gutenberg) editor.

Details:

Original report:

User was concerned that their images were not being uploaded from the iOS app because they were showing up in the Blocks Editor as ‘Invalid Blocks’. Manually converting to ‘Classic Editor’ blocks resolved this, but was time consuming.

I was able to see the invalid blocks when I SSO’s into their site. I have not been able to reproduce this issue with an Android Phone.

I was able to reproduce these issues with iOS: the issue comes up when the image is added to a Gutenberg block type that doesn't really support images.

An interesting note is that Android seems not to have issues with images, so we should figure out what it does differently in this scenario, since Gutenberg-block compatibility is very limited in Aztec for both platforms.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by reproducing the issue in the iOS Aztec editor by adding an image to a Gutenberg block type that does not support images, then compare the resulting content with Android's behavior. Done means the affected block reopens as a valid Gutenberg block and the image renders correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.