These forums are provided for community interactions only. For official support please submit a support ticket.
You are not logged in.
G'day
Still kicking the tires on Hosted Director - we're very excited about it's ability to be used for slideshow content management.
One key is the ability to have "Editors" and "Contributors" - this really opens up the content management possibilities.
One critical issue is how to restrict a Contributors access to some slideshows - many hands make for many broken things and a content managed solution needs to allow "permission control" .
The goal is to have multiple contributors that can of course post to their slideshows or galleries but not mess with others.
How is this achieved with the hosted Director setup?
Thanks in advance,
Thomas
Offline
Currently, it is not possible to restrict users in the way you describe in either version of Director.
Offline
bdaily wrote:
Currently, it is not possible to restrict users in the way you describe in either version of Director.
G'day Brad,
Thanks for your quick reply.
I assume you guys see the urgent need for such flexibility? This is sort of a deal-breaker for professional application of multi-contributor slideshow publishing - efforts that would otherwise oh-so easy to do now with your hosted solution.
Can you say anything about plans for such a feature? Definitely coming "sometime"? Definitely not coming ever? [I'd guess you would be unable to comment]
If you have a FR topic area I'll go post something there - otherwise please consider this a fully fledged feature request.
Bummed that my SSP plans may be scuttled,
Thomas
Offline
G'day again Brad,
Seems I'm not the only one urgently looking for basic permission control?
http://forums.slideshowpro.net/viewtopic.php?pid=33747
Thanks for your support,
Thomas
Offline
Thomas - We've certainly had this requested before, but those who have requested it comprise a fairly small percentage of our user base. I'd guess that 95% of our users (or more) either use Director alone or in a small team where permissions of this nature aren't necessary.
That's not to say we won't do it in the future, but for now we are focused on some features we think will have a greater impact on the user base as a whole.
Offline
bdaily wrote:
Thomas - We've certainly had this requested before, but those who have requested it comprise a fairly small percentage of our user base. I'd guess that 95% of our users (or more) either use Director alone or in a small team where permissions of this nature aren't necessary.
That's not to say we won't do it in the future, but for now we are focused on some features we think will have a greater impact on the user base as a whole.
Brad,
Thanks for your reply mate. It is clear you guys support your products.
I'm sure you know the demographics of your customers much better than I do but I also assume you are looking to add new types of customers to your user base? I assume that DDI is looking to expand business and not keep the user base static?
If it is true that Director is intentionally limited and not meant for use by anything bigger than a "small team", and you don't offer permission control, then why have the "Contributor vs Admin" user roles at all?
Even within a small team people will have different levels of skill, knowledge, and responsibility and after months or years of publishing there could literally be $10's or even $100's of thousands of dollars worth of (wo)man-hours invested in setting up the content and slideshows?
Your system appears to treat every "Contributor" exactly the same - appears to trust them all the same - appears to allow each and every one of them to cause system-wide damage if they make a mistake?
Apologies, but to me, this seems absurd and surprising? From my humble perspective digital content management is all about controlling content contributors with robust permissions?
Thanks for listening.
Thomas
Offline
cve55au wrote:
I'm sure you know the demographics of your customers much better than I do but I also assume you are looking to add new types of customers to your user base? I assume that DDI is looking to expand business and not keep the user base static?
Of course we want to grow our business, but I don't necessarily subscribe to the "be all things to all people" mentality. We want to make a really good product that is attractive to a certain set of users rather than making a mediocre product that is attractive to everyone. If we lose some people while Director doesn't have robust permissions, so be it. We're two developers with only a certain amount of time in the day, so like I said before we are focusing on some features for the near future that will serve our user base as a whole more than user permissions.
If it is true that Director is intentionally limited and not meant for use by anything bigger than a "small team", and you don't offer permission control, then why have the "Contributor vs Admin" user roles at all?
Administrators are the only ones who can assign new users access and also the only ones who can access the preferences pane. Both of those areas are quite important in maintaining control over the install.
Even within a small team people will have different levels of skill, knowledge, and responsibility and after months or years of publishing there could literally be $10's or even $100's of thousands of dollars worth of (wo)man-hours invested in setting up the content and slideshows?
Your system appears to treat every "Contributor" exactly the same - appears to trust them all the same - appears to allow each and every one of them to cause system-wide damage if they make a mistake?
Like I said, I'm aware of situations where more robust permissions are needed.
Apologies, but to me, this seems absurd and surprising?
It just seems that way.
From my humble perspective digital content management is all about controlling content contributors with robust permissions?
I tend to think digital content management is about a lot more than that ![]()
Offline
Thanks for the reply Brad,
Thomas
Offline
Hey Brad -
If enough of us threw some cash into a pot to get you to code this functionality in, would you consider it?
continuing over from... http://forums.slideshowpro.net/viewtopic.php?id=5301
cheers,
Scott
Offline
I too find this "perplexing," although "absurd" may be overstating the case a bit. ![]()
I suppose it's just speculating, but didn't you already have to build this type of functionality into the version of the app which you use for the hosted Director service? I fully respect the concept of priorities, and working on some items which people are clambering for is just good business sense. However if this would be a port from that version of the app, I know that there are a lot of us out here who would pay good money for it.
I'm going to take a small amount of hope from the following sentence:
Brad wrote:
If we lose some people while Director doesn't have robust permissions, so be it.
This functionality does really make the difference for me between an app that I can use for my personal sites and an app that I can use professionally.
I sincerely hope that you will reconsider adding this as an option sooner rather than later.
Thanks,
Michael
Offline
pruettsk wrote:
Hey Brad -
If enough of us threw some cash into a pot to get you to code this functionality in, would you consider it?
continuing over from... http://forums.slideshowpro.net/viewtopic.php?id=5301
cheers,
Scott
A constructive idea Scott - I'd certainly look a chipping in given the cost was "reasonable".
IMHO to make this work, and keep the cost reasonable, SSP / DDI would have to consider making an "official call" out to the SSP masses - getting the largest possible list of folks that are willing to pony up for "the rest of us" to all get this functionality.
Personally I think it would be a huge winner . . . and "professional" use of SSP / Director / Hosted Director would move forward as people recognize how slick and good SSP can be for managing web delivery of image content.
Just some thoughts . . .
Offline
cve55au wrote:
A constructive idea Scott - I'd certainly look a chipping in given the cost was "reasonable".
IMHO to make this work, and keep the cost reasonable, SSP / DDI would have to consider making an "official call" out to the SSP masses - getting the largest possible list of folks that are willing to pony up for "the rest of us" to all get this functionality.
Personally I think it would be a huge winner . . . and "professional" use of SSP / Director / Hosted Director would move forward as people recognize how slick and good SSP can be for managing web delivery of image content.
Just some thoughts . . .
The way I look at it is either pony up a couple hundred to pay a programmer an hourly rate to hack it, or grab a handful of people to petition for an official upgrade with some cash on hand. I understand I have little influence with these guys, and their product is their product, but I have no idea why I can set up multiple logins w/ Director, yet everyone basically has equal permissions. All I need is the ability to keep users from deleting/editing contributions from others. It can't be that hard...
I'd be weary of suggesting an "official call" to the masses to collect some dough. That wouldn't look good at all; I'd be appalled if they started asking me for money for developments that I wouldn't utilize.
There's enough opportunity to do this on the forums.
Offline
It's all good Scott,
I've done exactly what you are describing on another platform - and yes it worked well, even if the few paid a relatively high price. (still wasn't much).
Go for it mate.
I also see no reason I can setup multiple logins - but only with the same permissions. Like you, all I want is to keep contributor #1 from editing / deleting contributor #2's content (or mine!).
As you say it sounds straight forward - and if you are right that it is a $200 - $400 job (~$50/hour??? = 4 - 8 hours work???) then we should be able to get individual costs down below $30/each given just the 15 or so posters in the FR thread.
not sure if that is a realistic cost . . . but at that cost I'm certainly in.
Offline
(Moving this thread to the Feature Requests forum]
While I understand your continued interest in this, I stand by my original response. Cash flow is not the issue and users putting up money for development of certain features is not a road we want to go down, as it sets a bad precedent.
Saying "it can't be hard" or "it sounds straightforward" is shortsighted, as you are viewing it from your perspective and your specific needs. For us to implement a feature in Director, we have to make it palatable for tens of thousands of users, which I can assure you is neither easy or straightforward.
What would be more constructive would be to lay out exactly what kind of permissions you are seeking. Include "stories", like "Bill should only edit albums that he uploads". That might give us a better idea of what people are looking for and we can make a determination on if and when we might start working on this.
Offline
Excellent, I can do that, thank you for the suggestion.
The functionality that I would like to see would be that there would be essentially a "super-admin" user that could create spaces which would act like individual Director installations with their own admin/contributor/editor, etc. The super-admin would be able to create these new spaces and create an admin user for the space. The other users would only have permissions within that space.
The super-admin would also have the ability to view and control content across all the spaces.
I'm sure others have use for other types of granular user permissions, but for me this is all that is necessary. This would allow me to have only one install of Director on my server which services all of my clients and all of their slideshows while allowing easy upgrades of the whole system.
Basically what I'm thinking of is a kind of Director MU (after Wordpress MU, which is what I use to control the sites on my server).
Offline
Brad,
Thanks for the reply and thanks for listening.
Let me add something here that may be missing or misunderstood in this discussion.
From my POV (and I'm sure many others) SSP & SSP D is a valued product set - one that you guys obviously put alot of hard and good work into. It shows from my POV - that is why I hope to continue to use it. I love it.
My attempts to discuss with you and my fellow SSP customers my personal needs for more features doesn't negate my core positive impression of the SSP product set. Just for the record.
Now:
In terms of what I meant by "permissions" when I started this rant (before noting that others had requested it even before the hosted service started) - All I'd like is to be able to, on a "contributor by contributor" basis, lock down the ability to "make changes" (edit / upload / delete) on an "album by album" or "gallery by gallery" basis. (Then again if albums can belong to more than one gallery then "gallery permissions" may not make sense?)
Maybe the logical extension of this is that those who can't make changes to content in a gallery or in an album can't / don't even "see" those galleries or albums.
This is what I was looking for in the controls / settings when I first started with SSP D. This would ensure that, after months and years of running a SSP D system, that one "less able/smart" contributor can't somehow destroy / delete / mess up $10,000's worth of (wo)man-hours work. The one "dumb" contributor could only mess up what they have been given access to. One album, or a set of albums, for example.
I suppose maybe I'd envision an admin screen where all the contributors are listed down the page and all the galleries or albums (or both) are listed across the page with check-boxes for "access" or "no access".
Thanks again for listening.
Thomas in Tassie
Offline
Thanks for continuing in this discussion Brad.
bdaily wrote:
While I understand your continued interest in this, I stand by my original response. Cash flow is not the issue and users putting up money for development of certain features is not a road we want to go down, as it sets a bad precedent.
Understood, and I agree. I suppose you could chalk up the idea to some of your users seeing tremendous value in such a feature.
Saying "it can't be hard" or "it sounds straightforward" is shortsighted, as you are viewing it from your perspective and your specific needs. For us to implement a feature in Director, we have to make it palatable for tens of thousands of users, which I can assure you is neither easy or straightforward.
Fair enough, but at the same time I wouldn't expect an added feature like this to throw tens of thousands of users for a loop. What is being suggested could easily retain all current capability, even as default.
What would be more constructive would be to lay out exactly what kind of permissions you are seeking. Include "stories", like "Bill should only edit albums that he uploads". That might give us a better idea of what people are looking for and we can make a determination on if and when we might start working on this.
Alright. Here's my situation: I run a small photography business in which some of our coverage is contracted out, yet is directly & almost immediately published on our site(s) by the photographer. Currently it's just myself and one other photographer, so the current Director setup is fine for our immediate needs. However, in '08 we're expanding and signing some other photogs on board in different locations. In a similar sense to what Thomas stated in post #16, I simply can't afford to have one contributer mess up someone else's work, even by non-malicious user error.
I'd actually love to see the exact same implementation as Michael describes in post #15.
cheers,
Scott
Offline
Firstly let me start by saying, Great work... Love SSP Director... Its been a pleasure from installation through to use... Looks great, feel great and works great...
Except... I agree, for me the only thing missing is the ability to add users and give them permissions either at a Gallery and/or album level (Add/edit albums and images in a gallery).
I'd love it if you were to add this to the TOP of your list of things to do.
I can't imagine what else you think is more important, I think everything else works great! :-)
Please please please please :-)
Offline
Hi Brad,
My name is Wayne from New York City and I must say that I agree 100% with all of "Thomas" statements regarding "User Control".
I love the SSP product and I have purchased several SSP Director licenses for many of my cloned web sites nevertheless, I am unable to allow my users to sign up to my site's SSP Photo Gallery because I can't prevent/restrict any users from editing other user's "Galleries" within SSP Director - I don't even want them to have access to other user's galleries.
Yes, SSP Director does not allow Editors to delete Galleries but they can still mess up other user's gallery content by adding photos to it , changing URL's, and text information - which goes totally against having full control of your users as the main Administrator of SSP Director.
If this user restriction control was made available to purchasers of your product - I guarantee that the word would spread even more about your product thus sales would increase....Brad, I am talking out of line with regards to your product sale numbers due to the fact that I am not working in your sales department but as an end user/buyer of your product you should take my word for it.
I will continue to use the product but this limitation is "MAJOR".
Thanks for hearing me out!
Offline
I would like to add my voice to the request.
and basically what I want as a new feature is exactly the same thing as what thomas requested and the reason is also the same.
I want to be able to limit the access of a specific user to a specific gallery / album because I don't want a contributor to mess up the content contributed by somebody else.
It is a major issue for me to the extend that at this time I will sadly stop using SSP and turn to something else where this functionality is present or manageable. and that really does not make me happy because the product is great and I love it. But I just cannot trust a contributor and risk to get all my content screwed up.
L
Offline
I also need the ability to restrict people from editing albums that are not their own.
All of my experience with user access control comes from using Drupal for the past several years.
In Drupal, you can create "Roles" and give permissions to that "Role." Then you assign any number of "Roles" to each "User" as necessary.
Here's what I would like to see in Director:
User 1: (Role = "Administrator)"
User 2: (Role = "ABC Editor")
User 3: (Role = "ABC Contributor")
User 4: (Role = "XYZ Editor")
User 5: (Role = "XYZ Contributor")
User 6: (Role = "ABC Editor", and "XYZ Editor")
Role "Administrator": (Permission to do everything, Contribute to any Album, Edit any Album)
Role "ABC Contributor": (Permission to Contribute to "ABC Album 1" and "ABC Album 2")
Role "ABC Editor": (Permission to Contribute to and Edit "ABC Album 1" and "ABC Album 2")
Role "XYZ Contributor": (Permission to Contribute to "XYZ Album 3" and "XYZ Album 4")
Role "XYZ Editor": (Permission to Contribute to and Edit "XYZ Album 3" and "XYZ Album 4")
Users could be given roles by clicking check boxes on their account page.
New roles could be created as necessary.
Roles could be given the ability to Edit/Contribute to selected Albums by clicking check boxes.
This would provide very flexible and granular access control.
Offline
Here here. I fully agree with doubleedgedpen. Its time for SlideShowPro Director to start working with teams of people not just a few. I reviewed this post and others and it seems like Bradleyboy Productions & Dominey Design might be holding back due to cost restraints.
Like domain mapping, access control is something I am willing to pay extra for. I really need access control to alleviate having to process the incoming content.
In the past I believe this company has queried users concerning usability. If you only query users that are satisfied with the product as it stands, then the product will fail to grow and develop. This software has serious potential. Don't squash the possibilities by failing to add features that will attract new business.
WebDEZN on the Internet
doubleedgedpen wrote:
I also need the ability to restrict people from editing albums that are not their own.
All of my experience with user access control comes from using Drupal for the past several years.
In Drupal, you can create "Roles" and give permissions to that "Role." Then you assign any number of "Roles" to each "User" as necessary.
Here's what I would like to see in Director:
User 1: (Role = "Administrator)"
User 2: (Role = "ABC Editor")
User 3: (Role = "ABC Contributor")
User 4: (Role = "XYZ Editor")
User 5: (Role = "XYZ Contributor")
User 6: (Role = "ABC Editor", and "XYZ Editor")
Role "Administrator": (Permission to do everything, Contribute to any Album, Edit any Album)
Role "ABC Contributor": (Permission to Contribute to "ABC Album 1" and "ABC Album 2")
Role "ABC Editor": (Permission to Contribute to and Edit "ABC Album 1" and "ABC Album 2")
Role "XYZ Contributor": (Permission to Contribute to "XYZ Album 3" and "XYZ Album 4")
Role "XYZ Editor": (Permission to Contribute to and Edit "XYZ Album 3" and "XYZ Album 4")
Users could be given roles by clicking check boxes on their account page.
New roles could be created as necessary.
Roles could be given the ability to Edit/Contribute to selected Albums by clicking check boxes.
This would provide very flexible and granular access control.
Offline
Wow the years go by and no progress on this at all :-(
Ive just read most of this thread.
Brad asked what exact functionality we would like -
I would say that the simplest change to the already existing functionality
that would satisfy my basic needs is this...
Make an new role below editor that can only
add and delete content to one specific album.
Cannot change album or gallery settings.
Cannot affect other users.
Surely this is very easy to implement- no?
By the license for self hosted Director -
am I allowed to post this as a job at rentacoder.com ?
And when I have my adapted code can I share instructions for others
to integrate this mod into their director installs?
If so I see this as a possible solution for those of us who are super keen to
get a members CMS happening.
A side question - is it possible to use Amazons storage for the media that is uploaded to a self hosted Director?
Thanks very much - Dan V
Offline
@njaknjak
- Im glad to see others think this is important still.
SSP Admin - please think again about this.
It could be the way for SSP to go viral!
Someone WILL DO THIS.
Someone will rpovide the very best image and video CMS for communities.
Someone will create an image CMS with complete control over member access.
Do you think they wont find a big market for it?
Do you think they wont become super famous for doing it?
Why cant it be SSP ?
Why cant it start by simply adding a little more control to what is already there?
![]()
Thanks for creating a great program - I hope you dont mind your fans wanting it to be even better !
![]()
Offline
I would like the user to be able to add photos to albums and delete photos, but not be have the ability to delete a whole album. From what I've seen it doesn't seem like those permissions are possible? Please let me know if I'm missing something and it's right in my face.
If it doesn't I would suggest this feature. Thank you for your time ![]()
Offline
I built the request you guys were talking about, and am no programming genius (only been coding 3 years). It is fairly robust.
-only displays recent images, album list, for albums you own
-contributors own one album, can be changed in a dropdown menu by the admin on user screen
-editors own all albums in a given gallery, can create new albums
-users trying to hack the address bar typing in album numbers they do not own get error screen
-hardened security on the login, added blank index.php in the lg folder to keep spiders away
-white label branding and styling of Director with your corporate logos, bigger buttons
-Director styled by device, different stylesheets for tablets, phones, standard
-autodect and add FTP'ed images to all owned albums, so you can update Director from the road (since the Flash updater doesn't work on an iphone/ipad)
I just started programming php a few years ago, inspired by the Director API. If I can do it, so can they. I don't think I could legally sell my modification here, but would be happy to show screen captures to the dev team.
And if not against the terms of use, would entertain freelance offers.
Offline
just want to keep up the request for this feature...
At the very least, I'd love to be able to restrict some users to particular albums.
thanks!
Offline
Add one more. Been needing unique logins per album for a while now. I have a new client with 25 albums, each belonging to a different person and I can't allow all of them access to the same Director install. Please provide a solution to this. Love SSP and Director!
g
Offline