Call url wordpress://newpost (with optional parameters) used to work with the iOS app, taking you to the post editor with title and content pre-filled if passed along.
WordPress app opens, nothing happens.
Place a call in Safari to wordpress://newpost and click "Open" to open in WordPress, observe you are not delivered to the post editor.
iPad 2017 and iPhone 7, 10.3.2 and 10.3.3, WPiOS 8.0 (and a few versions before)
Thanks @ajgraves, we'll be working on this very soon.
@diegoreymendez it looks like you removed this in AppDelegate, do you remember why?
Even more context: https://github.com/wordpress-mobile/WordPress-iOS/pull/2369
The reasons behind the removal of this was:
My personal opinion is that, since a decision was taken to remove the feature, we should evaluate if this is really necessary before accepting the request to add it back.
I know "necessary" is not a very precise term, but we should try to qualify / quantify it somehow.
Any solution? It still doesn't work.
@ajgraves, @mklengel - Could you provide us with more information about how you were using this feature?
iOS's built-in share functionality should supersede this feature. It's currently a bit limited (WPiOS is not coming up in Pages.app's share dialog for instance) but we could definitely improve that.
I am using Drafts on my iPad Pro to write some text which goes via the URL scheme wordpress://newpost to WordPress. It's very annoying that this is not working anymore.
Additionally I have a scrolling problem with WordPress (in Safari) on my iPad Pro aka "WordPress Editor Jump Problem", see here:
https://www.makeuseof.com/tag/ipad-pro-app-problem
https://ditchwalk.com/2015/09/08/wordpress-editor-jump-fix
All in all - very frustrating.
This issue has been marked as stale and will be automatically closed. This happened because:
However, discussion is still welcome! If the issue is still valid, please leave a comment with a brief explanation so the issue can be reopened.
Most helpful comment
Even more context: https://github.com/wordpress-mobile/WordPress-iOS/pull/2369
The reasons behind the removal of this was:
My personal opinion is that, since a decision was taken to remove the feature, we should evaluate if this is really necessary before accepting the request to add it back.
I know "necessary" is not a very precise term, but we should try to qualify / quantify it somehow.