Thanks for sharing Juan!

This is so great!

I got this same requirement yesterday during a demo! How cool is that this company can now just install the hook plugin and start using it

And thanks to http://www.savoirfairelinux.com

Thanks for sharing

Thank you very much Juan for creating a ticket about it (that contribution was just a very small hook. We are currently publishing portlets as well).

This was made possible thanks to:
* Liferay's team: for the very powerfull SDK for developping hooks, portlets, and themes.
* my development team which does the work
* my company: which promotes open-source and invests in R&D.
* our customers: who accept that the work we do for them is then shared with the community.

"This is the kind of changes that we may not be interested in adding to the core"

Without that contribution scope selection in Asset configuration is almost useless. As you can see in comments this is very helpful extension so I think it should be a part of Liferay core. Maybe we should make a site when we (community) can vote for features that should go to core similar to this one: http://www.google.com/moderator/#15/e=2a03&t=2a03.40&f=2a03.9adac

Great feature.

I find hooks really useful and use them often. From Liferay fine tunning to mods in bulk or feature addition/modification.

And Liferay is improving them a lot making possible to change more and more points in the platform on the fly.

Congratulations to both Savoirfaire and Liferay.

regards

I am developing a second portal using liferay and again I struggle with the same problem. I have the following requirements:

1. portal content administration must be partitioned according the organization structure so that every department has a right to publish and edit its own articles.

2. the content must be read-only available to the world. It must be searchable, categorizable and published on any portal page independently of its departamental ownership.

I can not find a convenient way to implement it using liferay despite Liferays eleborate implementation of many partitioning and access management concepts like communities, organizations, roles, groups and scopes. It puzzles me. Is this requirement so rare or I am trying to work with Liferay in a wrong direction?

To model the first requirement, it seems, it would be good to use the organizations. But if the content items are organization-scoped, then there is no normal way to present them on a single page with the items of other organizations. Or to make them appear on a single search result list.

If I do not use organizations, then there is no good way to group the content to restrict its management rights.

What is the best way to satisfy my requirements? What would you recommend?