antarctic74

antarctic74

58p

180 comments posted · 3 followers · following 0

12 years ago @ Magnolia Documentation - Shop · 0 replies · +1 points

{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.

12 years ago @ Magnolia Documentation - Disabling activation w... · 1 reply · +1 points

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.

12 years ago @ Magnolia Documentation - LDAP Connector · 1 reply · +1 points

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...

12 years ago @ Magnolia Documentation - Disabling activation w... · 4 replies · +1 points

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.

12 years ago @ Magnolia Documentation - Forum · 0 replies · +1 points

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.

12 years ago @ Magnolia Documentation - Rendering and templating · 0 replies · +1 points

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...

13 years ago @ Magnolia Documentation - Forum · 0 replies · +1 points

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.

13 years ago @ Magnolia Documentation - Forum · 2 replies · +1 points

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

13 years ago @ Magnolia Documentation - Activation · 0 replies · +1 points

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.

13 years ago @ Magnolia Documentation - Instances · 0 replies · +1 points

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.