gmane.comp.cms.magnolia.devel

JIRA (on behalf of Ellie Hadyoon | 15 Jul 16:28

[magnolia-dev] [JIRA] Created: (MGNLDATA-35) Documentation Required

Documentation Required
----------------------

                 Key: MGNLDATA-35
                 URL: http://jira.magnolia.info/browse/MGNLDATA-35
             Project: Magnolia Data Module
          Issue Type: Improvement
            Reporter: Ellie Hadyoon
            Assignee: Philipp Bracher

Hi, 

We have decided to use your 'Data Module' on a project for a client but unfortunately cannot find any
documentation for this. Can you please point me in the right direction for this or forward me any
information you have. 

Many thanks, 

Ellie 

--

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

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/

(Continue reading)

headers

JIRA (on behalf of Philippe Marschall | 15 Jul 16:41

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2152) QueryManager and JCR browser seem to have different view on repository


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

Philippe Marschall updated MAGNOLIA-2152:
-----------------------------------------

              Summary: QueryManager and JCR browser seem to have different view on repository  (was: Strage Issue with
Attribute Values in JCR Queries)
    Affects Version/s: 3.5.8
                           (was: 3.5.7)

More descriptive title

> QueryManager and JCR browser seem to have different view on repository
> ----------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2152
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2152
>             Project: Magnolia
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.8
>            Reporter: Philippe Marschall
>            Assignee: Philipp Bracher
>
> We have a very strange issue with querying custom page attributes. We have a custom page dialog that sets
some custom page properties. These attributes are ad hoc and not defined in some sort of schema. We then
have observation code that queries the JCR for pages with these attributes and certain values. Our
queries look like this:

(Continue reading)

headers

JIRA (on behalf of Philippe Marschall | 15 Jul 16:45

[magnolia-dev] [JIRA] Issue Comment Edited: (MAGNOLIA-2152) QueryManager and JCR browser seem to have different view on repository


    [
http://jira.magnolia.info/browse/MAGNOLIA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125#action_17125
] 

pmm edited comment on MAGNOLIA-2152 at 7/15/08 4:45 PM:
-----------------------------------------------------------------------

Some more information:

The behaviour we are observing is that the QueryManager sometimes seems to have a different view on the JCR
than the JCR browser until "something" happens and they are in synch again.

To bring them in synch again we have worked out the following procedure:
- export the nodes
- delete then nodes
- restart the server
- import the nodes

Simply exporting, deleting and then importing did not fix the issue.

We don't observe this behavior in the development environment with Derby but on test / production with Oracle.

      was (Author: pmm):
    Some more information:

The behaviour we are observing is that the QueryManager sometimes seems to have a different view on the JCR
than the JCR browser until "something" happens and they are in synch again.

To bring them in synch again we have worked out the following procedure:

(Continue reading)

headers

JIRA (on behalf of Philippe Marschall | 15 Jul 16:45

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2152) QueryManager and JCR browser seem to have different view on repository


    [
http://jira.magnolia.info/browse/MAGNOLIA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125#action_17125
] 

Philippe Marschall commented on MAGNOLIA-2152:
----------------------------------------------

Some more information:

The behaviour we are observing is that the QueryManager sometimes seems to have a different view on the JCR
than the JCR browser until "something" happens and they are in synch again.

To bring them in synch again we have worked out the following procedure:
- export the nodes
- delete then nodes
- restart the server
- import the nodes

Simply exporting then importing did not fix the issue.

We don't observe this behavior in the development environment with Derby but on test / production with Oracle.

> QueryManager and JCR browser seem to have different view on repository
> ----------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2152
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2152
>             Project: Magnolia
>          Issue Type: Bug

(Continue reading)

headers

JIRA (on behalf of Philippe Marschall | 15 Jul 16:45

[magnolia-dev] [JIRA] Issue Comment Edited: (MAGNOLIA-2152) QueryManager and JCR browser seem to have different view on repository


    [
http://jira.magnolia.info/browse/MAGNOLIA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125#action_17125
] 

pmm edited comment on MAGNOLIA-2152 at 7/15/08 4:46 PM:
-----------------------------------------------------------------------

Some more information:

The behaviour we are observing is that the QueryManager sometimes seems to have a different view on the JCR
than the JCR browser until "something" happens and they are in synch again.

To bring them in synch again we have worked out the following procedure:
- export the nodes
- delete then nodes
- restart the server
- import the nodes

Simply exporting, deleting and then importing did not fix the issue.

We don't observe this behavior in the development environment with Derby but on test / production with Oracle.

We observed this behavior both in the website and data workspace.

      was (Author: pmm):
    Some more information:

The behaviour we are observing is that the QueryManager sometimes seems to have a different view on the JCR
than the JCR browser until "something" happens and they are in synch again.

(Continue reading)