sitemapper

version 0.8, approval status: PENDING, submitted by donbeave 1 month ago

Create sitemaps on the fly. Easy add support for dynamic or static sitemaps for you site.

google-oauth2

version 0.12, approval status: PENDING, submitted by chazsconi 3 weeks ago

This plugin provides integration with Google Accounts to use with services such as Google Calendar. It handles the OAuth2 control flow including redirecting the user to Google to request authorisation, storing the credential in the session and DB (encrypted) and obtaining refresh tokens when necessary. It does this without being dependent on the Spring Security plugin. See the README.md in the repository for more information.

bulk-data-imports

version 0.1, approval status: PENDING, submitted by jerleng 3 weeks ago

Bulk Data Imports Plugin simplifies importing of bulk data via file uploads Default support for CSV and domain classes

image-manager

version 1.0, approval status: PENDING, submitted by bogdibota 1 week ago

A simple, yet effective, plugin for managing and using images stored in the database. It is very simple to use: # Domain class class MyDomainClass{ ... Image image static mapping = { ... image cascade: "all" } } # Image creation CommonsMultipartFile file ... myDomainClass.image = imageCreationService.createImage(file).save() # Display the image //full sized image //notice that the backgroundColor must be specified in hexadecimal RGB format: BLACK="0x000000", RED="0xFF0000" and so on

gertx

version 0.0.1, approval status: PENDING, submitted by rodrigo_salado 5 days ago

> Use the PlatformManager to carry Vertx to Grails and expose a EventBus instance to use into de GrailsApp > The plugin adds two JavaScript libraries sockjs.min.js and vertxbus.js in web-app/js/libs/ directory, so you can use the power of EventBus from the view more comfortably. > Also adds a verticle serving as administrator other verticles in grails-app/vertx/ directory called VerticleManager.groovy that you can access e.g. via telnet to deploy, undeploy verticles and list installed and uninstalled verticles. > To use gertx inside your grails application runtime you have to: 1: Add "gertx: 0.1" in BuildConfig.groovy as a plugin 2: Add into BootStrap.groovy 'def gertxService' 2.1: Init Vertx with 'gertxService.initVertx()' If you just want to use within the services 2.2: And if you want to use external verticles help you install and uninstall add 'gertxService.runVerticleManager()' e.g.: class BootStrap { def gertxService def testVertxService def init = { servletContext -> gertxService.initVertx() gertxService.runVerticleManager() testVertxService.testVerticle() } 2.3: If you use the VerticleManager be accessed from a terminal with the command 'telnet localhost 5436' to manage verticles. 2.3.1: To add a new verticle must create it in the folder grails-app/vertx/ e.g.: If you want to create a EventBus Bridge called WebEventBus.groovy create a file create a file with that name in the folder grails-app/vertx/ and type something like: def server = vertx.createHttpServer() server.requestHandler { req -> } vertx.createSockJSServer(server).bridge( prefix: '/eventbus', [[:]], [[:]] ) server.listen(5540) 2.3.2: Restart your grails app and I enjoy it. References: http://vertx.io/embedding_manual.html#embedding-the-VERTX-platform http://vertx.io/docs.html http://vertx.io/core_manual_groovy.html#sockjs-eventbus-bridge

logHibernateStats

version 0.9, approval status: PENDING, submitted by ishults 1 day ago

Just add {code} logHibernateStats.enabled = 'ALWAYS' // From ALWAYS, ALLOWED, NEVER {code} to the environments you want to track statistics for, then in your config set: {code} info 'grails.app.filters.controller.ControllerFilters' // or debug {code} You should now be seeing output like: {code} INFO controller.ControllerFilters - ############## Hibernate Stats ############## Action: /controller/actionName Transaction Count: 2 Flush Count: 1 Prepared Statement Count: 2 Total time: 500 ms ############################################# {code} after each request. If you set the logging to 'debug', you will also see: {code} DEBUG controller.ControllerFilters - ### Start logging for action: controller/actionName ### {code} at the start of each action (useful if logSql is enabled). If instead you'd like to target only specific actions, you can set {code} logHibernateStats.enabled = 'ALLOWED' {code} and instead append the parameter '_logHibernateStats=true' to your request. This will isolate the logging to just that request. Full documentation as well as the source can be [found here|https://github.com/ishults/logHibernateStats].