Messages posted by: marcpalmer

Hi,

As far as we know there are no major problems with Weceem plugin and grails 2.

If you have some specific problems, have you JIRA'd them?

Thanks
Marc

Hi,

With a custom application you can bypass the weceem.config.location requirement. However:

1) The uploader is not easily replaced with one that uses e.g. S3.
2) Weceem expects all uploaded resources (Server File and Server Directory - WcmContentFile nodes) to exist in the file system, and will just not work without this
3) Searchable/Compass/Lucene search indexes require file system access. If this works, it will require regeneration every time the VM is restarted
4) Clustering is not supported out of the box so running >1 CF instance will not propagate hibernate changes (or hence Searchable index changes) to other nodes, spring security will likely not replicate logged in user session info across nodes etc

Basically, if you want to try it please do and report back, but its going to be non-trivial.

Thanks
Marc

Hi,

I'm afraid you can do this. CloudFoundry does not support persistent filesystem access, which is used both for passing Config to standalone Weceem and for all the CK image/media uploader stuff.

We raised this as soon as CloudFoundry was launched and they still do not seem to have added support for persistent file systems.

I'm sorry I don't have better news for you.

Thanks
Marc

Hi,

You can probably do what you want with Weceem, but it will depend on whether wcm:render works for you.

You'll need to play with it - install weceem, create a content node, and call wcm:render in one of your GSPs and see if it does what you need.

Obviously you may need to decorate your "widgets" with your own markup, and probably your own GSP tag that does this and then delegates to wcm:render.

Marc

Hi,

The way Widgets are executed, they cannot pollute the global namespace.

It's best for widgets not to have side effects on the model, but if you need to do this you can set attributes on the request object:

[code]
<g:set var="xxx" value="yyy" scope="request"/>
[code]

The request should be the same in the template and other GSPs.

Marc

Hi,

Windows file URLs are always confusing in Java.

A quick google found this:

http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx

So try three / and the drive and colon.

Marc

Hi,

The error you're seeing there is I think an error relating to debug logging only. If you turn off weceem debug logging it should be fine. I believe this is fixed in master but not released.

The JDBC problem we have not seen anywhere. Can you tell us what database you are using? It sounds like there is an issue with schema generation or the JDBC driver you have.

Marc

Hi Richard,

It's great that you want to start trying out Weceem.

I'm sorry that you're encountering this problem, but it does not seem to be a Weceem problem. Weceem does not use jline at all, this is something that Grails uses for the command line shell.

I suspect you have some issue with your Grails installation.

We may be able to help if you can give some details about your environment - exact grails version used, OS, how you installed Grails, does grails create-app and run-app without weceem work for you?

Thanks
Marc

Hi Nicolas,

The HTML is a bug in the forums. Its very annoying

Hi Nicolas,

You need a bare minimum 512M heap to run a Grails app like this well.

I think we run http://info.noticelocal.com with 768M

Cheers

Hi Balsa,

That sounds like a problem with the content node info caching mechanisms, but it could be something else.

If you are still suffering this problem (apologies for the delay getting to you) could you please let me know what Weceem version you are using, and try with 1.1.2 if you are not using that.

Thanks

Hi,

It sounds like your content is referencing a template that no longer exists.

Is that possible?

Thanks

Hi Søren,

They should appear in the order they appear in the repository. Drag and drop to reorder repository nodes.

Cheers

Hi,

In case you didn't find this, its all in the Weceem plugin:

https://github.com/jCatalog/weceem-plugin

Hi,

Are you 100% sure it is picking up your policy at startup? It outputs the full path of the policy it is using at startup, please check this.

Cheers