That's the thing.. I would have expected this to happen if I imported either
the base groups or base users. Luckily I have been doing the upgrade tests
on my own pc - so I've run through it a couple of times now.
Any included (or otherwise parsed) pages with protected instructions,
notably groovy
underbad wrote:
Sorry being a pain..
Is there no way of avoiding this? It effectively stops me from upgrading
past my current version of xwiki.
You shouldn't need this at all. Why are you saying it is not working?
Programming rights are lost in three cases:
1. You save the affected document
Thanks,
In this case I use XWiki.Admin as the user for all developments. Other than
importing the XAR (did not updating standard groups and users), only change
is the new xwiki war to the newer version.
On Fri, Dec 12, 2008 at 11:01 AM, Sergiu Dumitriu ser...@xwiki.com wrote:
underbad wrote:
On Fri, Dec 12, 2008 at 12:01 PM, Sergiu Dumitriu ser...@xwiki.com wrote:
underbad wrote:
Sorry being a pain..
Is there no way of avoiding this? It effectively stops me from upgrading
past my current version of xwiki.
You shouldn't need this at all. Why are you saying it is not working?
On Fri, Dec 12, 2008 at 1:22 PM, Jean-Vincent Drean
jean-vinc...@drean.org wrote:
On Fri, Dec 12, 2008 at 12:01 PM, Sergiu Dumitriu ser...@xwiki.com wrote:
underbad wrote:
Sorry being a pain..
Is there no way of avoiding this? It effectively stops me from upgrading
past my current version of
Sorry being a pain..
Is there no way of avoiding this? It effectively stops me from upgrading
past my current version of xwiki.
underbad wrote:
Seems when you upgrade from 1.4.1 to 1.6.1 then you need to resave all
pages that have restricted calls in them? For example, I use .search()
in
Seems when you upgrade from 1.4.1 to 1.6.1 then you need to resave all pages
that have restricted calls in them? For example, I use .search() in some
of my pages, but after upgrading the xwiki they won't work until I resave
the pages.
On upgrading, I did not import the XWiki.Admin user (this
