gmane.comp.cms.magnolia.devel

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2356) magnolia-parent-pom-ce is missing groupId

JIRA (on behalf of Gregory Joseph — 2008-09-06T18:39:11

[ http://jira.magnolia.info/browse/MAGNOLIA-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780#action_17780 ] Gregory Joseph commented on MAGNOLIA-2356: ------------------------------------------ Hi Philippe, Actually all except the "main" parent-pom do not specify their groupId specifically, so they inherit it from {{magnolia-parent-pom}}. Is that an issue ? I just noticed that {{magnolia-parent-pom-abstract}} actually does specify it; I don't really care either way, but would like to be consistent, so I'll wait for your opinion on this ;)

[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2356) magnolia-parent-pom-ce is missing groupId

JIRA (on behalf of Gregory Joseph — 2008-09-06T18:36:11

[ http://jira.magnolia.info/browse/MAGNOLIA-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Joseph reassigned MAGNOLIA-2356: ---------------------------------------- Assignee: Gregory Joseph (was: Boris Kraft)

[magnolia-dev] [JIRA] Created: (MAGNOLIA-2356) magnolia-parent-pom-ce is missing groupId

JIRA (on behalf of Philippe Marschall — 2008-09-06T16:59:11

magnolia-parent-pom-ce is missing groupId ----------------------------------------- Key: MAGNOLIA-2356 URL: http://jira.magnolia.info/browse/MAGNOLIA-2356 Project: Magnolia Issue Type: Bug Reporter: Philippe Marschall Assignee: Boris Kraft Attachments: pom.xml.patch The magnolia-parent-pom-ce is missing the groupId. Patch attached.

[magnolia-dev] [JIRA] Created: (MAGNOLIA-2355) RemoveMixversionableFilter uses Sun implementation class

JIRA (on behalf of Philippe Marschall — 2008-09-06T15:52:11

RemoveMixversionableFilter uses Sun implementation class -------------------------------------------------------- Key: MAGNOLIA-2355 URL: http://jira.magnolia.info/browse/MAGNOLIA-2355 Project: Magnolia Issue Type: Improvement Components: core Affects Versions: 3.6.1 Reporter: Philippe Marschall Assignee: Philipp Bracher Priority: Critical Attachments: RemoveMixversionableFilter.java.patch RemoveMixversionableFilter uses the Sun and JDK specific class com.sun.org.apache.xalan.internal.xsltc.runtime.AttributeList. Patch attached.

Re: [magnolia-dev] SVN restructuring

Grégory Joseph — 2008-09-06T13:52:43

Yeah, I forgot to mention I updated http://wiki.magnolia.info/display/DEV/Svn+structure Some more notes to be found at http://dev.magnolia.info/~gjoseph/news-from-bob Cheers, -g On Sep 6, 2008, at 12:44 AM, Vasko Gjurovski wrote: ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------

Re: [magnolia-dev] SVN restructuring

Vasko Gjurovski — 2008-09-05T22:44:20

My bad.. found it under build.. where I should have looked at the first place... Sorry for the false alaram... :) Regards, Vasko On Fri, Sep 5, 2008 at 11:39 PM, Vasko Gjurovski public.gmane.org> wrote: ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------

Re: [magnolia-dev] SVN restructuring

Vasko Gjurovski — 2008-09-05T21:39:38

I have been trying to build magnolia via Netbeans and as I was able to see that the parent of magnolia-parent-pom-abstract is magnolia-parent-pom which is nowhere to be found. Couldn't find it on the svn (I believe it used to be before the restructuring) and it can't be found on any repository. Am I doing something wrong or somebody forgot to commit something? Regards, Vasko Gjurovski On Wed, Aug 27, 2008 at 9:49 PM, Grégory Joseph public.gmane.org> wrote: ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------

[magnolia-dev] [JIRA] Updated: (MGNLDMS-96) sample DMS paragraph filters on 'extension' instead of 'type'

JIRA (on behalf of Jan Haderka — 2008-09-05T12:18:33

[ http://jira.magnolia.info/browse/MGNLDMS-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLDMS-96: ------------------------------- Original Estimate: (was: 1 minute) Remaining Estimate: (was: 1 minute)

[magnolia-dev] [JIRA] Commented: (MGNLDMS-96) sample DMS paragraph filters on 'extension' instead of 'type'

JIRA (on behalf of Jan Haderka — 2008-09-05T12:18:30

[ http://jira.magnolia.info/browse/MGNLDMS-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777#action_17777 ] Jan Haderka commented on MGNLDMS-96: ------------------------------------ The confusion comes from the fact that DMS stores the file type separately in the String type node data called "type". Apart from that extension of the uploaded file is stored also as an "extension" attribute of the binary node data holding uploaded file data. So in theory you can use both to filter the query results. With the default dms configuration I was not able to create an situation in which value of "type" property and "extension" attribute would not be in sync. If you were able to create such situation, please describe it here.

[magnolia-dev] [JIRA] Commented: (MGNLDMS-132) Dms query paragraph wrongly assumes that the "link" property is a path

JIRA (on behalf of Jan Haderka — 2008-09-05T10:51:30

[ http://jira.magnolia.info/browse/MGNLDMS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776#action_17776 ] Jan Haderka commented on MGNLDMS-132: ------------------------------------- The cause of the issue is the fact that that both dms and sitedesigner define dialog called dmsParagraph and while DMS-dmsParagraph defines "link" to use link control, SD-dmsParagraph defines "link" property to use uuidLink control. Do we rename paragraph in DMS or in SD to solve this? Also perhaps we should issue a warning when there are multiple dialogs or paragraphs of same name ...

[magnolia-dev] [JIRA] Resolved: (MGNLDMS-126) DMS Module Makes Web Pages With "dms" At Start Break

JIRA (on behalf of Jan Haderka — 2008-09-05T08:58:30

[ http://jira.magnolia.info/browse/MGNLDMS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka resolved MGNLDMS-126. --------------------------------- Resolution: Fixed Works fine with the other recent changes. Links constructed in the paragraph are fine as well and do not contain double slashes. Now you documents in root starting with "dms" will not be mistaken for links to dms. But if you create document called dms, any children of such document will be still unreachable.

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2353) Disabling all caching in magnolia 3.6.1

JIRA (on behalf of Jan Haderka — 2008-09-05T08:34:30

[ http://jira.magnolia.info/browse/MAGNOLIA-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773#action_17773 ] Jan Haderka commented on MAGNOLIA-2353: --------------------------------------- The most extreme way of disabling caching is to remove cache and gzip filters from filter chain (/server/filters). Could you please describe what makes you believe responses are still cached on server side even after you disabled cache? Also can you capture request and response headers for scenario when it works properly and when it doesn't work and attach it to the issue so we can analyze it and fix the issue? Thanks.

[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2095) Include Paragraph name in edit bar and/or dialog title bar

JIRA (on behalf of Jan Haderka — 2008-09-05T08:25:30

[ http://jira.magnolia.info/browse/MAGNOLIA-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka resolved MAGNOLIA-2095. ----------------------------------- Resolution: Fixed r17871 there is new optional attribute in the EditBar tag called showParagraphName, set it to true to show the paragraph names.

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2354) Show Paragraph path in edit bar or dialog

JIRA (on behalf of Jan Haderka — 2008-09-05T08:23:30

[ http://jira.magnolia.info/browse/MAGNOLIA-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-2354: ---------------------------------- Fix Version/s: 3.6.3 (was: 3.6.2) Description: It is useful for developers to see sometimes path to the paragraph that is currently used specially when there are many paragraphs defined in the system. (was: When creating a new paragraph or editing it later, it would be good to know which editor is being used as a memory reference. Used for creating similar paragraphs at a later date or reporting page build actions. When there are MANY paragraphs in a list, it's not always easy to remember what you've worked with.)

[magnolia-dev] [JIRA] Created: (MAGNOLIA-2354) Show Paragraph path in edit bar or dialog

JIRA (on behalf of Jan Haderka — 2008-09-05T08:21:30

Show Paragraph path in edit bar or dialog ----------------------------------------- Key: MAGNOLIA-2354 URL: http://jira.magnolia.info/browse/MAGNOLIA-2354 Project: Magnolia Issue Type: Improvement Reporter: Dawn Messier Assignee: Gregory Joseph Priority: Minor Fix For: 3.6.2 When creating a new paragraph or editing it later, it would be good to know which editor is being used as a memory reference. Used for creating similar paragraphs at a later date or reporting page build actions. When there are MANY paragraphs in a list, it's not always easy to remember what you've worked with.

[magnolia-dev] [JIRA] Assigned: (MGNLDMS-126) DMS Module Makes Web Pages With "dms" At Start Break

JIRA (on behalf of Gregory Joseph — 2008-09-05T00:26:30

[ http://jira.magnolia.info/browse/MGNLDMS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Joseph reassigned MGNLDMS-126: -------------------------------------- Assignee: Jan Haderka (was: Philipp Bracher) Jan, can you check this with regards to the fixes you've made for the linked issues?

[magnolia-dev] [JIRA] Commented: (MGNLDMS-126) DMS Module Makes Web Pages With "dms" At Start Break

JIRA (on behalf of Jeff Snider — 2008-09-04T18:16:30

[ http://jira.magnolia.info/browse/MGNLDMS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765#action_17765 ] Jeff Snider commented on MGNLDMS-126: ------------------------------------- What we found was that the URI 2 Repository mappings are actually two way, but only on some places. Changing it from "/dms" to "/dms/" worked fine when browsing through the dms in admin central, but it broke from the editor paragraphs that had internal links back to the dms. It created a link to "/dms//folder/file.doc". With the extra slash, it caused a 404. Since the problem only appears for root level pages and we create those pages for our users, we decided it was easier to just avoid it with process than programming.

[magnolia-dev] [JIRA] Created: (MAGNOLIA-2353) Disabling all caching in magnolia 3.6.1

JIRA (on behalf of Tyronne Mae — 2008-09-04T16:19:30

Disabling all caching in magnolia 3.6.1 --------------------------------------- Key: MAGNOLIA-2353 URL: http://jira.magnolia.info/browse/MAGNOLIA-2353 Project: Magnolia Issue Type: Task Affects Versions: 3.6.1 Environment: linux Reporter: Tyronne Mae Assignee: Boris Kraft Priority: Minor How to entirely disable response caching throughout version 3.6.1, does not appear to work as it did in versions 3.5.x.. For instance we are requesting content from cms using RequestLocaleAwareI18nContentSupport so that content is returned in correct locale for client browser.. however at the moment, this localised response seems to be caching even though we have deactivated/disabled caching/advanced-caching.. can you please advise? thanks in advance,

[magnolia-dev] [JIRA] Created: (MAGNOLIA-2352) OSGi for a module container?

JIRA (on behalf of Edgar Vonk — 2008-09-04T15:14:30

OSGi for a module container? ---------------------------- Key: MAGNOLIA-2352 URL: http://jira.magnolia.info/browse/MAGNOLIA-2352 Project: Magnolia Issue Type: New Feature Components: updatemechanism Affects Versions: Ideas Reporter: Edgar Vonk Assignee: Boris Kraft The module mechanism (bootstrapping, reloading of classes) is only done on startup of Magnolia (ignoring the deployment tools). Maybe it is an idea to use an OSGi container (like Felix) in which to run the Magnolia modules. The advantage is that you could update modules on the fly without having to restart your application server. Of course you would still need to think about bootstrapping JCR data. GX WebManager, a leading Dutch CMS, uses OSGi for their module mechanism (called "WCB's", WebManager Component Bundles). This works very nicely. They have a community edition out but it is not an open source product..

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-573) customizable change notification

JIRA (on behalf of Jan Haderka — 2008-09-04T12:24:30

[ http://jira.magnolia.info/browse/MAGNOLIA-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758#action_17758 ] Jan Haderka commented on MAGNOLIA-573: -------------------------------------- Observation module is already able to send emails. It should be trivial to write more event listeners to for example store the infos from events in data module and make weekly digests or rss from there.

[magnolia-dev] Spanish Magnolia blog

Boris Kraft — 2008-09-04T09:26:12

Magnolia news of the day: Alvaro started blogging in Spanish: http://magnolia-cms-hispano.blogspot.com/ Follow us on Twitter for more Magnolia news: http://twitter.com/magnolia_cms Cheers Boris ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------