Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author Access #22

Open
nilshoerrmann opened this issue Aug 29, 2013 · 4 comments
Open

Author Access #22

nilshoerrmann opened this issue Aug 29, 2013 · 4 comments

Comments

@nilshoerrmann
Copy link
Contributor

While I understand that the setup of importers is left to developers, is there any specific reasons why authors cannot run them? I don't necessarily mean that they should see them in the navigation, but it would be nice if they could access the URL.

Currently, authors get a Symphony Access Denied page, but if they could access the import pages, it would be possible to add import buttons using Publish Shortcuts.

/cc @brendo

@brendo
Copy link
Member

brendo commented Sep 5, 2013

Not that I can think of. It's essentially bulk publishing so I don't have any issues removing this restriction.

@nilshoerrmann
Copy link
Contributor Author

What needs to be changes to allow authors to run importers?

@brendo
Copy link
Member

brendo commented Dec 17, 2014

I've had a look at this and unfortunately I don't know how to lift this restriction. The 'run' and 'index' pages are the same page, so short of duplicating the page and allowing one to be accessible by authors (run only) and the other as is, I'm stumped.

@nilshoerrmann
Copy link
Contributor Author

While working on a project, this issue came up again. I think it would be just fine to let authors access all importer pages. There are only two things that should be disallowed for authors in my eyes:

  1. Authors should not be able to edit/save importers: the Create New button should be removed, the action buttons on the edit pages should be removed and – maybe – the links to the edit pages.
  2. Authors should not see the link to the extension's pages in the navigation automatically: this should be a setting in the preferences because it depends on the project, if the navigation link is desireable or not.

What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants