On 1 July 2011 15:47, Paul Harris <[email protected]> wrote:
On 1 July 2011 15:28, Vincent Massol <[email protected]> wrote:
On Jul 1, 2011, at 9:14 AM, Paul Harris wrote:
On 1 July 2011 14:59, Vincent Massol <[email protected]> wrote:
On Jul 1, 2011, at 8:41 AM, Paul Harris wrote:
On 1 July 2011 14:36, Marius Dumitru Florea <[email protected]>wrote:
Hi Paul,
On 07/01/2011 05:38 AM, Paul Harris wrote: > Hi again, > > I wanted to delete all the packages I had uploaded for Import. > > If I go through the XWikiPreferences --> Import, I can't see any packages... > the link is: > > http://HOST/xwiki/import/XWiki/XWikiPreferences?editor=globaladmin§ion=I... > > However, if I go to this page (which I can't remember how I got there): > http://host/xwiki/import/XWiki/Import?editor=globaladmin§ion=Import > > I can see a dozen packages that I uploaded. > > Whats the difference between these two imports, and how do I get to the > second one without knowing the link beforehand? (I think I found it via the > Document Index and scanning hundreds of docs in the XWiki space)
XWiki.Import page is not part of the standard XAR. I don't have it on a fresh XE 3.1. Moreover, the XARs I import are attached to XWiki.XWikiPreferences page so for me the Import administration section is synchronized with http://host/xwiki/bin/view/XWiki/XWikiPreferences?viewer=attachments
XWiki.Import page is either from your previous XE 2.6 (which you said you upgraded to 3.1) or was created by an application (extension) that you have installed on top of 3.1.
Hope this helps, Marius
I started with a blank web folder and extracted 3.1...
How can I find out where it came from?
The pages are not saved on the file system but in the database. So if you haven't modified your DB when you upgraded you still have the same data there.
You could just delete the XWiki.Import page IMO.
Shouldn't this have been handled by the Migration thing?
Ideally yes but that's not implemented at the moment.
We're introducing the notion of extension manager to manager extensions and as part of it there'll be a notion of an application (ie a set of pages) and when an app is installed or upgraded it'll have the ability to run some script.
I am struggling with a similar design issue in one of my projects. I am currently thinking along the lines that: * If there are a set of pages, keep them bundled together - don't unwrap them. The moment you unwrap them, and someone modifies a page, then you can't upgrade the package without stomping on the changes.
* Allow pages to be extracted if the user really wants to hack.
* Don't store configuration within pages that are part of an upgrade. Instead, separate structure and data, and put the data in a configuration file (or a configuration page that is NOT EVER overwritten during an upgrade). Then, if there is an upgrade, add a mechanism to upgrade the configuration file IF REQUIRED.
How can I find other pages are lingering?
You could compare the two XARs using either http://extensions.xwiki.org/xwiki/bin/view/Extension/XAR+Diff+Application or the Admin Tools which reuse this XAR Diff app code (http://extensions.xwiki.org/xwiki/bin/view/Extension/AdminTools).
urgh
What I did was Imported and opened the latest 3.1.xar to see the contents. What I found interesting is that there are a lot of pages (eg Blog.BlogParameters) that are not listed in the Blog-Space-Index Are these pages? How does one see the hidden pages? thanks Paul