Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • <blockqoute>In my original post, I was referring to zip file uploads, and having it auto-unzip for us.</blockqoute>

    Auto-unzip is the direction I’m leaning for console uploading but primary support will stil be centered around FTP due to the lack of filesize restrictions … I just don’t like sending large files via HTTP forms.

    the main thing lacking in all of the plugins is the ability to do bulk file uploads via the WP admin panel

    Just to make sure I’m on the same page … you’re talking about uploading around 5-10 files at a time from a web form on the admin? The other option would be support for uploaded zip files.

    One thing I always lament is the lack of support for media files (like movies and Flash content)

    Multiple media types w/ customizable formats are already built into the backend. It comes with a predefined list of mediatypes and a handfull of formats (size & aspects). Each Media record can contain an assortment of images sizes and any number of other files (flash, pdf, video, etc.)

    Just out of curiosity … what features constitute most of the bloat in g2 and coppermine? I avoided both since I already have a working backend … I just need to make it plugin enabled … not to mention presentable (the original version will NEVER see the light of day, it’s embaressing)

    In regards to access rights …
    I’m just using the users/roles that are assigned in wordpress. If you trust someone to update your blog, it’s likely you trust them to update you gallery. No need for a seperate permission system when one’s already in place.

    In regards to protecting images …
    Media Items (images,video, etc.) can be set as public or private. Private media will not show up while browsing through the category index. It will only be visible if explicitly linked from a post, custom sidebar, or group.

    Categories can also be set to Public or Private. Private categories will not show up in an browse index.

    Groups can be set to Public, Private, or Protected. Private groups operate the same as private media and categories. Protected groups are only visible to registered users who have also been granted access to the group or one of the groups parent (if propagation is allowed).

    Restrictions and access will likely be integrated into the data queries so protection will be automatically included into all gallery templates. This would prevent accidentally disabling protection by updating a template.

    I’m using groups to basicly replace tags, albums, and folders. Hopefully it will provide more functionality with less hassle. Adding additional meta-tag support is possible but I “think” that would just over complicate things.

    I’ve got a “very” rough draft from my notes of what I’m considering. Over the weekend I’ll be taking stock of what’s already/needs to be done. I should have a more formal spec then. Until then, feel free to comment on the rough specs or add ideas, I’d love to hear them… keeps me from getting over focused on some mundane detail. I should be setting up a site for the project soon as well. (never enough time.)

    1. primarily a personal/single gallery
    1. having permissions tied to the wp database to allow for several people to maintain the gallery
    1. personal media groups are a possibility [see access control]
    • uploading
    1. mass upload via ftp (inbox)
    2. web interface upload for users
    3. ability to add any file type
    1. configurable list of allowed file types
    1. option to restrict files to certain dimentions/aspect ratios
    2. the list of dimentions/aspects would be used in thumbnail creation as well
    • changable icon sets for non-picture formats [simply replace the standard icons, nothing fancy]
    • optional automatic thumb generation
    1. build down from selected hi-res image (delete original?)
    • bulk edit mode
    1. still working on details/feasability
    • access control
    1. online vs. offline resources
    1. offline will prevent media from being displayed outside the manager console
    • public vs. private images
    1. public media will show up in browseable indices (implied inclusion)
    2. private media will only be visible if explicitly added to a group or post (explicit inclusion)
    • private groups (explicit access)
    1. allows for groups of media with viewing restrictions (p/w protected, client access, etc.)
    2. these could also be used for keeping track of internal resources, i.e. annual banners, etc.
    • standard media record
    1. description (text,bbcode?,html)
    2. caption/excerpt (text)
    3. image size, aspect ratio
    4. creation date
    5. posting date
    • post integration
    1. media browser to insert images in posts (dynamic linking?) [linking is a low priority but the browser would be nice]
    • template based themed gallery pages
    1. main gallery page
    2. category, medium, group index pages
    3. detail pages
    • taxonomy
    1. media item
    1. physical files
    1. size, aspect ratio, filetype
    • category
    1. used to describe what an item represents
    • medium
    1. used to describe how an item was created
    • groups
    1. presentational grouping similar to albums but a little more abstracted as virtual folders (unlimited)
    • note.
    1. categories, mediums, and groups can be hierarchal

    In regards to linking to items from a blog post… Aside from static linking, would there be any need for dynamic linking. What I mean here is that if a change was made in the gallery record, it would show up in the post. If a new thumbnail replaced an older one, the post would show the new image. This would be accomplished via links such as

    <img src="./gallery/image.php?id=xxxx">
    or w /rewrites
    <img src=".gallery/image/xxxxxxx/thumb">
    <img src=".gallery/image/imagename/thumb">

    It’s rather low on my list right now as I’d rather keep things simple and focus elsewhere.

Viewing 6 replies - 1 through 6 (of 6 total)