Hi, thanks for the work on this module. Have you considered implementing block queue as a block configuration option ($op case 'configure'), so that if a user edits the block they can also edit the path, queue length, and added blocks? It seems like this would be a more "Drupalish" solution, and would also solve some of the error messages I'm getting related to using the Zen theme. Then the process of creating a block queue would look like this:
- Goto Block -> Add Block Queue
- Configure normal block settings (description, title, user/role/page visibility, etc) AND Block Queue settings (queue length, adding blocks, adjusting block weight)

Any thoughts/feedback?

Comments

sethcohn’s picture

sethcohn commented

I dislike this approach, as one of the advantages of the current method is a distinct block queue edit page, ala nodequeue. With your suggestion, users I only want to be able to edit queue _contents_ would be able to make other changes to the blockqueue itself.

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.
I agree with the last maintainer. Block exposed from "Blockqueue" can be too used in Panels, or tailor made templates.
More over, the new release (7.x) is based on CTools API, and the work to support a such behavior would be too huge.

So I'll close this issue because won't be fixed under 6.x branch.
However, thanks for your suggest.