Skip to content
This repository has been archived by the owner on Dec 2, 2020. It is now read-only.

Question about the purpose of this plugin? #1

Open
mgolino16 opened this issue Feb 4, 2015 · 4 comments
Open

Question about the purpose of this plugin? #1

mgolino16 opened this issue Feb 4, 2015 · 4 comments

Comments

@mgolino16
Copy link

What is the use of this plugin in hippo CMS since it has a built in "Updater Editor" feature? Is this redundant upon that feature but with a different UI or does it serve some other purpose?

@jreijn
Copy link
Owner

jreijn commented Feb 5, 2015

Hi thanks for the interest! This plugin preceded the Updater Editor and can be considered more a Groovy console. The Updater Editor is really focussed on performing update operations on the JCR. It's not capable of doing something else. This groovy addon gives you a way of creating and running any type of groovy script on the JCR. You could for instance create a report based on content in the JCR and write it to a CSV file or to some other location inside the repository or call a webservice and import some data into the repository.

@mgolino16
Copy link
Author

Thanks for the quick response and for putting the plugin together!
What I'm trying to do is write a reusable groovy script so admins can create new security domains from within the CMS to set permissions when new groups of users get added. Is this something you think I would need your plugin for or is the updater editor sufficient for this purpose?

@jreijn
Copy link
Owner

jreijn commented Feb 5, 2015

The Update Editor can do this just fine and you won't need this plugin do to just that. Have you seen the Groovy script at http://www.onehippo.org/library/concepts/update/groovy-update-script-examples.html ? It contains a script for creating security domains, etc.

@mgolino16
Copy link
Author

Oh that's super helpful! Thanks so much :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants