gmane.comp.cms.magnolia.devel

JIRA (on behalf of Philippe Marschall | 15 Jul 17:06

[magnolia-dev] [JIRA] Created: (MAGNOLIA-2263) creating or importing a virtualURIMapping folder requires a restart to become active

creating or importing a virtualURIMapping folder requires a restart to become active
------------------------------------------------------------------------------------

                 Key: MAGNOLIA-2263
                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2263
             Project: Magnolia
          Issue Type: Bug
          Components: core
    Affects Versions: 3.5.8
            Reporter: Philippe Marschall
            Assignee: Philipp Bracher
            Priority: Minor
         Attachments: config.modules.data.virtualURIMapping.xml

h2.Steps to Reproduce
# in the configuration folder of your module create a virtual URI mapping
## create a folder virtualURIMapping
## create a content node eg 'virtualUriTest'
### add a node data named 'class' with the value 'info.magnolia.cms.beans.config.DefaultVirtualURIMapping'
### add a node data named 'fromUri' with value '/virtualUriTest'
### add a node data named 'toUri' with value 'redirect:/.magnolia/pages/adminCentral.html'
# alternatively imported the attached xml file to /modules/data

h2.Observed Behavior
# the virtual URI mapping is not active, a restart is required

h2.Expected Behavior
# the virtual URI mapping is active without a restart

--

--

(Continue reading)

headers

JIRA (on behalf of Gregory Joseph | 15 Jul 18:19

[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=17128#action_17128
] 

Gregory Joseph commented on MAGNOLIA-2152:
------------------------------------------

It is likely to be related to indexing. Indexing happens (by default) asynchronously - and queries are
based on those indexes.
Could you post some details about your jackrabbit/oracle configuration ?

> 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:
> {code}
> //element(*, mgnl:content) [@someLongAttribute and @someLongAttribute != 0]

(Continue reading)