gdp's Comments

Magnolia Documentation : Shop

Tue, 23 Jul 2013 07:46:26 +0000

{quote}Any release notes for updating module version?{quote} The dependencies listed above have been updated to match Shop 1.1.2. Hope this helps.

Magnolia Documentation : Disabling activation workflow

Tue, 23 Jul 2013 06:58:43 +0000

The Workflow module is installed with the Enterprise Edition by default. I think that was the case already in 4.3.1 so the default 4-eye workflow should be in place. Are you using the Community Edition? In CE the Workflow module is not installed by default but you can find it in the add-ons folder.

Magnolia Documentation : LDAP Connector

Mon, 15 Jul 2013 11:14:39 +0000

LDAP tester is in enterprise releases. It is also included in the LDAP bundle. Log into Nexus and search for magnolia-ldap-tester or see the directory below. http://nexus.magnolia-cms.com/
http://nexus.magnolia-cms.com/content/repositorie...

Magnolia Documentation : Disabling activation workflow

Thu, 11 Jul 2013 07:30:55 +0000

Yes, this is default behavior. When an editor deactivates a page, a workitem is sent to the publisher. The page will not be deactivated (removed from the public instance) until the publisher approves the workitem.

Magnolia Documentation : Forum

Fri, 28 Jun 2013 06:52:23 +0000

Forum has not been ported to 5.0 yet so it won't work there. But it should work on 4.5.9. If you can't see the Forum template in the dropdown, check step 3 "Make template available" again.

Magnolia Documentation : Rendering and templating

Mon, 17 Jun 2013 11:31:33 +0000

I recommend that you look at the Standard Templating Kit (STK) templates. Choose a template that is a close match to what you need and start customizing it. Extend the STK template, don't copy it. http://documentation.magnolia-cms.com/templates/s... http://documentation.magnolia-cms.com/templates/s... If you really want to create a template from scratch, follow the Introduction to templating tutorial. http://documentation.magnolia-cms.com/templates/i...

Magnolia Documentation : Forum

Wed, 29 May 2013 13:16:04 +0000

The Forum module installs the component definitions under the module folder. Look in Configuration > /modules/forum/templates/components. When the tutorial says "Add the forum components to the main area" it means you need to reference the component definitions from Templating Kit > Template Definitions > /pages/stkForum/areas/main/areas/content/availableComponents. For example, to make the threadView component available in the area, create a node threadView under availableComponents and under it an id node and set its value to forum:components/threadView. See how STK components such as stkTextImage are referenced for an example.

Magnolia Documentation : Forum

Wed, 29 May 2013 12:27:24 +0000

The screenshot are outdated. Add the forum components under Templating Kit > Template Definitions > /pages/stkForum/areas/main/areas/content/availableComponents.

Magnolia Documentation : Activation

Wed, 29 May 2013 08:53:55 +0000

You can create a key pair in Tools > Activation tools. It creates both a public and a private key. You can find them in the location defined in the magnolia.properties file. The default location is ${magnolia.home}/WEB-INF/config/default/magnolia-activation-keypair.properties. To keep the private key private, Magnolia doesn't publish it.

Magnolia Documentation : Instances

Wed, 29 May 2013 08:02:43 +0000

Having multiple instances and multiple redundant content stores is by-design. It uses more disk space but ensures availability when one instance goes down. Alternatively, you could use clustered storage for the workspace in question. The clustered workspace then becomes a single point of failure so be aware of that. When the clustered storage goes down, none of your 4 public instances can access the content. What type of content are you storing? Please describe your scenario on the Magnolia forum and ask for advice.

Magnolia Documentation : Community Edition on Windows

Wed, 29 May 2013 07:49:01 +0000

Look at the log file and try find the point where the author instance startup fails. Post the failure point to the Magnolia forum. Compare also the JARs between author and public. Are there differences?

Magnolia Documentation : Community Edition on Windows

Thu, 16 May 2013 11:06:56 +0000

Yes, mobile is included in both editions. http://www.magnolia-cms.com/magnolia-cms/features...

Magnolia Documentation : Rendering engine

Thu, 16 May 2013 11:03:49 +0000

Channels, yes. An example would be rendering the same content differently for desktop and mobile clients. You can select a channel in the URL with the mgnlChannel attribute. For example http://demopublic.magnolia-cms.com/demo-project.h...

Magnolia Documentation : Public User Registration

Wed, 17 Apr 2013 14:51:53 +0000

Are you looking on the public instance? Public users are typically registered on the public instance. So you need to log public to see them.

Magnolia Documentation : Public User Registration

Mon, 15 Apr 2013 11:16:54 +0000

Did you delete the Members area only from the author instance? Activate the changes.

Magnolia Documentation : JBoss 4.0

Wed, 10 Apr 2013 11:26:26 +0000

Kindly post your issue on the forum. http://forum.magnolia-cms.com Include a debug log from the JBoss server and Magnolia CMS. http://documentation.magnolia-cms.com/administrat...

Magnolia Documentation : Security

Mon, 8 Apr 2013 09:16:30 +0000

To add new fields to a user profile, add new controls to the useredit dialog. /modules/adminInterface/dialogs/useredit. The field values are stored under the user node in a new node named after the control node. You can use Tools > JCR queries to find users based on the new field. Suppose you added a new field "pet" to a profile and set eric's pet to "dog". Repository: users Query language: SQL Result ItemType: mgnl:user Query: select * from mgnl:user where pet='dog' If you want to make such a search available on the website, see http://documentation.magnolia-cms.com/searching.h... for options.

Magnolia Documentation : Cache

Fri, 5 Apr 2013 08:17:23 +0000

Remove the /server/filters/cache folder and its children from the filter chain. Removing the filter from the chain is different from removing the Cache module altogether. Removing the filter has no side effects. You don't need to do anything in /modules/cache.

Magnolia Documentation : Cache

Thu, 4 Apr 2013 12:52:20 +0000

Hi Raneez, Your configuration looks correct. Did you try restarting? Check also that you don't have other cache filters configured. It is possible to have multiple. As an alternative to disabling, you can remove the cache filter altogether.

Magnolia Documentation : Cache

Wed, 3 Apr 2013 13:49:27 +0000

Hi Raneez, Check first that you created an enabled property (node data), not a content node, and that its value is set to false. The number of elements in Cache Tools should indeed stop growing when cache is disabled. Considering the exception message you are getting, cache is still running. Try to restart the server.