Hello, thanks for the great module. It's so much help. I wanted to open it up for clients/site managers to use, but was hoping there would be a way to restrict block selection only to those blocks with visibility set for their role.

thanks so much!

Comments

irakli’s picture

irakli commented

Do you mean - block selection when you are constructing the queue?

g76’s picture

g76 commented

yes. I wanted clients to be able to create block queues and manage their own blocks (only the ones they have access to).

thanks so much, I love your module!

Jen

irakli’s picture

irakli commented

I am afraid, I am missing something here.

1. What's the determinant of "their own blocks"? Blocks they've created? And they would have no access to any other blocks?
2. If #1 is true, then block queues must be owned by owner, as well. A queue can not contain blocks that user can arrange and others that he/she can not. Imagine a scenario: John creates a queue and adds blocks A,B,C in it that he had created. Later Joanne (an administrator) adds blocks X,Y,Z that are not authored by John. On day 3rd, John comes back and wants to arrange blocks in the block queue. However, the queue now contains blocks he does not have access to. He can not manage only part of the queue (makes no sense), so he gets blocked from the queue he's started? Also makes no sense.

Sorry, but unless you provide more details, this requirement does not seem consistent, in the manner it is currently stated.

Thank you for your interest.

sebastien m.’s picture

sebastien m. commented
Version: 6.x-1.6 » 6.x-1.9
Issue summary: View changes
Status: Active » Closed (won't fix)

This module is no more maintained on it's 6.x branch.
Sorry, but such behavior seems to be quite overhead and won't be implemented on the 7.x branch.

So I'll close this issue because won't be fixed under 6.x branch.