eZecosystem / Issues

Carlos Revillo commented on EZP-29433 - Replacing default Editor policy Content,*,* with Content,read,* produces error for Editors in back office

i think i know where the issue come from.
with the conditions above the user has read access for '/1/2/' and '/1/43/'.
When the location is trying to be rendered, it tries to build the related tabs. when it reach the tab for the url, it reach this piece of code https://github.com/ezsystems/ezplatform-admin-ui/blob/master/src/lib/Tab/LocationView/UrlsTab.php#L133

there it tries to load location 1, parent of location 2. as it has no rights, then the issue arise.

i've created a pull request here. let me know your thoughts
https://github.com/ezsystems/ezplatform-admin-ui/pull/568

07/18/2018 01:19 pm   jira.ez.no   Mirror   Link

Sylvain Guittard commented on EZP-29436 - Create policy is not enough to create Role or Content Type

Thanks Andrzej Longosz for checking and confirming the reason.
role/create can also confuse users. I expect to be able to create a new role. Role and Content Types are not like content items, you cannot send them for review and another user cannot access what you just created. So right now, having only role/create is not useful for the user.

I think the issue is related to the publish action that is related to role/update. As you said, we should have role/publish.
But do we need this granularity for the roles and content types? In eZ Publish it was not the case.
Bertrand Dunogier any idea why we added those permissions?

07/18/2018 11:38 am   jira.ez.no   Mirror   Link

Andrzej Longosz commented on EZP-29436 - Create policy is not enough to create Role or Content Type

Sylvain Guittard: Yes, it is related to kernel, but it is not a bug.

The Public API workflow for roles is as follows:

  1. Create role from struct, which returns Role Draft and requires role/create.
  2. Publish Role Draft, which requires role/update.

This is not a bug because API can be used as follows:

  1. Create Draft from existing Role, which requires role/create.
  2. Update Role Draft. which requires role/update.
  3. Publish Role Draft, which requires role/update.

AFAICS there is no way to distinguish if draft was just created or if it's a Draft for Role being updated.

The same scenario can be inferred for Content Type.

The use case for this setup is one user being able to only draft a Role and the other user having permissions to publish it (confirm the action of the first user).
Policy for publishing Draft probably should be role/publish, so it would be less misleading. However introducing it would require running database upgrade script to avoid BC break.

The problem is that AdminUI does not reflect API expectations.

BTW. Barbara Grajczyk these are two separate issues, should be reported separately. It seems similar because probably one feature was modelled based on the other.

07/18/2018 10:13 am   jira.ez.no   Mirror   Link

Sylvain Guittard commented on EZP-29436 - Create policy is not enough to create Role or Content Type

According to Mikołaj Adamczyk, it's related to kernel. Andrzej Longosz could you please confirm that?

07/18/2018 09:23 am   jira.ez.no   Mirror   Link

Barbara Grajczyk changed the status to Confirmed on EZP-29436 - Create policy is not enough to create Role or Content Type

07/18/2018 08:45 am   jira.ez.no   Mirror   Link

Barbara Grajczyk updated the Description of EZP-29436 - Create policy is not enough to create Role or Content Type

Roles:

Steps

1. Create a User with policies listed below:

  • User/Login
  • User/Password
  • Content/Read
  • Setup/Administrate
  • Role/Create
  • Role/Read
    2. Log in as a new user
    3. Go to Admin/Roles
    4. Click [+] button and fill the field
    5. Click Create
Actual result:

There is a message: User does not have access to 'update' 'role'

Content Types:

1. Create a User with policies listed below:

  • User/Login
  • User/Password
  • Content/Read
  • Setup/Administrate
  • Class/Create
    2. Log in as a new user
    3. Go to Admin/Content Types/Content
    4. Click [+] button and fill Identifier
    5. Click Add field definition
Actual result:

There is a message: User does not have access to 'update' 'ContentType'

Expected result:

For both cases user should be able to create role/content type only with Create policy. Update should be connected with editing.

07/18/2018 08:45 am   jira.ez.no   Mirror   Link

Barbara Grajczyk updated the Description of EZP-29436 - Create policy is not enough to create Role or Content Type

Roles:

Steps

1. Create a User with policies listed below:

  • User/Login
  • User/Password
  • Content/Read
  • Setup/Administrate
  • Role/Create
  • Role/Read
    2. Log in as a new user
    3. Go to Admin/Roles
    4. Click [+] button and fill the field
    5. Click Create
Actual result:

There is a message: User does not have access to 'update' 'role'

Content Types:

1. Create a User with policies listed below:

  • User/Login
  • User/Password
  • Content/Read
  • Setup/Administrate
  • Class/Create
    2. Log in as a new user
    3. Go to Admin/Content Types/Content
    4. Click [+] button and fill Identifier
    5. Click Add field definition
Actual result:

There is a message: User does not have access to 'update' 'ContentType'

Expected result:

For both cases user should be able to create role/content type only with Create policy. Update should be connected with editing.

07/18/2018 08:45 am   jira.ez.no   Mirror   Link

Barbara Grajczyk created EZP-29436 - Create policy is not enough to create Role or Content Type

Roles:

Steps

1. Create a User with policies listed below:

  • User/Login
  • User/Password
  • Content/Read
  • Setup/Administrate
  • Role/Create
  • Role/Read
    2. Log in as a new user
    3. Go to Admin/Roles
    4. Click [+] button and fill the field
    5. Click Create
Actual result:

There is a message: User does not have access to 'update' 'role'

Content Types:

