We’ve managed to package a bit more than expected into the release that’s just about ready, so we’re going to christen it 2.1 on Matt M.’s suggestion. Swipe to delete, HTTP authentication, and the requisite bugfixes should make a pretty solid point release.
Recent Updates RSS Toggle Comment Threads | Keyboard Shortcuts
-
MT
-
MT
Holding off on submitting until we’re sure we’ve got the final issue sorted out with deleting pages on 2.9/wpcom. The delay may give us time to incorporate our first patch! Going to review jeffstieler’s patch for HTTP authentication after he’s had a chance to upload the files tomorrow.
-
MT
We’re very close to closing the final ticket for version 2.0.1. http://iphone.trac.wordpress.org/milestone/2.0.1
We should be on track to submit 2.0.1 to the App Store sometime tomorrow.
-
John Bickerstaff
I think we’re there… Found a similar issue with Pages (have to delete twice on WPCOM) MT and Joseph are aware… Once that’s done, we can probably release.
-
-
MT
John’s managed to get a fix for the link helper ticket 274 ready for the 2.0.1 release. Thanks John!
-
John Bickerstaff
You bet… That one was interesting! Will have the other two asap…
-
John Bickerstaff
one down, one to go…
-
-
MT
I’ve tagged 1.3.1, a minor maintenance update to the 1.3 branch. This update will not be necessary for anyone who has upgraded to 2.0. The primary function of this release will be an in-app notification directing the user to download 2.0 from the App Store. We’ll have our contractor build this and submit to Apple later this week.
-
MT
The build was successfully submitted, after leaping over one last version number headache with the 1.x branch.
-
-
MT
I’ve organized Trac tickets a bit; removed the somewhat-vague “next release” milestone in favor of 2.0.1, 2.0.2, and 2.1. All major tickets we’ve identified for the “next release” are now assigned to 2.1. Small stuff we’re tackling now is 2.0.1, and 2.0.2 is for the small things we’d like to address before 2.1 but won’t be ready within the next week or so.
I’ve tentatively scheduled 2.0.1 as being “due” at the end of this week, but that will depend on our success in addressing the 2.9/wpcom-related delete issue.
@jb62 — do you think ticket #274 would be a good candidate for 2.0.1 or 2.0.2? Seems like it should be a relatively small issue, possibly fixable while we’re waiting on more info regarding the delete issue.
-
John Bickerstaff
@MT,
Let me poke around a bit on #274 – I’ll post back in a bit.Also, I just fixed the rotation thing for comments…
-
-
MT
Testing a new swipe-to-delete gesture for posts and pages that John’s added to trunk. Working well so far, except for a small issue with wpcom blogs. Happy to have this one added soon.
-
John Bickerstaff
We can go two ways here…
If modifying wpcom blogs is troublesome, I can put in code to recognize when it’s wpcom and “delete twice” — that would prevent us from having to wait. Of course, it would generate errors once wpcom behaves differently…
Just putting the option out there in case it’s helpful in terms of getting us to a release – then we could coordinate the change to wpcom for the next release and change the code back…
Or, second way would be to modify wpcom now and wait for that before rolling swipe-to-delete into app…
Thoughts anyone?
-
Raanan Bar-Cohen
would prefer to have it work right and fix whatever wp.com issue is out there
-
John Bickerstaff
Right – will do. Joseph and I exchanging data to pin it down… I’ve just created a list of steps to reproduce and e-mailed so Joseph can test my logic…
-
MT
Just occurred to me that the double-delete issue could be related to the new trash feature in 2.9, that’s also been rolled out on wpcom. Sure enough, the same issue exists on my self-hosted 2.9 blog. We probably need to think through how we’ll handle the trash, anyway. Will we be able to move posts into, browse, and move posts out of, the server-side trash from the app? That’d be pretty useful.
-
John Bickerstaff
You were right! Joseph did some magic and all is well… Swipe-to-delete works on one swipe now.
If the trash functionality has an XMLRPC “handle” there’s no reason we couldn’t do that… it’s all just bits with labels… We could even add a “Trash” selection to the list that includes “Local Draft” and “Publish” and display them there…
-
-
-
-
John Bickerstaff
@MT – just committed a change that makes the crash go away in “distribution mode”… Hopefully we’re good to go on swipe-to-delete now…
-
MT
Working now. I’ve commented on the ticket with a few usability suggestions for what happens after you’ve tapped “delete.” http://iphone.trac.wordpress.org/ticket/163#comment:15
-
-
-
MT
I’ve created the first ticket for 2.0.1; John’s working on adding the commenter email address to the comment detail view. http://iphone.trac.wordpress.org/ticket/273
-
John Bickerstaff
Last night, committed code for the Comment Edit page. It now displays the e-mail. Will next address the comments list as I see by Matt’s comment that we want to show e-mail there too…
-
MT
Thanks, John. I’ve checked in r658, which straightens up the display of the commenter URL and address just a bit.
-
John Bickerstaff
Nice – thanks!
-
-
-
-
MT
I’ve been directing support requests to the forums instead of approving them in blog comments; when you have time please peruse the forums to see if there are any questions you can answer. There’s only one so far; it’s about our pal XML-RPC.
-
MT
The FAQ could use a bit of editing probably; John, if you could look at the XML-RPC information and see if it should be updated, I can edit the page.
-
John Bickerstaff
Will do…
-
John Bickerstaff
Just looked this over – it’s good from an XMLRPC perspective.
NSXMLParserErrorDomain error (some number) is a different matter and seems to resolve to broken XML coming back in the response to an XMLRPC call… for example when a certain user’s site had XML-illegal characters within the text of a few comments.
This should probably get it’s own trouble-shooting write-up — although it’s complex and I think the whole write up should probably go as a sticky post on the troubleshooting forum, to which we can link from a simpler explanation in the FAQ…
I’ll kick that out in the next few days and ping you with the text…
-
MT
Sounds good. It may make the most sense to go ahead and compile documentation as a set of pages on the iphone.wordpress.org site. We can organize them easily, and they can be searchable right from the homepage.
-
John Bickerstaff
OK, when I’ve got content I’ll run it past you… Do I have permission to post pages there?
-
-
John Bickerstaff
One of the things necessary for this little troubleshooting recipie to work is an HTTP Client type tool. There is a great one for Mac, but I cannot find a similar tool for Windows… Does anyone know of one? I’d like to suggest one for Windows users – otherwise the troubleshooting is only good for Mac users…
-
-
John Bickerstaff, and 
John Bickerstaff 6:12 pm on November 19, 2009 Permalink |
I’m getting errors when attempting to apply the patch – both in my SmartSVN GUI tool and the command line… @MT were you able to apply the patch?
MT 6:25 pm on November 19, 2009 Permalink |
It was a little tricky but once I got all the files in place, I was able to build. I’m setting up a test blog right now.
MT 9:12 pm on November 19, 2009 Permalink |
The functionality works well, so I’ve replied with a few usability suggestions. It’ll be great to get this in.
John Bickerstaff 6:25 pm on November 20, 2009 Permalink |
Big thanks to jeffstieler for the http auth code!