…s to clean up the output for the site search results.
…y to Downloads page.
…ch plugin. Still need to add caching though.
… corresponding URLs (same as for the Issues link).
…nn, they are permanently redirected to the corresponding plugin page. Before, an exception would be thrown because the view was expecting a WikiPage instance rather than a PluginTab one. As far as I can tell, only web crawlers hit these URLs.
…pgraded to Resources plugin 1.0-RC2 (from the snapshot).
…he REST interface. In addition, fixed a NullPointerException that occurred when using the 'Create Plugin' page.
…plugin forum when a new plugin is released.
…rsion, just include a version number with the ' beta' suffix in the downloads.versions config setting.
…ed and an error message rendered. This helps keep a common exception stack trace out of the logs.
…had already been updated).
…also now displays the type of each result. And finally, fixed a bug where the result title wasn't being encoded as HTML.
… as HTML. Also removed a bunch of views and templates that weren't being used.
…an build the project and run it with existing data.
…sage in place of the results, rather than an exception trace. This is because we now catch SearchEngineQueryParseException when searching.
…an the contents of its description tab.
…ciated plugins. This commit fixes that by manually reindexing the plugin when tab contents are changed.
…er works. The new one points to a 'browse Grails Plugins project category' page.
… for the grails-plugins project.
…he split between WikiPage and PluginTab. Also improves code sharing, but does introduce some hacks with regard to some of the wiki/plugin tab views.
…round plugin tabs. Basically, some plugins are pointing to the wrong DB records for some of their tabs. This fix will enable us to remove the duplicates.