Sorry for the confusion, you should make a node under paragraphs in the same style as the other stk***** nodes. In this case, the node name should be kkpara, and it should have just a property "name" with the value "kkpara". Once you do that, the konakart paragraph should show up if you hit the "New Teasers" button on the STK demo page.
Show posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
1
Liferay, Magnolia, Hippo, dotCMS, OpenCms Integration / Re: Magnolia - Konakart integration
August 12, 2011, 07:16:30 pm2
Liferay, Magnolia, Hippo, dotCMS, OpenCms Integration / Re: Magnolia - Konakart integration
August 10, 2011, 08:34:28 pm
Hi Dritan!
This is Kyle from headwire. In response to your numbered questions:
1. The error is caused by the Konakart filter not being initialized. To fix this, go to the Configuration page of AdminCentral. Under /server/filters/ should be a list of filters with "konakart" at the bottom. Right click on this and move it to be directly above the "login" filter. Restart the server when this is done and the links will work.
2. The select box was removed in favor of a text box so that it can still work even with later versions of Konakart. The text box expects the name of a .jsp file located in the /WEB-INF/jsp/ folder. I recommend checking the paragraphs on the sample pages to get a feel of which .jsp is which. As a general rule, the ones that end in "Body" tend to be designed for the main column, the ones that end in "Tile" tend to be designed for the side columns of a page.
3. It supports 4.3.8. It needs a slight change to the WEB-INF/web.xml to run with Magnolia 4.4. If you want to use it with 4.4, around line 167 is two filter mappings for the magnoliaFilterChain. Add a "<dispatcher>INCLUDE</dispatcher>" to both.
4. This is the issue that was causing #1. The documentation is a little confusing, hopefully my description above makes sense.
5. I'm not sure where those are either. I'll find out and update the website. The HWT4M isn't required, and depending on what exactly you are doing it may add more clutter than you need as it adds over 100 templates.
6. The konakart paragraph needs to be added to the template definitions wherever you want to use it. The template definitions for the STK are under the configuration, /modules/standard-templating-kit/templates. Many of those have a /mainArea/paragraphs node, its under this node with the rest of the paragraphs you would put a new node called "kkpara" or "kksidepara" for whichever type of konakart paragraph you want. The konakart paragraph definitions themselves are under /modules/konakart/paragraphs.
I hope this helps. Please let us know if you have any other questions or recommendations on how we can improve the documentation. I'm glad to see someone using the module, hopefully it works well for your project.
Best regards,
Kyle
This is Kyle from headwire. In response to your numbered questions:
1. The error is caused by the Konakart filter not being initialized. To fix this, go to the Configuration page of AdminCentral. Under /server/filters/ should be a list of filters with "konakart" at the bottom. Right click on this and move it to be directly above the "login" filter. Restart the server when this is done and the links will work.
2. The select box was removed in favor of a text box so that it can still work even with later versions of Konakart. The text box expects the name of a .jsp file located in the /WEB-INF/jsp/ folder. I recommend checking the paragraphs on the sample pages to get a feel of which .jsp is which. As a general rule, the ones that end in "Body" tend to be designed for the main column, the ones that end in "Tile" tend to be designed for the side columns of a page.
3. It supports 4.3.8. It needs a slight change to the WEB-INF/web.xml to run with Magnolia 4.4. If you want to use it with 4.4, around line 167 is two filter mappings for the magnoliaFilterChain. Add a "<dispatcher>INCLUDE</dispatcher>" to both.
4. This is the issue that was causing #1. The documentation is a little confusing, hopefully my description above makes sense.
5. I'm not sure where those are either. I'll find out and update the website. The HWT4M isn't required, and depending on what exactly you are doing it may add more clutter than you need as it adds over 100 templates.
6. The konakart paragraph needs to be added to the template definitions wherever you want to use it. The template definitions for the STK are under the configuration, /modules/standard-templating-kit/templates. Many of those have a /mainArea/paragraphs node, its under this node with the rest of the paragraphs you would put a new node called "kkpara" or "kksidepara" for whichever type of konakart paragraph you want. The konakart paragraph definitions themselves are under /modules/konakart/paragraphs.
I hope this helps. Please let us know if you have any other questions or recommendations on how we can improve the documentation. I'm glad to see someone using the module, hopefully it works well for your project.
Best regards,
Kyle
Pages1