Asset Listing Permission Restricted Items

(Squiz) #1

Is there a way to publicly asset list a bunch of permission restricted files? I'd like to display a list of files, which prompts the visitor to log in once they click on one.


There only appears to be "read", "write", and "admin" permission options. Is there any way to ignore permissions completely?



Edit:Removed redundant words that were redundant.

(Nic Hubbard) #2

You could use the Link Asset for this, and then list those link assets, but it sounds like a headache to upkeep that unless you use a trigger to create a new link asset each time you create a new file asset.

(Robin Shi) #3

There seems not a neat or simple way to do that. Here is another option. You can remote content the asset listing and put the http authentication in the remote content page. Make sure not to tunnel any links. When the user clicks the file link they are asked to login.

(Squiz) #4

That's a good idea, but I think it's probably overkill for my purposes.


I suppose if the asset listing can't do it out of the box, I've got the choice between that or hard-coding it. It's only going to be about three assets tops per listing and they're not going to change too often, it's just a large number of listings to set up initially.



Thanks for the ideas.

(Nic Hubbard) #5

[quote]
That's a good idea, but I think it's probably overkill for my purposes.



I suppose if the asset listing can't do it out of the box, I've got the choice between that or hard-coding it. It's only going to be about three assets tops per listing and they're not going to change too often, it's just a large number of listings to set up initially.



[/quote]



Well if you decide to hard-code it just create your listing and view it as a logged in user. Then just copy the HTML that it is creating.

(Squiz) #6

Yup, that's the easiest way I think. I already had the paint layout done up, so I'm using Firebug to spit out the html of the content div.


Thanks again for your ideas. :slight_smile:

(Dan Simmons) #7

There's no way to ignore permissions in asset listings, but there is a way to ignore permissions for menu items so you could do a really basic listing using a menu design area…

(Joel Porgand) #8

Would there be any glaring downsides to creating a custom asset the same as the standard asset listing, only adding an "ignore" option for the "Asset Access to List" field (which skips the permission check on the backend)?

(Squiz) #9

[quote]
There's no way to ignore permissions in asset listings, but there is a way to ignore permissions for menu items so you could do a really basic listing using a menu design area…

[/quote]



In order to keep this functionality out of the main design, perhaps something along the lines of this could work:



[list=1]

  • Make a new design with nothing but a menu section to list [i]sibling[/i] assets (perhaps setting wanted_asset_types to restrict the types I don't want).
    [*] Create/clone a data record asset (without a web path) into each folder I want to list, and apply the design.
    [*] Nest the data record asset into each page, ensuring the design gets printed (I think there's an option for this, but I've never used it).

    [s]If that all works out without hitting any bugs/unintended consequences, that might actually be feasible for me. Certainly a lot better than hard-coding everything.[/s]

    Doesn't work this way. You can nest with a paint layout, but not a design without a remote content and a HTTP request, which is just getting stupid. Oh well.

    (For those wondering, I've been recommended in the past by Squiz to keep the size and amount of elements in my design parse file to a minimum, as they can get rather slow. I've already got a two second render time, and as my parse files are shared across multiple sites [only one of which will actually need this customisation] it's a lot safer and economical to simply hard-code everything. :rolleyes:)
    • (Andrew Harris) #10

    I know it’s been 5 years, but has there been any advance on this topic.
    I need to give users a peek at stuff they wouldn’t normally have access to.

    To quote Donald Rumsfeld:
    “But there are also unknown unknowns” … “that tend to be the difficult ones”

    (Peter McLeod) #11

    Hi

    Maybe try something like:

    • a public accessible asset to hold data/content set by a trigger (e.g. metadata or file contents) - the file contents approach might be a bit easier to get working

    • trigger condition could be when your restricted assets are modified

    • the trigger would be set to ignore permissions and act on other assets. It could get the contents of a listing or something else (%globals_asset_contents_…% with permissions ignored) and set to the public asset

    • then use this publicly accessible asset to get the content

    Thanks
    Peter