Hi Kristian
Sorry for being late.
It seems that Magnolia expects the underlying JCR implementation to
make changes made in one session visible to all other sessions
immediately on a save. We noticed while testing Magnolia with Jeceira
that when you create a new page in Magnolia and then procee
Cool I will check in later
Philipp
On 09.09.2005, at 11:13, Andreas Brenk (JIRA) wrote:
[ http://jira.magnolia.info/browse/MAGNOLIA-540?page=all ]
Andreas Brenk updated MAGNOLIA-540:
---
Attachment: MultipartRequestFilter.java
Okay, I replaced the Mu
THANKS,
I noticed your effort, but was not able to test and check in yet. I
will do this as soon I have time.
Philipp
On 09.09.2005, at 16:38, Felipe Curty do Rego Pinto wrote:
Hi people,
I posted that issue into Jira. It is solved.
Take a look, I fixed two bugs into magnolia and now it
The pages are created in the tree handler which uses the tree control.
See:
- info.magnolia.module.admininterface.AdminTreeMVCHandler.createNode()
- info.magnolia.cms.gui.control.Tree.createNode(String label, String
itemType)
Philipp
On 10.09.2005, at 16:31, Felipe Curty do Rego Pinto wrote:
1) Change the combo (Read only, Read/Write, Deny) for a group of
checkbox with all the access (add, set, remove, write, syndicate,
read)
May be, it allow a more flexible security structure.
Yep!
2) Add the possibility of a role provider. It would be a configuration
that able you to hand
Philipp Bracher wrote:
It seams that jackrabbit does not always update the session properly
(there are maybe still some bugs), perhaps we can change to the model
you proposed.
see http://issues.apache.org/jira/browse/JCR-155
Hopefully this bug is fixed. However, I still suffered from this bug
[ http://jira.magnolia.info/browse/MAGNOLIA-540?page=comments#action_11265
]
Fabrizio Giustina commented on MAGNOLIA-540:
Just a comment: I already tried replacing cos with commons-fileupload months
ago, during the dependencies cleanup work, but
It seams that jackrabbit does not always update the session properly
(there are maybe still some bugs), perhaps we can change to the model
you proposed.
see http://issues.apache.org/jira/browse/JCR-155
The fix is very new (7. September)
Hopefully this bug is fixed. However, I still suffered
On 9/12/05, Michael Aemisegger wrote:
> Hopefully this bug is fixed. However, I still suffered from this bug, although
> in the magnolia build, maven claims to download a jackrabbit-snapshot.jar.
>
> Which jackrabbit version does maven download? I didn't get it. I remember
> Fabrizio having said,
[ http://jira.magnolia.info/browse/MAGNOLIA-540?page=all ]
Andreas Brenk updated MAGNOLIA-540:
---
Attachment: MultipartRequestFilterTest.java
A first go at a JUnit test case.
> problematic com.oreilly.servlet package license terms
>
Fabrizio Giustina wrote:
In the past we were used to link the snapshot version in project.xml
but this becomes problematic when changes in jackrabbit require a
change to the repository configuration file (and this will happen
again soon, due to the restructuring that's going on for the
jackrabbit
[ http://jira.magnolia.info/browse/MAGNOLIA-540?page=comments#action_11267
]
Andreas Brenk commented on MAGNOLIA-540:
I forgot: the test case uses commons-httpclient 3.0-rc3. So you have to update
the dependency.
Multi-value properties are not yet
Philipp Bracher wrote:
It seams that jackrabbit does not always update the session properly
(there are maybe still some bugs), perhaps we can change to the model
you proposed.
see http://issues.apache.org/jira/browse/JCR-155
The fix is very new (7. September)
Any chance to upgrade to the
Does jeceira follow the copy-on-read strategy?
No and that's the problem. Should we be compatible to such
repositories too?
Sorry for the hasty reading: Jeceira uses copy-on-read!
To avoid any confusion:
jackrabbit follows copy-on-write
Yes, I know.
Philipp, from your statement I conclude
Hi Philipp,
This is true: see info.magnolia.cms.security.SessionAccessControl
But I think you can patch easily the methods:
Then you must patch ContentRepository.getHierachieManager too.
See below - the change is really minimal.
I think, we should not do this, since this would not solve t
Ampersand can not be edited properly in tree column 'title'
---
Key: MAGNOLIA-548
URL: http://jira.magnolia.info/browse/MAGNOLIA-548
Project: magnolia wcm
Type: Bug
Components: gui-admin
Versions: 2.1 Fi
16 matches
Mail list logo
