[magnolia-dev] Magnolia 4.5 sneak preview !

Hey peeps,

Magnolia developers have been very busy in the last few months putting a new page editing UI together for
4.5. The green bars that we had a love/hate relationship with (don't we all?) have been tamed a little.

We wanted to first write up some of the ideas and intentions behind these changes - those which have been
included in this version that is, keeping in mind the grand scheme of things, where this version is a
stepping stone towards 5.0 - but we figured we might as well just drop it here and now. I'm sure y'all will
have interesting feedback, and the developer team will read and react to your suggestions and questions
as they come.

I'm going to try and not say *too much* about what has changed and what hasn't, but everyone would be grateful
if you took a few minutes of your time to try a snapshot out. In particular, this one bundle here is actually
in a "known state" - we know it works, we know it still has a lot of polishing to do, but we also think this is the
right time to integrate some of your feedback.

You can grab it here: http://hudson.magnolia-cms.com/job/magnolia-bundle_trunk/1925/info.magnolia$magnolia-tomcat-bundle/artifact/info.magnolia/magnolia-tomcat-bundle/4.5-20120209.173147-466/magnolia-4.5-SNAPSHOT-tomcat-bundle.zip

Just a hint (I've just been bitten myself) - to navigate within your site, you might need to switch to preview mode.

In particular, we'd like to hear what you think about the new "experience" of editing a page. Put yourself in
an editor's shoes and tell us what you think, comparing to your 4.4 or prior experience.

I suggest we simply use this thread for feedback, but if you feel more comfortable in private, feel free to
email me at greg at magnolia-cms dot com.

Cheers !

--

-- 
Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=939ca472-a01f-4178-a619-0b25aa5c3647
(Continue reading)

[magnolia-dev] [JIRA] Created: (MAGNOLIA-3968) Improve saveHandler for multiSelect controls to handle single-valued properties

Improve saveHandler for multiSelect controls to handle single-valued properties
-------------------------------------------------------------------------------

                 Key: MAGNOLIA-3968
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3968
             Project: Magnolia
          Issue Type: Improvement
      Security Level: Public
          Components: core
    Affects Versions: 4.4.6, 4.4.5, 4.4.4, 4.4.3, 4.4.2
            Reporter: Richard Unger
            Assignee: Philipp Bärfuss

We are faced with the following problems, which are really 2 instances of the same problem:

1. We changed a control in one of our dialogs to use multiselect rather than single-select (originally the
customer wanted one category, then changed their mind and wanted multiple categories to be assignable to
the content)

2. We observed that data imported from XML had problems with the multiselect for categories

The problem is that the multiselect control does not work if the node already contains a single-valued
property of the same name.
In case 1. the single-valued properties were created by the editors using the old dialog definition.
In case 2. the single-valued properties were created by the XML-Import-Bug (see MAGNOLIA-3035)

In both cases the behaviour is the same: when an editor wants to edit the content using the dialog, the
existing (single-valued) property is not displayed in the multiselect control. If the user sets new
values in the multiselect control, the dialog cannot be saved as there is an exception in the saveHandler
when it finds the existing single-valued property.
(Continue reading)

[magnolia-dev] [JIRA] Created: (BLOSSOM-81) Templates with empty dialogs should not be displayed

Templates with empty dialogs should not be displayed
----------------------------------------------------

                 Key: BLOSSOM-81
                 URL: http://jira.magnolia-cms.com/browse/BLOSSOM-81
             Project: Magnolia Blossom Module
          Issue Type: Improvement
            Reporter: Tobias Mattsson
            Assignee: Tobias Mattsson
             Fix For: 2.0

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

[magnolia-dev] [JIRA] Created: (DEVDECT-5) Provide special channel only for Smartphones - not Tablets

Provide special channel only for Smartphones - not Tablets
----------------------------------------------------------

                 Key: DEVDECT-5
                 URL: http://jira.magnolia-cms.com/browse/DEVDECT-5
             Project: Magnolia Device Detection Module
          Issue Type: Improvement
            Reporter: Samuel Schmitt
            Assignee: Samuel Schmitt

- rename channel & variation: "mobile" -> "smartphone"
- rename "MobileChannelResolver" -> "SmartphoneChannelResolver" (resolve only if (isMobile && !isTablet))
- adapt configuration accordingly

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

[magnolia-dev] [JIRA] Created: (EXTIDX-12) Investigate integration with Google Custom Search Engine

Investigate integration with Google Custom Search Engine
--------------------------------------------------------

                 Key: EXTIDX-12
                 URL: http://jira.magnolia-cms.com/browse/EXTIDX-12
             Project: External indexing and search engine services
          Issue Type: Task
            Reporter: Grégory Joseph
            Assignee: Grégory Joseph
             Fix For: 1.0

See http://code.google.com/intl/en/apis/customsearch/docs/dev_guide.html
There even seems to be a generated Java library for the api, see: http://code.google.com/p/google-api-java-client/wiki/APIs#CustomSearch_API

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3967) core: after 4.4.6 update to 4.5 adminCentral is no longer accessible


     [
http://jira.magnolia-cms.com/browse/MAGNOLIA-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Federico Grilli updated MAGNOLIA-3967:
--------------------------------------

    Description: After performing an update from 4.4.6 to 4.5, trying to access AdminCentral always returns
the following page
{{http://localhost:8080/magnoliaAuthor/demo-project/members-area/login.html}} which
eventually issues a 403 HTTP error. It looks like the wrong HttpClientCallback is selected at startup.
See also attached securityCallback filter config after update.  (was: After performing an update from
4.4.6 to 4.5, trying to access AdminCentral always returns the following page
{{http://localhost:8080/magnoliaAuthor/demo-project/members-area/login.html}} which
eventually issues a 403 HHTP error. It looks like the wrong HttpClientCallback is selected at startup.
See also attached securityCallback filter config after update.)

> core: after 4.4.6 update to 4.5  adminCentral is no longer accessible
> ---------------------------------------------------------------------
>
>                 Key: MAGNOLIA-3967
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3967
>             Project: Magnolia
>          Issue Type: Bug
>      Security Level: Public
>          Components: core
>    Affects Versions: 4.5
>            Reporter: Federico Grilli
>            Assignee: Federico Grilli
>            Priority: Blocker
(Continue reading)

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3967) core: after 4.4.6 update to 4.5 adminCentral is no longer accessible


     [
http://jira.magnolia-cms.com/browse/MAGNOLIA-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Federico Grilli updated MAGNOLIA-3967:
--------------------------------------

    Affects Version/s: 4.5

> core: after 4.4.6 update to 4.5  adminCentral is no longer accessible
> ---------------------------------------------------------------------
>
>                 Key: MAGNOLIA-3967
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3967
>             Project: Magnolia
>          Issue Type: Bug
>      Security Level: Public
>          Components: core
>    Affects Versions: 4.5
>            Reporter: Federico Grilli
>            Assignee: Federico Grilli
>            Priority: Blocker
>             Fix For: 4.5
>
>         Attachments: securityCallbackFilterAfterUpdate.png
>
>
> After performing an update from 4.4.6 to 4.5, trying to access AdminCentral always returns the following
page {{http://localhost:8080/magnoliaAuthor/demo-project/members-area/login.html}} which
eventually issues a 403 HHTP error. It looks like the wrong HttpClientCallback is selected at startup.
(Continue reading)

[magnolia-dev] [JIRA] Created: (MAGNOLIA-3966) AuditLoggingManager#log(String, String[]) should not use NPE for control flow

AuditLoggingManager#log(String, String[]) should not use NPE for control flow
-----------------------------------------------------------------------------

                 Key: MAGNOLIA-3966
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3966
             Project: Magnolia
          Issue Type: Improvement
      Security Level: Public
            Reporter: Daniel Lipp
            Assignee: Daniel Lipp
             Fix For: 4.5

Calling AuditLoggingManager#log(String, String[]) will internally throw and catch a NPE. This is not
good design and can be cumbersome when debugging with a breakPoint on NPE (ton's of unwanted stops e.g. in Tests).

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

[magnolia-dev] [JIRA] Created: (BLOSSOM-80) Bridge magnolia components into Spring BeanFactory

Bridge magnolia components into Spring BeanFactory
--------------------------------------------------

                 Key: BLOSSOM-80
                 URL: http://jira.magnolia-cms.com/browse/BLOSSOM-80
             Project: Magnolia Blossom Module
          Issue Type: New Feature
            Reporter: Tobias Mattsson
            Assignee: Tobias Mattsson

Implement using a xml namespace tag. <blossom:bridge-magnolia-components />

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

[magnolia-dev] [JIRA] Created: (BLOSSOM-79) Remove ServletContextExposingContextListener as its no longer necessary

Remove ServletContextExposingContextListener as its no longer necessary
-----------------------------------------------------------------------

                 Key: BLOSSOM-79
                 URL: http://jira.magnolia-cms.com/browse/BLOSSOM-79
             Project: Magnolia Blossom Module
          Issue Type: Improvement
            Reporter: Tobias Mattsson
            Assignee: Tobias Mattsson
             Fix For: 2.0

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

[magnolia-dev] [JIRA] Created: (MGNLGROOVY-53) commons coded dep is provided by http

commons coded dep is provided by http
-------------------------------------

                 Key: MGNLGROOVY-53
                 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-53
             Project: Magnolia Groovy Module
          Issue Type: Task
            Reporter: Federico Grilli
            Assignee: Federico Grilli
            Priority: Major
             Fix For: 1.2

exclude commons-codec from http-client dep as it is provided by core otherwise it ends up in the bundle.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------


Gmane