1. Create a User with policies listed below:

  • User/Login
  • User/Password
  • Content/Read
  • Setup/Administrate
  • Class/Create
    2. Log in as a new user
    3. Go to Admin/Content Types/Content
    4. Click [+] button and fill Identifier
    5. Click Add field definition
Actual result:

There is a message: User does not have access to 'update' 'ContentType'

Expected result:

For both cases user should be able to create role/content type only with Create policy. Update should be connected with editing.

07/18/2018 08:44 am   jira.ez.no   Mirror   Link

Dominika Kurek changed the status to QA on EZP-29276 - As a QA I want to cover scenarios of testing media, binary and image fields in content management

07/18/2018 08:24 am   jira.ez.no   Mirror   Link

Barbara Grajczyk changed the status to Confirmed on EZP-29435 - It is impossible to swap locations of two non-container Content Items

07/18/2018 08:23 am   jira.ez.no   Mirror   Link

Barbara Grajczyk created EZP-29435 - It is impossible to swap locations of two non-container Content Items

PREREQUISITES:

Two non-container content items and one container content item with children

STEPS:
  1. Go to Content > Content Structure > non-container CI
  2. Go to Locations tab and click Swap locations
  3. Try to select the second non-container content item
ACTUAL RESULT:

In UDW there is still blocked non-container object instead of containers with children.

EXPECTED RESULT:

You cannot select containers with children in UDW. But it should be possible to select non-containers.

07/18/2018 08:23 am   jira.ez.no   Mirror   Link

Dominika Kurek commented on EZP-28447 - Document consequences of changing Content Type name pattern

PR: https://github.com/ezsystems/developer-documentation/pull/345

07/18/2018 08:17 am   jira.ez.no   Mirror   Link

Barbara Grajczyk changed the status to Confirmed on EZP-29434 - Folder Content Type is displayed as N/A on subitems list

07/18/2018 08:16 am   jira.ez.no   Mirror   Link

Barbara Grajczyk attached one file to EZP-29434 - Folder Content Type is displayed as N/A on subitems list

07/18/2018 08:16 am   jira.ez.no   Mirror   Link

Barbara Grajczyk created EZP-29434 - Folder Content Type is displayed as N/A on subitems list

Preconditions:

To make path shorter, please configure in vendor/ezsystems/ezplatform-admin-ui/src/bundle/Resources/config/ezplatform_default_settings.yml like placed below:
ezsettings.default.subitems_module.limit: 1

Steps:
  1. Go to Content/Content structure
  2. Create a Folder (path: eZ Platform/Folder)
  3. Go back to eZ Platform and create new image (path: eZ Platform/Image)
  4. Go back to eZ Platform and scroll down to the subitems
  5. Switch to the grid view
  6. Click Show more results
  7. Switch to the list view
Actual result:

In Content Type column there is N/A for Folder

Expected result:

Folder should be displayed.

07/18/2018 08:16 am   jira.ez.no   Mirror   Link

Dominika Kurek changed the status to Documentation on EZP-28447 - Document consequences of changing Content Type name pattern

07/18/2018 08:14 am   jira.ez.no   Mirror   Link

Dominika Kurek resolved EZP-28447 - Document consequences of changing Content Type name pattern

07/18/2018 08:14 am   jira.ez.no   Mirror   Link

Dominika Kurek started progress on EZP-28447 - Document consequences of changing Content Type name pattern

07/18/2018 08:14 am   jira.ez.no   Mirror   Link

Dominika Kurek changed the status to Specification Done on EZP-28447 - Document consequences of changing Content Type name pattern

07/18/2018 08:14 am   jira.ez.no   Mirror   Link

Dominika Kurek changed the status to Specification on EZP-28447 - Document consequences of changing Content Type name pattern

07/18/2018 08:13 am   jira.ez.no   Mirror   Link

Maciej Tyrała commented on EZP-29276 - As a QA I want to cover scenarios of testing media, binary and image fields in content management

PR: https://github.com/ezsystems/ezplatform-admin-ui/pull/566

07/18/2018 08:12 am   jira.ez.no   Mirror   Link

Maciej Tyrała resolved EZP-29276 - As a QA I want to cover scenarios of testing media, binary and image fields in content management

07/18/2018 08:11 am   jira.ez.no   Mirror   Link

Mateusz Bieniek started progress on EZP-29379 - Changing section for content is not commited to the solr index

07/18/2018 08:09 am   jira.ez.no   Mirror   Link

Mateusz Bieniek changed the Assignee to 'Mateusz Bieniek' on EZP-29379 - Changing section for content is not commited to the solr index

07/18/2018 08:09 am   jira.ez.no   Mirror   Link

Magdalena Zuba closed EZP-29399 - Missing example Solr configuration for Platform.sh

07/18/2018 08:01 am   jira.ez.no   Mirror   Link

Magdalena Zuba changed the status to Documentation Done on EZP-29399 - Missing example Solr configuration for Platform.sh

07/18/2018 08:01 am   jira.ez.no   Mirror   Link

André Rømcke changed the status to Confirmed on EZP-29418 - Wrong Session Name after EZP-29390

07/18/2018 07:39 am   jira.ez.no   Mirror   Link

Dariusz Szut commented on EZP-29182 - As an Editor, I want to select a content item directly for a single selection to minimize the number of clicks

PR created: https://github.com/ezsystems/ezplatform-admin-ui-modules/pull/94

07/18/2018 07:14 am   jira.ez.no   Mirror   Link

Dariusz Szut commented on EZP-29187 - As an Editor, I want to see a relevant UDW title for MULTI-SELECTION

PR created: https://github.com/ezsystems/ezplatform-admin-ui-modules/pull/94

07/18/2018 07:14 am   jira.ez.no   Mirror   Link