There wasn't enough excitement about an hp.o series, so this week in tickets is staying on -dev.
Since the last edition: 24 commits, 18 new tickets and 17 closed tickets (2 weeks) The last edition seemed to be a bit more effective, many of the tickets mentioned getting comments, and 6 being closed, including 3 old tickets. Yay! In other news, we've crossed the dubious milestone of 1000 tickets. Are we grown up yet ? #1012 user can't edit only their own profile There isn't a permission for users to edit just their own profile, only to edit all users' profiles. #1011 normal user has permission to restore a deleted (but not forever) entry of a different user Permissions checks need to be added to the undelete plugin. #1010 image silo thumbnails don't update when replaced Overwrite an image with the Habari silo and the thumbnail doesn't get recreated. The Habari silo should probably check if a file already exists when uploading, and remove or recreate associated derivative files. #1008 Post slugs conflicting with directories Naming a post the same as a rewrite rule, such as admin, or a directory, such as user, can conflict. A couple of solutions are discussed. #1007 Add <compatible> field to Pluggable A proposal that the new pluggable XML should include information about what version of Habari the pluggable is compatible with. #1006 Controller::get_full_url() improperly encodes ampersands Ampersands get turned into entities. #1005 lighttpd Error I'm not really sure what this ticket is about. Any lighty users understand it? #1004 Plugin l10n Moving plugins' descriptions into the pluggable XML means they're no longer translatable. Same goes for themes. #1003 FormUI should natively support AJAX It should be easy to submit FormUIs using AJAX. #1002 More keyboard shortcuts The ticket doesn't actually suggest anything concrete, but suggests "more epically awesome keyboard shortcuts, especially on the publish and manage pages." #1000 long content type names do not fit in menu If a content type name is too long, the menu becomes screwed up. #998 Replace tags with a custom taxonomy system We all know this is going to happen, but there may as well be a ticket. The taxonomy system is currently partially implemented. Terms can be added to vocabularies in a hierarchy, but as yet terms cannot be associated with objects and other vocabulary features are not implemented. The subpages plugin in -extras works (though shouldn't be relied upon). Feel free to pitch in! Discuss (here or on the ticket), fix, close, as appropriate. Tickets http://trac.habariproject.org/habari/ticket/1012 http://trac.habariproject.org/habari/ticket/1011 http://trac.habariproject.org/habari/ticket/1010 http://trac.habariproject.org/habari/ticket/1008 http://trac.habariproject.org/habari/ticket/1007 http://trac.habariproject.org/habari/ticket/1006 http://trac.habariproject.org/habari/ticket/1005 http://trac.habariproject.org/habari/ticket/1004 http://trac.habariproject.org/habari/ticket/1003 http://trac.habariproject.org/habari/ticket/1002 http://trac.habariproject.org/habari/ticket/1000 http://trac.habariproject.org/habari/ticket/998 -- Michael C. Harris, School of CS&IT, RMIT University http://twofishcreative.com/michael/blog IRC: michaeltwofish #habari --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
