This is still refactoring concept even if it might not appear in the
rename UI :)
Such a listener would probably make more sense in the refactoring module.
On Wed, Apr 20, 2016 at 5:37 PM, Eduard Moraru wrote:
> Not sure refactoring is the right place.
>
> IMO, it should
Not sure refactoring is the right place.
IMO, it should be generically handled by some listener for moving any
document having a class inside it (and fixing all the objects). But for
that we would first need to have a DocumentRenam(ing/ed)Event being
triggered by the rename operation(s).
Thanks,
On Wed, Apr 20, 2016 at 9:43 AM, Thomas Mortagne
wrote:
> The main issue is probably that moving a class is not that simple
> right now, when you move the class defining all the application
> entries they all end up broken (they keep referencing the old class
>
The main issue is probably that moving a class is not that simple
right now, when you move the class defining all the application
entries they all end up broken (they keep referencing the old class
location). We need to add support for it in the refactoring module.
On Tue, Apr 19, 2016 at 10:21
Hi,
> On 19 Apr 2016, at 22:02, Ryszard Łach wrote:
>
> Hi.
>
> Is there a way to migrate (xwiki 7.2.4) an application created via
> AppWithinMInutes to another node in the same wiki tree, with all documents
> created by the app ? The easy way (move parent document
Hi.
Is there a way to migrate (xwiki 7.2.4) an application created via
AppWithinMInutes to another node in the same wiki tree, with all documents
created by the app ? The easy way (move parent document with all children)
doesn't seem to work.
TIA,
R.