GithubHelp home page GithubHelp logo

Comments (2)

azul avatar azul commented on August 15, 2024

We used to have something similar for gallery pages. You could have the same image displayed on multiple galleries. Turns out it's a mess for permissions:
What if an asset is shared from a page with one set of permissions to a page with a different set of permissions? Well it should probably show up on both pages for all users that have access to each of the pages. Not so hard, right?
Well... fetching the page and fetching the thumbnail or the attachment itself are two distinct requests. So for the second request we need to check if the asset is attached to any page the user has access to. Determining the access to a single page is quite complex all by itself. You can have access because the page has been shared with a committee of a network one of your groups is in.
So we decided that pages determine access permissions. Everything that is access restricted can only be on a single page.

So I am open to copying or moving assets from one page to another. However copying would effectively create a new asset with the same content rather than sharing the same asset between the pages. I'd rather waste disc space than deal with increasing the complexity of our permission system.

from crabgrass-core.

fabacab avatar fabacab commented on August 15, 2024

So I am open to copying or moving assets from one page to another. However copying would effectively create a new asset with the same content rather than sharing the same asset between the pages. I'd rather waste disc space than deal with increasing the complexity of our permission system.

That makes sense to me.

The simplest use case for this is just wiki gardening: I want to move Asset 1 attached from Page A to Page B where both Page A and Page B are within the same group. Currently, doing this is a somewhat involved process:

  1. Locate Asset 1 on Page A.
  2. Download/copy Asset 1.
  3. Go to Page B.
  4. Upload local copy of Asset 1 to Page B, creating Asset 2.
  5. Return to Page A.
  6. Delete Asset 1 from Page A.

If the only thing that happens is a convenience button to perform these steps for me, we can call it "Move asset to another page" for instance, I would be happy. :) In this case, nothing about the logic to determine access permissions for the asset would need to change.

Does that sound feasible?

from crabgrass-core.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.