<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.cms.magnolia.devel">
    <title>gmane.comp.cms.magnolia.devel</title>
    <link>http://blog.gmane.org/gmane.comp.cms.magnolia.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34631"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34629"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34628"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34627"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34626"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34625"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34623"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34616"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34613"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34605"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34604"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34601"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34594"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34593"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34592"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34591"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34588"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34587"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34584"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34580"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34631">
    <title>[magnolia-dev]  [JIRA] Updated: (MAGNOLIA-4421) CLONE -DefaultLocale and fallbackLocale dont behave as expected when creating a new Site definition</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34631</link>
    <description>&lt;pre&gt;
     [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Haderka updated MAGNOLIA-4421:
----------------------------------

    Priority: Minor  (was: Blocker)


&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Jan Haderka</dc:creator>
    <dc:date>2012-05-26T10:44:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34629">
    <title>[magnolia-dev]  [JIRA] Created: (MAGNOLIA-4424) CLONE -magnolia-empty-webapp should provide dependency on magnolia-templating-jsp and compatibility jars</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34629</link>
    <description>&lt;pre&gt;CLONE -magnolia-empty-webapp should provide dependency on magnolia-templating-jsp and compatibility jars
--------------------------------------------------------------------------------------------------------

                 Key: MAGNOLIA-4424
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4424
             Project: Magnolia
          Issue Type: Task
      Security Level: Public
          Components: build
            Reporter: Federico Grilli
            Assignee: Milan Divilek
             Fix For: 4.5.3


As both CE and EE webapps depend on m-empty-webapp and as Magnolia aims at providing JSP support out of the box, it makes sense to add m-templating-jsp dependency to the m-empty-webapp module. We also want to provide compatibility jars directly in the magnolia-empty-webapp rather than provide them as an add-on or as separate downloads. Furthermore, m-templating-samples should use scope {{provided}} so that the add-ons folder in the bundles does not contain a useless duplicate of m&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Milan Divilek</dc:creator>
    <dc:date>2012-05-25T14:56:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34628">
    <title>[magnolia-dev]  Magnolia as KB platform</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34628</link>
    <description>&lt;pre&gt;I'm looking for open source platform that could be used for Knowledgebase application. So it should have multilingual content creation with all other nice features, also way to create custom content template and have a way to assign categories to each item.
UI for end user I will build separately using API functions. 

Can Magnolia be used something like that? Can be stripped down with modules leaving only the ones that are important? Can it be easily extended?

&lt;/pre&gt;</description>
    <dc:creator>Martin Koppel (via Magnolia Forums</dc:creator>
    <dc:date>2012-05-25T14:44:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34627">
    <title>[magnolia-dev]  [JIRA] Created: (MAGNOLIA-4423) Rewrite Integration test-servlet sanity templates to not using cms-taglib tags</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34627</link>
    <description>&lt;pre&gt;Rewrite Integration test-servlet sanity templates to not using cms-taglib tags
------------------------------------------------------------------------------

                 Key: MAGNOLIA-4423
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4423
             Project: Magnolia
          Issue Type: Improvement
      Security Level: Public
          Components: integration tests
    Affects Versions: 4.5.3
            Reporter: Milan Divilek
            Priority: Major
             Fix For: 4.5.4


Integration test-servlet sanity templates are still written with tags from cms-taglibs. When we removed compatibility module from empty-webapp, this templates causes ce-bundle build on activation test to fail.

&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Milan Divilek</dc:creator>
    <dc:date>2012-05-25T14:32:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34626">
    <title>[magnolia-dev]  [JIRA] Created: (MAGNOLIA-4422) securityCallback is not working for custom pattern: PUR pattern not working</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34626</link>
    <description>&lt;pre&gt;securityCallback is not working for custom pattern: PUR pattern not working
---------------------------------------------------------------------------

                 Key: MAGNOLIA-4422
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4422
             Project: Magnolia
          Issue Type: Bug
      Security Level: Public
          Components: core
    Affects Versions: 4.5.2
            Reporter: Christian Ringele
            Assignee: Ondřej Chytil
            Priority: Critical
             Fix For: 4.5.x


After setting the ACL of the PUR right (MGNLPUR-68), the standard login form appears and not the PUR login form:
http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html?something

Seems as the public securityCallback pattern is ignored.

Besides:
Its not viewable&amp;amp;changeable anymore, to what 'location' the default 'form' pattern is matched to.
So it can't be changed, and for beginners it can't be known where it will apply to.

&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Christian Ringele</dc:creator>
    <dc:date>2012-05-25T10:08:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34625">
    <title>[magnolia-dev]  [JIRA] Created: (MGNLPUR-68) ACL of anonymous wrong set -&gt; no deny protected page</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34625</link>
    <description>&lt;pre&gt;ACL of anonymous wrong set -&amp;gt; no deny protected page
----------------------------------------------------

                 Key: MGNLPUR-68
                 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-68
             Project: Magnolia Public User Registration
          Issue Type: Bug
    Affects Versions: 1.4.1
            Reporter: Christian Ringele
            Assignee: Ondřej Chytil
            Priority: Critical
             Fix For: 1.4.2


The anonymous role has no deny on the protect page on a public:
http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html

The login screen does not appear.

&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Christian Ringele</dc:creator>
    <dc:date>2012-05-25T09:56:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34623">
    <title>[magnolia-dev]  [JIRA] Created: (MGNLSTK-958) RSS Feeds on Articles or Pages</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34623</link>
    <description>&lt;pre&gt;RSS Feeds on Articles or Pages
------------------------------

                 Key: MGNLSTK-958
                 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-958
             Project: Magnolia Standard Templating Kit
          Issue Type: New Feature
          Components: demoproject
            Reporter: Christian Hauser
            Assignee: Philipp Bärfuss


The main request on having RSS feeds on articles or pages was added to the Product Demo project within JIRA. 

It may be considered to add this feature to the 'Demo Project' instead, or later. 

&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Christian Hauser</dc:creator>
    <dc:date>2012-05-25T08:14:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34616">
    <title>[magnolia-dev]  [JIRA] Created: (MAGNOLIA-4420) Broken diff view - NullPointerException</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34616</link>
    <description>&lt;pre&gt;Broken diff view - NullPointerException
---------------------------------------

                 Key: MAGNOLIA-4420
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4420
             Project: Magnolia
          Issue Type: Bug
      Security Level: Public
          Components: admininterface
    Affects Versions: 4.4.5
            Reporter: Tomas Brimor
            Assignee: Philipp Bärfuss


Tried to show a version-diff for a page (webite repository) - in an author instance we have.

URL:
http://&amp;lt;host&amp;gt;/.magnolia/versionDiff?diffViewContentHandle=&amp;lt;path&amp;gt;&amp;amp;fromVersionNr=1.0&amp;amp;toVersionNr=

Result:
HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

java.lang.RuntimeException: java.lang.NullPointerException
        info.magnolia.module.cache.filter.CacheFilter.doFilter(CacheFilter.java:159)
        info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAb&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Tomas Brimor</dc:creator>
    <dc:date>2012-05-24T13:50:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34613">
    <title>[magnolia-dev]  [JIRA] Created: (MAGNOLIA-4419) Integration tests webapp contains pages with missing templates.</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34613</link>
    <description>&lt;pre&gt;Integration tests webapp contains pages with missing templates.
---------------------------------------------------------------

                 Key: MAGNOLIA-4419
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4419
             Project: Magnolia
          Issue Type: Bug
      Security Level: Public
    Affects Versions: 4.5
            Reporter: Robert Šiška
            Assignee: Robert Šiška
             Fix For: 4.5.3
         Attachments: templates.png

Requesting pages generates ERRORs in logs, which causes log-parsing tests to fail.



&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Robert Šiška</dc:creator>
    <dc:date>2012-05-24T11:26:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34605">
    <title>[magnolia-dev]  [JIRA] Created: (BUILD-108) Fix and update org.eclipse.m2e lifecycle-mapping</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34605</link>
    <description>&lt;pre&gt;Fix and update org.eclipse.m2e lifecycle-mapping
------------------------------------------------

                 Key: BUILD-108
                 URL: http://jira.magnolia-cms.com/browse/BUILD-108
             Project: Build
          Issue Type: Bug
      Security Level: Public
          Components: poms
    Affects Versions: POMs 23
            Reporter: Federico Grilli
            Assignee: Grégory Joseph
            Priority: Major
             Fix For: POMs24


As we started developing the new UI with Vaadin we got again the infamous Eclipse error "" with gwt-maven-plugin. This is due to the fact that we needed to downgrade to version 2.3.0 as Vaadin depends on gwt 2.3.0 (gwt and gwt-maven-plugin versions are in synch and 2.4.x cannot be used with 2.3.x or viceversa). Also I realized that in pom 23 I mistakenly inverted goals for maven-javadoc-plugin and gwt-maven-plugin, namely I set goal "resources" for javadoc and "javadoc" for resources.

&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Federico Grilli</dc:creator>
    <dc:date>2012-05-24T08:44:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34604">
    <title>[magnolia-dev]  [JIRA] Created: (MGNLWEBDAV-30) 10(?) seconds delay before templates are updated (blossom paragraphs with templates stored in jcr)</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34604</link>
    <description>&lt;pre&gt;10(?) seconds delay before templates are updated (blossom paragraphs with templates stored in jcr)
--------------------------------------------------------------------------------------------------

                 Key: MGNLWEBDAV-30
                 URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-30
             Project: Magnolia WebDAV Module
          Issue Type: Bug
    Affects Versions: 1.0.1
            Reporter: Tomas Brimor
            Priority: Major


Using the webdav module to edit templates stored in the JCR which is used by blossom paragraphs it takes about 10 seconds until the template is actually the updated version when reloading the web page.




&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Tomas Brimor</dc:creator>
    <dc:date>2012-05-24T08:44:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34601">
    <title>[magnolia-dev]  Discussion: magnolia lastAction and Publication-Date</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34601</link>
    <description>&lt;pre&gt;Hi everyone,

I recently filed a bug: http://jira.magnolia-cms.com/browse/MAGNOLIA-4415
which was closed as "Not an Issue".
However, Jan encouraged me to post this issue to the user list for discussion, which I am now doing.

The error I posted was this: When activating, magnolia activates the content "as is", and then sets the "lastAction" metadata field on the author instance after activation.
This means that the values of the "lastAction" metadata field differ between author and public instances, with the public instance always trailing "one activation behind" the author instance with respect to the "lastAction" field.

We noticed this error because we use the "lastAction" field to implement sorting by publication date, and were getting different sort-order on author and public instances.

Jan has proposed 2 solutions, which will work for us, but IMHO they are more workarounds than final solutions.

Jan writes: "lastAction date in meta data is value meant for Magnolia internal use only and is used on auth&lt;/pre&gt;</description>
    <dc:creator>Unger, Richard</dc:creator>
    <dc:date>2012-05-23T14:24:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34594">
    <title>[magnolia-dev]  [JIRA] Created: (MAGNOLIA-4418) Keypair updating function uses relative paths</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34594</link>
    <description>&lt;pre&gt;Keypair updating function uses relative paths
---------------------------------------------

                 Key: MAGNOLIA-4418
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4418
             Project: Magnolia
          Issue Type: Bug
      Security Level: Public
    Affects Versions: 4.5
            Reporter: Robert Šiška
            Assignee: Robert Šiška
             Fix For: 4.5.3


On some deployments (Jetty in integration tests, for example), the SystemProperty.getProperty() returns relative path resulting in SecurityUtil.updateKeys() saving into the wrong location.

SecurityUtil.updateKeys() should convert the path to the absolute path before saving.



&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Robert Šiška</dc:creator>
    <dc:date>2012-05-22T14:08:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34593">
    <title>[magnolia-dev]  [JIRA] Created: (MGNLSTK-957) Internal link component throws freemarker exception if target is not available</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34593</link>
    <description>&lt;pre&gt;Internal link component throws freemarker exception if target is not available
------------------------------------------------------------------------------

                 Key: MGNLSTK-957
                 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-957
             Project: Magnolia Standard Templating Kit
          Issue Type: Bug
          Components: demoproject
    Affects Versions: 2.0.2
            Reporter: Frank Sommer
            Assignee: Philipp Bärfuss


Tested on demoauthor instance. Try to reference a not existing page in a internal link component and a freemarker stack trace will occure.

{{stkFunctions.getReferencedContent(content, "link", RepositoryConstants.WEBSITE)}} throws an uncatched runtime exception.

&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Frank Sommer</dc:creator>
    <dc:date>2012-05-22T13:14:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34592">
    <title>[magnolia-dev]  [JIRA] Created: (MGNLSTK-956) Glossary model can not add letter sub pages</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34592</link>
    <description>&lt;pre&gt;Glossary model can not add letter sub pages
-------------------------------------------

                 Key: MGNLSTK-956
                 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-956
             Project: Magnolia Standard Templating Kit
          Issue Type: Bug
          Components: demoproject
    Affects Versions: 2.0.2
            Reporter: Frank Sommer
            Assignee: Philipp Bärfuss


The mode of the glossary info.magnolia.module.templatingkit.templates.GlossaryTemplateModel throws an exception, if a letter sub page is not available. The model can not add the letter node automatically.

I tested it successfully on the demo author instance.

&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Frank Sommer</dc:creator>
    <dc:date>2012-05-22T13:08:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34591">
    <title>[magnolia-dev]  [JIRA] Created: (BUILD-107) Update Maven site layouts</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34591</link>
    <description>&lt;pre&gt;Update Maven site layouts
-------------------------

                 Key: BUILD-107
                 URL: http://jira.magnolia-cms.com/browse/BUILD-107
             Project: Build
          Issue Type: Improvement
      Security Level: Public
          Components: poms
            Reporter: Grégory Joseph
            Assignee: Grégory Joseph
             Fix For: POMs24


* use common header (see http://dev.magnolia-cms.com)
* use current slogan "yes, we're open"

&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Grégory Joseph</dc:creator>
    <dc:date>2012-05-22T12:38:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34588">
    <title>[magnolia-dev]  [JIRA] Created: (BUILD-105) buildnumber plugin's support for Git is half-baked</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34588</link>
    <description>&lt;pre&gt;buildnumber plugin's support for Git is half-baked
--------------------------------------------------

                 Key: BUILD-105
                 URL: http://jira.magnolia-cms.com/browse/BUILD-105
             Project: Build
          Issue Type: Bug
          Components: poms
            Reporter: Grégory Joseph
            Assignee: Grégory Joseph
            Priority: Major
             Fix For: POMs24


The branch name is not resolved: http://jira.codehaus.org/browse/MBUILDNUM-87 (upgrading to 1.1 does not help)
Revision number works, so we can derive the branch from that, but it's just silly.

&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Grégory Joseph</dc:creator>
    <dc:date>2012-05-22T11:20:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34587">
    <title>[magnolia-dev]  [JIRA] Created: (MGNLSTK-955) Impossible to edit an Event Overview component</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34587</link>
    <description>&lt;pre&gt;Impossible to edit an Event Overview component
----------------------------------------------

                 Key: MGNLSTK-955
                 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-955
             Project: Magnolia Standard Templating Kit
          Issue Type: Bug
          Components: paragraphs
    Affects Versions: 2.0.x
            Reporter: Samuel Schmitt
            Priority: Critical
             Fix For: 2.0.3
         Attachments: Screen Shot 2012-05-22 at 9.48.09 AM.png

Open this page http://demoauthor.magnolia-cms.com/demo-project/news-and-events/events-overview.html
and try to edit the Event Overview component.

The "next/prev month" links are hover the button of the edit bar... so no way to click on the edit bar buttons.


&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Samuel Schmitt</dc:creator>
    <dc:date>2012-05-22T07:56:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34584">
    <title>[magnolia-dev]  ContentSecurityFilter CallBack Configuration</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34584</link>
    <description>&lt;pre&gt;Hi everyone,

is it possible to configure the ContentSecurity Filter Callback so that it returns instead of the magnolia-login  form a 403 Http Error?

Thanks and best regards

Dominik

&lt;/pre&gt;</description>
    <dc:creator>Dominik Berger (via Magnolia Forums</dc:creator>
    <dc:date>2012-05-21T14:58:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34580">
    <title>[magnolia-dev]  filters-2.0.235.jar - is it necessary?</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34580</link>
    <description>&lt;pre&gt;Hello Magnolia Developers,

Magnolia 4.4.6 EE Bundle contains the JAR "filters-2.0.235.jar". This contains image and math classes from com.jhlabs.
However, a quick search through the magnolia code shows that the import "jhlabs" is used only in the imaging module test-classes.

My Question:

-          Is it safe to remove the JAR "filters-2.0.235.jar" ?

-          Did I miss something? Is this JAR used by some other module?

-          Could you remove JARs needed only for testing from the official bundle releases?
That would make the releases more compact, and help to minimize class conflict type errors.

Background info:
I have a conflict with the jcaptcha library, which also includes the jhlabs classes. I'm trying to serve captchas from Magnolia, and have rewritten the magnolia captcha module to work with our version.

Thanks &amp;amp; regards from Vienna,

Richard




----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
&lt;/pre&gt;</description>
    <dc:creator>Unger, Richard</dc:creator>
    <dc:date>2012-05-21T12:48:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34578">
    <title>[magnolia-dev]  [JIRA] Created: (MGNLSTK-954) HTML generated by the component "teaser group -  horizontal tabbed" is not align with the HTML of STK prototype</title>
    <link>http://comments.gmane.org/gmane.comp.cms.magnolia.devel/34578</link>
    <description>&lt;pre&gt;HTML generated by the component "teaser group -  horizontal tabbed" is not align with the HTML of STK prototype
---------------------------------------------------------------------------------------------------------------

                 Key: MGNLSTK-954
                 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-954
             Project: Magnolia Standard Templating Kit
          Issue Type: Bug
          Components: paragraphs
    Affects Versions: 2.0.x
            Reporter: Samuel Schmitt
            Assignee: Philipp Bärfuss
             Fix For: 2.0.3
         Attachments: horizontalTabbedArea.ftl

STK prototype and HTML generated by any STK elements must be aligned.

The links generated by {{stkTeaserHorizontalTabbed}}, the ones letting you navigate to another teaser, have all the same css class {{on ui-disabled js-selected}}
But in the prototype only the selected link has this class. The others have no class.

Replacing the following template script {{/templating-kit/components/teasers/hor&lt;/pre&gt;</description>
    <dc:creator>JIRA (on behalf of Samuel Schmitt</dc:creator>
    <dc:date>2012-05-21T11:50:07</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.cms.magnolia.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.cms.magnolia.devel</link>
  </textinput>
</rdf:RDF>

