Updates from Ben Balter Toggle Comment Threads | Keyboard Shortcuts

  • Ben Balter 1:06 pm on August 29, 2011 Permalink | Reply
    Tags:   

    WP Document Revisions – Document Management and Version Control for WordPress 

    Proud to say I have released a stable 1.0 of WP Document Revisions, now available in the WordPress repository.

    For those just tuning in, WP Document Revisions is essentially three things:

    1. document management system (DMS), to track, store, and organize files of any format
    2. collaboration tool to empower teams to collaboratively draft, edit, and refine documents
    3. file hosting solution to publish and securely deliver files to a team, to clients, or to the public
    A brief screencast highlighting some of the top-level functionality through a typical use case is below. More information, including the full list of features and link to a code cookbook with some sample integrations is available on the WP Document Revisions plugin page.

    Questions? Comments? Would love to hear them below, otherwise, be sure to tune in to the IRC chat, this Friday, Sept. 2nd, at 16:00 UTC (Noon Eastern).

     
    • marv51 3:12 pm on August 29, 2011 Permalink | Reply

      Do you have any plans to implement a front end?

      • Benjamin J. Balter 3:18 pm on August 29, 2011 Permalink | Reply

        Yes and no. For a site I’m working on, I’m using a combination of two plugins I wrote for another project, count shortcode which can make a front end to browse documents, especially in coordination with a faceted search widget. Because documents are really posts, many built in WordPress features should work based on the query. You can modify it with a handful of filters or URL changes, e.g., ?post_type=document. Also of note, the code cookbook has an example of how to implement a shortcode of revisions.

  • Ben Balter 8:23 pm on August 23, 2011 Permalink | Reply
    Tags: document revision   

    This Isn’t Goodbye, This is I’ll See You Again Soon… 

    Just pushed the latest “revision” of WP Document Revision into the .org repo (“0.6”).  I’m thinking of this as somewhat of an RC1, and pending any unexpected fires, hope to have a formal 1.0 along with a screencast and some better documentation in the very near future. Slowly transitioning the GSOC repo to end of life, so if you’re playing the home game, be sure to check .org for updates.

    Please feel free to install the plugin (all indications suggest that its mature and stable), and let me know your thoughts. I have been configuring WordPress as a document management system for an academic publication, and have even surprised myself at how customizable it is (adding additional fields, changing the word “document” to “article”, fine tuning permissions, etc.).

    It goes without saying, that none of this would be possible without the sage wisdom of the WP Document Revisions mentoring team. Special thanks to Mitcho, Jorbin, Duck_, and Nacin for their invaluable guidance, knowledge, and insight. I would also like to thank the WordPress community more broadly for the both the opportunity to give back and for the constant feedback and support throughout the summer.

    Thanks for the memories, and rest assured that this is just the beginning, not the end.

     

     

     
    • Jon Cave 8:31 pm on August 23, 2011 Permalink | Reply

      Since this is GoogleSoC I’m surprised at how quickly this project is out of beta! 😉

      Thanks for the hard work. Great job!

  • Ben Balter 9:41 pm on August 15, 2011 Permalink | Reply
    Tags: ,   

    ….annnndddddd Pencils down!

    Things are just about wrapped up. Been getting some great feedback from the community this past week, and have been meeting with some security folks to discuss some of the more customized features enterprise and government deployments may be looking for down the line. Have a few small tweaks to the readme still on my plate, but by-and-large, should be a solid 1.0 when formally released.

    After / along-side evaluations, would love to put together somewhat of a “code cookbook” with examples of how to extend the plugin to your particular environment (audit log, state-level permissions, etc.), and need to reconcile a few things with 3.3’s new file upload functionality prior to 3.3’s launch — both beyond scope, and looking forward to final code review in the weeks to come.

     
  • Ben Balter 12:57 pm on August 8, 2011 Permalink | Reply
    Tags: ,   

    Been getting lots of great feedback from the community and just pushed the 8th “revision” into the Plugin Repository (nearly 350 downloads of the beta to date!). The project is ahead of schedule and in a good, stable place — just testing and waiting on feedback at this point. Have a big deliverable due in a few weeks, and have been using WP Document Revisions to track its progress and to get a first-hand feel for how things work in the wild.
    A handful of minor fixes and enhancements this week to clear out the bulk of the backlog:
    • Removed “Private:” and “Protected” from feed titles
    • Fixed bug where all RSS feed entries would link to the post rather than the particular revision
    • Fixed bug where revision summaries on RSS feed were not accurate
    • Removed “Continue Reading…” from RSS feed excerpts
    • Better permission checks on revision downloading
    • Fixed deprecated notice
    • Added a custom post type icon
    • Fixed live timestamp formatting / i18n
     
  • Ben Balter 12:02 pm on August 1, 2011 Permalink | Reply
    Tags: ,   

    Right now, just a handful of small fixes left on the backlog. This week saw a bunch of tweaks to the user interface and experience:

    UI/UX Improvements

    Code fixes and cleanup

     
    • Kyle Goleno 5:19 pm on August 1, 2011 Permalink | Reply

      Whatever you did fixed part of my problem from the previous version. Before all my posts in my blog were giving 404 errors, including when I tried to view documents added through the plugin.
      Now the documents added through the plugin work!
      And all my previous entered posts show up, but NOW any new post on my blog shows up as a 404 error.

      • Benjamin J. Balter 6:14 pm on August 1, 2011 Permalink | Reply

        Found the mistake and will push the change into the wordpress.org repo shortly. In the mean time, the GSoC SVN should be working. Sorry for the trouble, but thanks for the feedback! (Diff)

    • Erlend 3:33 pm on August 2, 2011 Permalink | Reply

      You might want to have a chat with Ron at WPMUtutorials.com, who just released this plugin:
      http://wpmututorials.com/plugins/document-repository

      • Benjamin J. Balter 8:11 pm on August 3, 2011 Permalink | Reply

        Interesting. Thanks for pointing that out. Seems like the projects are a bit different, but will be sure to reach out.

    • onlybmd 5:25 pm on August 3, 2011 Permalink | Reply

      Great plugin, but I cannot download any files I originally uploaded. Should the permalinks be set a certain way?

      • Benjamin J. Balter 8:04 pm on August 3, 2011 Permalink | Reply

        Sorry to hear you’re having trouble. It should be working. What’s your current permalink structure? What do you see when you try? (also, latest version?)

  • Ben Balter 4:45 pm on July 25, 2011 Permalink | Reply
    Tags: ,   

    Closed 16 tickets this week, leaving just about 24 tickets to go:
    • Disabled the submit button until a file is uploaded
    • Mapped capabilities to a new permission type {action}_document to allow greater control of capabilities
    • Removed the hidden content editor and replaced it with a hidden input field
    • Ported human_time_diff to javscript so timestamps update as page remains open
    • Filtered document attachments from media lists
    • Significant overhaul to the autosave ping and file lock
    • Changing document upload directory now verifies the directory exists and attempts to create it if not
    • Changing document upload directory provides a warning that it will 404 documents
    • Admin class no longer extends parent class
    • Internationalization fixes
    • Fixed bug where revision log would not properly display
    • Fixed bug where the post-upload javascript would fire twice on non-flash upload
    • Fixed bug where private drafts were impossible
     
  • Ben Balter 1:32 am on July 18, 2011 Permalink | Reply
    Tags: ,   

    Had a great strategy chat last Wednesday with the mentors three to answer some big-picture questions and map out the second half of the summer as they provided some very, very helpful feedback through a deep-code review.

    Added WP Document Revisions to the WordPress.org Plugin Repository to gain some additional community feedback and it’s already been downloaded 150 times.

    Beyond that, lots of changes this week (69 to be exact!):

    • Cleaned up HTML 5 Notifications code
    • Cleaned up on-screen notification text
    • Cleaned up formatting on the document edit screen
    • Performance improvements on some helper functions
    • I18n Fixes
    • W h i t e s p a c e  i m p r o v e m e n t s
    • Feed authentication improvements
    • UI/UX enhancements
    The full list of this week’s successes is available on trac.
     
    • Erlend 6:47 pm on July 19, 2011 Permalink | Reply

      Your plugin has a very impressive interface, which also goes a long way to explain in great detail what it actually does. Please add some to the plugin entry 🙂

  • Ben Balter 12:51 pm on July 11, 2011 Permalink | Reply
    Tags: ,   

    Extremely productive week over here at document revision central:
    This week is the midterm evaluation and I am looking to get lots of great feedback from mentors and community alike. There’s a small handful of bugs on the backlog, but everything should be working and I encourage you to download the plugin and try things out.
     
  • Ben Balter 11:05 am on July 4, 2011 Permalink | Reply
    Tags: ,   

    It took a bit of getting into the javascript weeds, but file locking is up and running. While a user has the edit-document screen open, the standard autosave ping serves to maintain a file lock. Other users are alerted that the document is being edited, and can view, but cannot edit the document. The lock can also be overridden and the editing user is alerted that they lost their file lock.
    This week I also matured the plugin’s approach to javascript and was able to tackle a bit of low-hanging fruit.
    • Moved JavaScript from inline JS stuffed awkwardly into metaboxes to a separate file and created dev and minified versions
    • Linked JavaScript to jQuery events (rather than calling directly)
    • Fixed feed authentication
    • Fixed post-upload javascript to close the iframe and store the attachment ID
    • Fixed a handful of deprecated notices and E_NOTICE level warnings
    Next week marks the midterm and the end (in theory) of new feature development. The second half of the summer, per the project schedule, will involve thoroughly kicking the tires and further refining the past few weeks work. I look forward to hearing my mentor’s continued feedback, and the community’s thoughts.
     
  • Ben Balter 11:23 pm on June 27, 2011 Permalink | Reply
    Tags: ,   

    Things are finally starting to come together (see screenshot below of the document edit screen). The core functionality is in place and working, the biggest task from here out is mainly crossing T’s and dotting I’s.
    This week’s task was basic workflow support to allow for rudimentary document management. I tried an initial pass with register_post_status but quickly realized that the powers that be decided to hard-code the publish metabox (thus requiring significant re-invention of the wheel) and added a quick custom taxonomy and many API hooks instead. This freed some time up to tackle a handful of outstanding items from the backlog:
    Next week, the final week before the mid-term will build on this week’s progress and (hopefully) usher in file locking based on WordPress’s built-in auto-save ping.


     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel