eZecosystem / Mirror

Mirror

eZecosystem Sources Mirror

This is a mirror based on the rss and atom feeds of eZ Publish Platform related sources on the internet. This mirror exists as a point in time reflection of eZ Publish Platform and Symfony ecosystem and related community activity. Contact us if you have a feed you want added to this site.


New! Checkout our new GitHub homepage! Follow the latest activity of eZ Publish Developers on GitHub.com


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
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezpublish-legacy Jul 18, 2018
2 commits to master
07/18/2018 12:10 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezplatform-demo Jul 18, 2018
2 commits to master
  • @andrerom 7e82bcc
    Merge branch 'demo_2.2' into demo_master
  • @lolautruche 13560bb
    Change instanciation position of EzCoreExtraBundle (#90)
07/18/2018 12:08 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform-demo Jul 18, 2018
2 commits to master
  • @andrerom 7e82bcc
    Merge branch 'demo_2.2' into demo_master
  • @lolautruche 13560bb
    Change instanciation position of EzCoreExtraBundle (#90)
07/18/2018 11:59 am   eZecosystem @ GitHub   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
@andrerom
andrerom deleted branch cache_locations_limits at ezsystems/ezpublish-kernel Jul 18, 2018
07/18/2018 10:22 am   André @ GitHub   Mirror   Link  
@andrerom
andrerom closed a pull request in ezsystems/ezpublish-kernel Jul 18, 2018
[RFC][Cache] Limit number of locations we tag to not cripple performance #2399

Reported on slack on some install with several hundred locations for a given content, as Symfony Cache is not designed for such amount of tags it m…

+20 -0
7 comments
07/18/2018 10:22 am   André @ GitHub   Mirror   Link  
@andrerom
andrerom commented on pull request ezsystems/ezpublish-kernel#2399 Jul 18, 2018

ah, yeah but that would still be throwing on a issue further down, so I'll be closing this for now and look for alternative ways ;)

07/18/2018 10:22 am   André @ GitHub   Mirror   Link  
@andrerom
andrerom commented on pull request ezsystems/ezplatform-demo#90 Jul 18, 2018

I would guess that means basically applying the features directly where the extended feature is in Core, as opposed to having to apply them retroac…

07/18/2018 10:14 am   André @ GitHub   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
@lolautruche
lolautruche commented on pull request ezsystems/ezplatform-demo#90 Jul 18, 2018

@lserwatka You mean all the features provided by EzCoreExtra?

07/18/2018 10:09 am   Jérôme @ GitHub   Mirror   Link  
@gggeek
gggeek commented on pull request ezsystems/ezpublish-kernel#2399 Jul 18, 2018

"enforce the limit at editing time" => sorry, badly phrased. More like: "throw an exception at this layer and let upper layer transform this into a…

07/18/2018 09:48 am   Gaetano @ GitHub   Mirror   Link  
@emodric
emodric commented on pull request ezsystems/ezpublish-legacy#1377 Jul 18, 2018

Thanks @blankse ! This also fixes the notice I reported :)

07/18/2018 09:26 am   Edi @ GitHub   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
@emodric
emodric pushed to master in netgen/NetgenDocs Jul 18, 2018
1 commit to master
  • @emodric b1ac2a7
    Use https protocol for docs.netgen.io
07/18/2018 09:21 am   Edi @ GitHub   Mirror   Link  
@andrerom
andrerom commented on issue netgen/TagsBundle#77 Jul 18, 2018

@alongosz / @damianz5 Any takes on what will be needed to avoid this issue from standard design?

07/18/2018 09:07 am   André @ GitHub   Mirror   Link  
@andrerom
andrerom commented on pull request ezsystems/ezplatform-demo#90 Jul 18, 2018

@damianz5 be aware I did not port this over to ezplatform-ee-demo as they don't share code base so I can't merge it in there, so I'll let you take …

07/18/2018 09:05 am   André @ GitHub   Mirror   Link  
@emodric
emodric commented on issue netgen/TagsBundle#77 Jul 18, 2018

@flutchman I don't know how to fix this. The templates need to be in default scope to allow using them in every area, and not to limit them to admi…

07/18/2018 09:04 am   Edi @ GitHub   Mirror   Link  
@andrerom
andrerom commented on pull request ezsystems/ezplatform-demo#90 Jul 18, 2018

It could be, would that make sense for you @bdunogier and @SylvainGuittard ?

07/18/2018 09:03 am   André @ GitHub   Mirror   Link  
@andrerom
andrerom pushed to master in ezsystems/ezplatform-demo Jul 18, 2018
2 commits to master
  • @andrerom 7e82bcc
    Merge branch 'demo_2.2' into demo_master
  • @lolautruche 13560bb
    Change instanciation position of EzCoreExtraBundle (#90)
07/18/2018 09:00 am   André @ GitHub   Mirror   Link  
@lolautruche
lolautruche commented on pull request ezsystems/ezplatform-demo#90 Jul 18, 2018

Thanks guys! What about including EzCoreExtra into standard distribution? Would it be something relevant to you?

07/18/2018 08:59 am   Jérôme @ GitHub   Mirror   Link  
@andrerom
andrerom pushed to 2.2 in ezsystems/ezplatform-demo Jul 18, 2018
1 commit to 2.2
  • @lolautruche 13560bb
    Change instanciation position of EzCoreExtraBundle (#90)
07/18/2018 08:57 am   André @ GitHub   Mirror   Link  
@andrerom
andrerom merged a pull request in ezsystems/ezplatform-demo Jul 18, 2018
Change instanciation position of EzCoreExtraBundle #90

In order for all features of EzCoreExtraBundle to work, it must be instanciated after eZ dependencies. This is mainly because of compiler passes pr…

+1 -1
07/18/2018 08:57 am   André @ GitHub   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
@andrerom
andrerom commented on pull request ezsystems/ezpublish-kernel#2399 Jul 18, 2018

enforce the limit at editing time instead of fetching time this is on cache storing time (editing, publishing, ...) ;)

07/18/2018 08:34 am   André @ GitHub   Mirror   Link  
@gggeek
gggeek commented on pull request ezsystems/ezpublish-kernel#2399 Jul 18, 2018

Random ideas for alternatives: makes the limit at least configurable enforce the limit at editing time instead of fetching time

07/18/2018 08:27 am   Gaetano @ GitHub   Mirror   Link