I am facing problem with XWiki export, it creates backup.xar (20,396 KB) file but when I try to unzip that file it can not unzip the file and gives error "Unexpected end of archive".. however export works fine if i export only original installed XWiki without any changes. Do you have any idea how to fix the issue ?
____________________________________________________________________________________
Got a little couch potato?
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&…
All,
A space selection combo box could be useful.
I've revised the New Page panel code (see below) to provide functionality to
create a new page or space based upon a page template (from a Template space
or where ever). Its not perfect, but maybe it can help. If you or anyone can
do any better then let me know! Paste it into the New Page panel code area
to see it work.
Also I'd like a pop up (or something) to appear when a user clicks on a ?
link so they can select a template to base the new page on - but I don't
know how that could be coded.
Creating a series of page from a template page (by reading the template
pages the top level template page) would also be a good feature or having a
template space from which to create new space e.g. template project
spaces/pages which can be reused for new projects, etc.
Best Regards,
Richard
Revised New Page panel code:
#if($hasedit)
#panelheader($msg.get("Create"))
<form method="post" action="$doc.getURL("view", "xpage=create")"
onsubmit="cancelCancelEdit()">
<br>Create:
<div class="left">
<select name="tocreate" class="panelselect">
<option value="page">New Page\*</option>
<option value="space">New Space</option>
<option value="post">New Blog Post</option>
</select>
</div>
#set($spaces = $xwiki.spaces)
#set($currentspace = "Templates")
#set($currentdoc = "-- N/A --")
#if ($request.sourcedoc && $request.sourcedoc.indexOf(".") > 0)
#set($currentspace =
$request.sourcedoc.substring(0,$request.sourcedoc.indexOf(".")))
#set($index = $request.sourcedoc.indexOf(".") + 1)
#set($currentdoc = $request.sourcedoc.substring($index))
#end
#if ($request.selspace) #set($currentspace = $request.selspace) #end
<br><div class="left">Space:</div><br>
<select
name="selspace"
onchange="location='?selspace=' + this.value;">
<option value="$!{request.selspace}">$!{request.selspace}</option>
#foreach($space in $spaces)
#if ($space == $currentspace)
<option value="${space}" selected>${space}</option>
#else
<option value="${space}">${space}</option>
#end
#end
</select>
<br>Page Template:
<select name="template">
<option value="" selected="selected">-- N/A --</option>
#foreach($subdoc in $xwiki.getSpaceDocsName("$currentspace"))
#if ($currentdoc == ${subdoc})
<option value="${currentspace}.${subdoc}" selected>$subdoc</option>
#else
#if ($request.selspace)
<option value="${request.selspace}.${subdoc}">$subdoc</option>
#else
<option value="${currentspace}.${subdoc}">$subdoc</option>
#end
#end
#end
</select>
<br>Page/Space Name:
<div class="left">
<input type="text" name="title" value="Title" class="panelinput"
style="margin:left;" onfocus="if(this.value=='Title') this.value=''"
onblur="if(this.value=='') this.value='Title'"/>
</div>
<div class="padded centered" style="text-align:center;">
<input type="submit" class="button" style="margin:left;"
value="$msg.get("create")"/>
</div>
<p style="font-size:0.75em;padding-left:8px;">*New pages are created in
current space</p>
</form>
#panelfooter()
#end
-----Original Message-----
From: notifications-bounces(a)xwiki.org
[mailto:notifications-bounces@xwiki.org]On Behalf Of Vincent Massol
(JIRA)
Sent: 01 October 2007 11:33
To: notifications(a)xwiki.org
Subject: [xwiki-notifications] [Issue] Updated: (XAPANELS-22) Add space
selection combo box to the "Create" Panel
[
http://jira.xwiki.org/jira/browse/XAPANELS-22?page=com.atlassian.jira.plugin
.system.issuetabpanels:all-tabpanel ]
Vincent Massol updated XAPANELS-22:
-----------------------------------
Fix Version/s: 1.2 M2
(was: 1.2 M1)
> Add space selection combo box to the "Create" Panel
> ---------------------------------------------------
>
> Key: XAPANELS-22
> URL: http://jira.xwiki.org/jira/browse/XAPANELS-22
> Project: XWiki Panels Application
> Issue Type: Improvement
> Affects Versions: 1.0 RC4
> Reporter: Vincent Massol
> Fix For: 1.2 M2
>
>
> Right now it's very difficult for new user to find out how to create a
page in a given space.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.xwiki.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
notifications mailing list
notifications(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/notifications
Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail
is confidential. It may also be legally privileged. It is intended only for
the stated addressee(s) and access to it by any other person is
unauthorised. If you are not an addressee, you must not disclose, copy,
circulate or in any other way use or rely on the information contained in
this e-mail. Such unauthorised use may be unlawful. We may monitor all
e-mail communications through our networks. If you have received this e-mail
in error, please inform us immediately on +44 (0) 1749 672081 and delete it
and all copies from your system. We accept no responsibility for changes to
any e-mail which occur after it has been sent. Attachments to this e-mail
may contain software viruses which could damage your system. We therefore
recommend you virus-check all attachments before opening. A business of
Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business
Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No.
868273
I've been running XWiki 1.1 milestone 3 (the latest at the time I installed
it) for some time now. We've made a couple of alterations to the skin (we
did it right in the albatross skin instead of making our own -- shame on
us). We also edited a couple of pages. Most importantly, we've added TONS
of content.
I'm struggling to understand the best way to upgrade to the latest release,
XWiki 1.1.1. I think it is the case that I can leave my DB as is and the
new XWiki engine will run against its syrcture (or, hibernate will
automatically update it).
However, I want ot be sure to pick up any changes made in the default set
of XWiki pages. The latest release notes page says to link at the list of
hcanged pages to import, but I saw no such list.
But even beyond that, should I be installing/extracting to a separate
directory and copying my changes over, pointing ti my existing DB, and then
importing those pages known to have changed (once I can identify those)?
I've done some searching but can't seem to find an overall upgrade
strategy.
Thoughts?
Regards,
Brian.
-----------------------------------------
CONFIDENTIALITY STATEMENT:
This e-mail transmission contains information that is intended to
be confidential. It is intended only for the addressee named
above. If you receive this e-mail in error, please do not read,
copy, or disseminate it. If you are not the intended recipient,
any disclosure, copying, distribution or use of the contents of
this information is prohibited. Please reply to the message
immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer
system. Your assistance in correcting this error is appreciated.
The XWiki development team is pleased to announce the release of
XWiki Enterprise 1.1.1.
This is a bug fix release. It's a stable release. Everyone using
XWiki Enterprise 1.1 should upgrade to it.
Bugs fixed in 1.1.1:
* Fullscreen doesn't work on IE6 or IE7
* Cache issue on new document creation in multilingual mode
* Document change notification not sent for new documents
* Code macro doesn't like groovy code
* Backlinks are not working anymore
* Cannot delete Space with a simple quote in its name
* Lucene Plugin does not index creation or modification dates
* Import with history throws exception from time to time
* Panels Wizard not saving panels correctly
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise111
Thanks
-The XWiki dev team
Hi,
I have just tried migrating my 1.0 installation to 1.1. (MSQLDB, on WinXP)
Using a copy of the XWiki 1.0 MSQL Database and pointing at it from my new
V1.1 installation.
Currently, I encounter a strange phenomenon, that I haven't seen discussed
anywhere:
All links that were specified without Space name (e.g. [test>test] instead
[test>myspace.test] break, since appearently XWiki is looking for these
pages in the XWIKI Space rather than the space of the parent document.
$doc.space is set correctly but all (space-local) links refer to the xwiki
space: eg.
http://localhost:8080/xwiki/bin/edit/XWiki/XWikiNeu2?parent=XWiki.gleeb
rather then:
http://xwiki/xwiki/bin/view/Architektur/XWikiNeu2 (as seen in our original
V1.0 installation)
Using #includeForm("XWiki.WebHomeTemplate") also caused the XWiki Space to
be used although the including page is in another space.
Nothing appearent in the xwiki.log.
Did I screw up the configuration somehow?
Any pointers of what is wrong are appreciated.
Regards,
Gunter
-------------------------------------------------------------------------------
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
-------------------------------------------------------------------------------
my company is running XWiki old and using databse MYSql... they want me to migrate it to new XWiki....can you please suggest how to accomplish it
bikram
____________________________________________________________________________________
Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545469
ok I will try that...
thanks
bikram
----- Original Message ----
From: Vincent Massol <vincent(a)massol.net>
To: XWiki Users <users(a)xwiki.org>
Sent: Friday, September 28, 2007 11:54:56 AM
Subject: Re: [xwiki-users] migration from old XWiki to XWiki new
Hi Bikram,
On Sep 28, 2007, at 8:39 PM, BIKRAMJIT SINGH wrote:
my company is running XWiki old and using databse MYSql... they want me to migrate it to new XWiki....can you please suggest how to accomplish it
Could you try following the information in the release notes and see if you can get it to work. If not please post here and we'll find the solution together and improve the release notes.
Thanks
-Vincent
____________________________________________________________________________________
Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545469
I have been testing out Xwiki for a couple of months now and I am very
impressed with it. One feature that I can't seem to find though is the
ability to include one section of a page instead of a whole page. Is this
supported? Or is there a way to write a macro that does this?
-SJB
Ok, I see two items:
1. Current issues with inability to move content from for example
word document even using WYSIWYG editor and disappearing texts doesn't
allow me to get the pages with the same content in xWiki as they were in
word document
2. I don't want to use wiki at least now for coding something and
want to use only what it provides as it's assured on the site but in
order to make it work for some cases I need to read DevGuide as well.
3. I'm newbie for wikis since never edited wiki pages before just
used as web pages for getting information but what I see that seems
xWiki IRC channel is only for dev discussions or for questions that can
be handled by one answer and providing 4-5 sentences for getting one
answer which will work is not enough.
As I said that xWiki is great tool and perhaps best one for wiki but
these items don't allow me to get xWiki working now in they way as I
want and since I'm newbie I don't expect much, just get the same content
from existing documents.
That cwould be good If WYSIWYG editor will be fixed and no questions
will appear about their simple usage so they will not take dev team to
answer.
All IMHO.
Have a good weekend.
Best regards,
Juri.
________________________________
From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org] On Behalf
Of Vincent Massol
Sent: Thursday, September 27, 2007 9:34 PM
To: XWiki Users
Subject: Re: [xwiki-users] xwiki experience
Hi Juri,
On Sep 27, 2007, at 7:46 PM, Artamonov, Juri wrote:
HI All,
just would like to share my first week usage experience with xwiki.
That's great tool and helped me at work but what I see I need to know it
better and deeper. This is not easy to follow WYSIWYG editor since its
usage leads to unexpected behaviour and incorrect result preview page
sometimes even with disappearing the text and I need to follow macros,
velocity code to get what I want. Summarizing, it's ok if only me will
change the pages but will not be ok for others in the company since they
don't want to spend time on velocity and introducing macros for xwiki
which leads to that I can't say to them please go and edit that page by
yourself.
We know that the wysiwyg editor has bugs that need to be fixed. See JIRA
for the known bugs.
If you discover a new bug please file it so that it can be fixed.
Just so that you know we're also working on a new implementation of the
wysiwyg editor using a different architecture (GWT) which will make it
easier to maintain.
Thanks
-Vincent