On 5/13/2013 5:09 PM, Les Henderson wrote:
Ha. Now I have to research even a basic understanding of presets.
Luckily ShareDraft is by Arthus and Ringmaster, so an update isn't
entirely out of the question.
Sharedraft was designed to allow you to share the draft of a post with
someone (say, have a friend edit it) prior to publication. As a result,
it generates a single hash on a single URL so that you can share that
URL with the intended person for review. I've hacked the plugin a few
times to get it to display non-draft posts regardless of permission, but
it still uses that generated hash. When the hash is out, there's no
calling it back. If someone gets the URL, the post remains available on
that hash until it is deleted. Also, the post is only visible via the
single post page, not within any post listings, because it does not
Sharedraft needs to be updated to work with 0.10 to account for new
FormUI, which uses different controls. I don't know what changes might
be required to account for presets, though I imagine that its
interaction might have something to do with it only affecting draft
posts by default.
Passcode works differently.
Passcode is unfinished, but its intended functionality is to allow a
visitor to specify one or more passcodes which will be cached with a
cookie or in the session, and then used as a substitute for user-based
authentication.
Passcode is designed to work with master. There were recent changes to
the query class that are required for Passcode to work. As a result,
Passcode requires 0.10.
Passcode creates a separate table for the purpose of storing passcodes
that grant entry to specific posts. Different passcodes can be stored
for any single post. The implication is that you can permit one
passcode access to posts 1, 2, and 3, and another passcode access to
posts 3, 4 and 5, allowing some overlap between the two. If a user
supplies both passcodes, then both sets of posts should be available.
Where Sharedraft tries to remove the restriction to show only published
posts when a hash is supplied, Passcode integrates with the parts of the
posts query that deal with the permission system directly. As a result,
if you've supplied a valid passcode, you should see qualifying posts
within any listing that would hold them. This is a significant
difference from Sharedraft, which cannot do this well with its current
architecture.
Perhaps more interestingly, Passcode serves as an adequate model for how
Habari's native permission system can be augmented to account for
external permissions.
Passcode yet needs user-facing UI elements, such that passcodes can be
set on individual posts and users can supply passcodes to reveal those
protected posts. These interface elements are reasonably trivial to add
given the new capabilities of the latest revisions to FormUI. Had I
done that rather than write this email, it would probably be done already.
Sharedraft is not a poor plugin. It can be tuned to get close to what
was originally requested, but it was not intended for that use, nor is
it the most efficient for that purpose. For the purpose it was designed
- sharing a draft post with a friend for review prior to publication -
it succeeds. While it's likely that the plugin will be updated for
0.10, it will likely not be updated to support features more than what
it already supplies.
Hopefully that explanation of the differences between these plugins is
helpful.
Owen
--
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
---
You received this message because you are subscribed to the Google Groups "habari-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
