Hey Debra,
I am sorry for the delay of this reply,
(1) when I open the post, I get a very early version of the file. Fortunately, the latest version is in the history list. How do I get the system to actually save the last version of the post so that it's immediately available when I open it. (Never mind, I think I've figured that out - Update Post. I had planned to save this file as a draft but that wasn't working well either.)
I can't replicate this, perhaps you can take a look of my following 2 situation and see is it you referring this:
#1. When I start create a new post, but I didn't click `Apply` and `Publish` button, just click `save for later` then close it the composer. If you want to open back this draft, you have go to draft filter tab (screenshot :
http://screencast.com/t/dYAGWOhQ4orr ) then continue back.
#2. When I start create a new post and click `Apply` or `publish` the post, which mean that this post already publish in your site. If you would like to edit this post and save as draft, you can edit the post > save for later, it will generate a new revision for this level. Then you can click back that `history` tab then select back your draft for that post.
(2) what is the the difference between "Save for Later" and "Apply"?
- Save for later : If the post haven't publish yet, it will save as draft. If the post already published, this functionality will save as another revision, and this revision will not appear on your frontpage.
- Apply : When you click this apply, it will publish the post directly.
(3) when I open the correct, last version of the post from the history tab, if I click on "Use", I get an error - Invalid controller: name='posts', format='' What's up with that? The system bounces me entirely out of Easyblog and I'm back at the Joomla entry screen. BUT, I'm still in a composer screen (creepy).
It seems like that was bug, can you download my file then replace into ->
JoomlaFolder\administrator\components\com_easyblog\controllers\posts.php , it should work fine.
That was good ideas, I will recommend this video tutorial to our documentation team and see if we can improve this in the future.