Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post content can be lost if you publish before editor loads images #2926

Closed
roundhill opened this issue Jun 26, 2015 · 5 comments
Closed

Post content can be lost if you publish before editor loads images #2926

roundhill opened this issue Jun 26, 2015 · 5 comments

Comments

@roundhill
Copy link
Contributor

  1. Add a lot of images (I tested with 15) to a new post.
  2. Save the post as a draft.
  3. Edit the post again. Quick! Before the images load in the content area, press Publish.
  4. The post will be uploaded empty, because the app grabs whatever is in the EditText and uploads it (which is nothing because the content loading task hasn't finished yet)

Pretty simple solution would be to just disable the Publish/Save button until the content loading task completes.

@kwonye
Copy link
Contributor

kwonye commented Jul 20, 2015

Slightly related: wordpress-mobile/MediaPicker-Android#25

I cannot repro due to that bug. Will fix that before looking at this.

@kwonye kwonye self-assigned this Jul 20, 2015
@kwonye kwonye modified the milestones: 4.4, 4.3 Jul 21, 2015
@tonyr59h tonyr59h modified the milestones: 4.5, 4.4 Aug 18, 2015
@maxme maxme modified the milestone: 4.5 Sep 21, 2015
@sandymcfadden
Copy link

I just had another report of this happening. Are there any updates to it? I see the last milestone was 4.5

@maxme
Copy link
Contributor

maxme commented Nov 19, 2015

I just had another report of this happening. Are there any updates to it?

The new editor will fix this problem, media will be uploaded when the user adds it to the post and a post can't be published if a media is not fully uploaded.

If this is not a common problem, I think we should wait for the new editor to be released.

@rachelmcr
Copy link
Member

If this is not a common problem, I think we should wait for the new editor to be released.

Agreed. This doesn't seem like a common enough issue to spend time resolving it before the new editor is released.

@daniloercoli
Copy link
Contributor

Closing this ticket, since the "new" (that soon will be called "old" again) editor fixed the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants