Hello,
I've XWiki 2.0rc2 instance and I want to update to 2.0.5 version.
I find empty FAQ here:
http://www.xwiki.org/xwiki/bin/view/FAQ/WhoCanIUpdateXWIKIFromAnOlderVersion
I'd like to update it on myself experience.
But before I've one question at the end of my email on xar import.
1st/ re-deploy war (easy part)
By chance we didn't update any files excepted xwiki.cfg and hibernate.cfg.xml.
So I did the following:
- zip current webapp/xwiki folder
- remove webapp/xwiki folder
- deploy xwiki-enterprise-web-2.0.5.war in webapp/xwiki
- report my old xwiki.cfg and hibernate.cfg.xml configuration to the new one
2nd/ import xar (difficulties start here)
First, I import the full xar without any question: whao, everything is broken.
Do not forget to backup your database before upgrade!
After restoration, I decide to write a small script based on curl to
export same xar as the one I want to import:
#!/bin/bash
XWIKI_BASE_URL=http://localhost:8080
if [[ $# -ne 2 ]]; then
echo usage $0 login password
exit 1
fi
EXPORT_XAR="?format=xar&name=Current"
for page in `jar tvf xwiki-enterprise-wiki-2.0.5.xar | sed -ne
"/\/.*xml/{s/.*\s\(\S\+\)\/\(\S\+\).xml/\1.\2/ p}"`; do
EXPORT_XAR="${EXPORT_XAR}&pages=${page}"
done
curl -b cookies.txt -c cookies.txt
-d"j_username=$1&j_password=$2&j_rememberme=true&submit=Log-in"
${XWIKI_BASE_URL}/xwiki/bin/loginsubmit/XWiki/XWikiLogin
curl -b cookies.txt -c cookies.txt
${XWIKI_BASE_URL}/xwiki/bin/export/Main/WebHome${EXPORT_XAR} -o
Current.xar
Whatever I used the best diff tool (Beyond Compare IMHO), it is not so
easy to check if difference are good or not: I need other way.
Thanks to RESTful API, I write a second script which check page
version: version 1.1 was never updated from previous xar version:
#!/bin/bash
XWIKI_BASE_URL=http://localhost:8080
for page in `jar tvf xwiki-enterprise-wiki-2.0.5.xar | sed -ne
"/\/.*xml/{s/.*\s\(\S\+\)\/\(\S\+\).xml/\1\/pages\/\2/ p}"`; do
version=`curl -s -b cookies.txt -c cookies.txt
${XWIKI_BASE_URL}/xwiki/rest/wikis/xwiki/spaces/$page | sed -ne
"/version/{s/.*version>\(.*\)<\/version.*/\1/ p}"`
if [[ $version != "1.1" ]]; then
echo $page $version UPDATED
fi
done
Cool, only 8 updated pages:
Main/pages/WebHome 144.1 UPDATED
XWiki/pages/XWikiUserSheet 4.1 UPDATED
XWiki/pages/XWikiAdminGroup 4.2 UPDATED
XWiki/pages/XWikiPreferences 78.1 UPDATED
XWiki/pages/LiveTableResults 2.1 UPDATED
XWiki/pages/XWikiAllGroup 34.1 UPDATED
XWiki/pages/WebPreferences 3.2 UPDATED
XWiki/pages/LiveTableResultsMacros 2.1 UPDATED
All other pages can be updated without any check :-D
6 pages of 8 should be not updated:
- Main.WebHome: it is our own main page
- XWiki.AdminGroup and XWikiAllGroup: list Admin users and users
- XWiki.XWikiUserSheet, we apply a patch to display user
contribution: not updated
- XWiki.LiveTableResults and XWiki.LiveTableResultsMacros, I check
with my diff tool: there is a tag object inside.should not updated it.
But I block on XWiki.XWikiPreferences and XWiki.WebPreferences.
I want our own preferences, I should not update
But new preferences may be added
My diff tool find them too different.
Could I keep my old preferences or do I have to merge?
Regards,
Arnaud.
For some reason, I chose db-names for my virtual hosts that were
descriptive, but ugly and not meant to be seen in the UI.
Unfortunately, in Xwiki Enterprise 2.X, the new colibri skin exposes this
name e.g. "host_xe_foo_dot_com" on the left-hand-side top-menu.
As a quick hack to suppress this new feature, I cloned "colibri" into a new
skin "exlibri" (runner up names: NorwegianBlue and DeadParrot :-) ) and
changed colibri.css
ROOT-golem-85-.../java/xe-210> diff -c skins/exlibri/colibri.css.~1~
skins/exlibri/colibri.css
*** skins/exlibri/colibri.css.~1~ 2009-12-08 17:37:58.000000000 -0800
--- skins/exlibri/colibri.css 2009-12-31 13:55:51.082007773 -0800
***************
*** 916,921 ****
--- 916,926 ----
text-transform: uppercase;
}
+ /* NPM: get rid of annoying ServerHost name, leaving all other top-menus
the same */
+ div#tmWiki a.tme strong {
+ display: none;
+ }
+
.actionmenu .hasIcon a.tme {
padding-left: 20px;
}
Niels
http://nielsmayer.com
Hi everybody,
I've a problem with Xeclipse Plugin (xwiki-eclipse-feature-1.2-rc-1).
The connection to xwiki is OK
If I do a refresh in the navigator, the list of spaces appears, but no pages
inside.
For each space I've this error :
Cannot find navigator content extension (using triggerPoints) for object
"org.xwiki.eclipse.core.model.XWikiEclipseSpaceSummary@1d501c5c" parent
path: "org.xwiki.eclipse.core.DataManager@1c10945d". Check that you have an
expression for this object in a navigatorContent triggerPoints or
enablement.
I'm on Mac OS X 10.6.2 and Eclipse Galileo.
Any idea ?
Thanks,
Emmanuel
--
View this message in context: http://n2.nabble.com/Xeclipse-plugin-the-Eclipse-Navigator-don-t-show-the-p…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi,
I notice that when you import a XAR file with 'users' these users are not automatically added to XWikiAllGroup?
Is this by design, and if so how do you restore them as members of this group (have > 100 users)
Is there a script or macro to add users to a group?
Gerritjan
Hello experts,
I and stats to some page,the code is as following:
#if($xwiki.statsService.enabled)
{{include document="Stats.Document"/}}
#end
it works,but when I log out, there is error message :
Caused by: org.xwiki.rendering.macro.MacroExecutionException: Current
user doesn't have view rights on document [Stats.Document]
at org.xwiki.rendering.internal.macro.include.IncludeMacro.execute(IncludeMacro.java:139)
So how can I add rights permission code?
Thansk & Best Regards
Tom
Hi,
Is there a reference document describing the default classes of xwiki
I'm specifically interested in XWiki.XWikiUsers.
In the version we have developped in (1.6) i see a property (or class attribute) Country
In the new version 2.1.1 I do not see that property (or attribute)
Is this because our developer has customized the class in 1.6
or does the class editor not show all the properties of the class in 2.1.1 ?
Gerritjan
Hello,
How do we launch openoffice server please ??
Please help Logica to respect the environment by not printing this email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei, die Umwelt zu sch�tzen. / Por favor ajude a Logica a respeitar o ambiente nao imprimindo este correio electronico.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
They are not using XWiki... yet!
Cheers,
Ricardo
-------- Original Message --------
Subject: [Obo-discuss] CFP: The Future of the Web for Collaborative
Science (FWCS 2010) at WWW'10
Date: Fri, 11 Dec 2009 16:10:54 +0000
From: Jun Zhao <jun.zhao(a)zoo.ox.ac.uk>
Reply-To: obo-discuss(a)lists.sourceforge.net
To: undisclosed-recipients:;
[apologies for cross-posting]
=================================================================================================
CALL FOR PAPERS - International Workshop on The Future of the Web for
Collaborative Science 2010
=================================================================================================
The First International Workshop on The Future of the Web for
Collaborative Science (http://esw.w3.org/topic/HCLS/WWW2010/Workshop),
co-located with WWW'10, April 27 or 28 2010, Raleigh, NC, USA
---------------------------------------------------
INTRODUCTION
The Web was originally invented with the physics community in mind, but
rapidly expanded to include other scientific disciplines, in particular
the health care and life sciences. By the mid 1990s the Web was already
being used to share data by biomedical professionals and
bioinformaticians. The Web continues to be immensely important to these
fields, however use cases have expanded considerably. Researchers are
now looking to share extremely large data sets on the Web, extract
insights from vast numbers of papers cross sub-disciplines, and use
social networking tools to aggregate data and engage in scientific
discussion. Furthermore, individuals are beginning to store their
medical records online, and some are sharing their genetic makeup in a
bid to find others with a similar profile. These use cases are pushing
the boundaries of what is currently possible with the Web. This half-day
workshop will present how scientists are currently using the Web, and
discuss the functionality that is required to make the Web an ideal
platform for both cutting edge scientific collaboration and for managing
health care related data.
The goals of this workshop are the following:
* Foster innovation in applying the latest web technologies to
collaborative HCLS
* Explore HCLS specific requirements for collaborating on the web, e.g.
trust, privacy, intellectual property, knowledge management, and the
scale and diversity of data
* Learn about the latest developments in data modeling, tools and
technologies for web-based collaborative science
* Bridge communication and knowledge transfer between the HCLS and web
communities
---------------------------------------------------
TOPICS FOR PAPER SUBMISSION
We would encourage submission of papers covering the following topics:
* Web 2.0 applications for large, heterogeneous and complex data sets
* Models for collaborative scientific annotations
* Tools and applications for aggregating information across web sites
* Provenance, attribution, trust, and intellectual property
* Policy for data access, sharing, and anonymization
We seek three kinds of submissions:
* Full technical papers: up to 10 pages
* Short technical and position papers: up to 5 pages
* Demo description: up to 2 pages
---------------------------------------------------
SUBMISSIONS
Submitted papers will be refereed by at least three members the Program
Committee. Accepted papers will be published on the workshop web site.
All submissions must be formatted using the WWW2010 templates
(http://www2010.org/www/authors/submissions/formatting-guidelines/). The
address for the online submission system will be published shortly.
---------------------------------------------------
IMPORTANT DATES:
* Submission deadline- February 15, 2010
* Notification of acceptance - March 8, 2010
* Camera-ready version - March 22, 2010
* Workshop date - April 27 or 28, 2010
---------------------------------------------------
Workshop Chairs
Jun Zhao, Oxford University
Kei Cheung, Yale University
M. Scott Marshall, Leiden University Medical Center / University of
Amsterdam
Eric Prud'hommeaux, W3C
Susie Stephens, Johnson & Johnson Pharmaceutical Research & Development
---------------------------------------------------
Programme Committee
* Christopher Baker, University of New Brunswick
* John Breslin, GUI Galway
* Simon Buckingham Shum, Open University
* Annamaria Carusi, Oxford University
* Helen Chen, Agfa Healthcare
* Paolo Ciccarese, Harvard University
* Tim Clark, Harvard Medical School
* Anita de Waard, Elsevier
* Michel Dumontier, Carleton University
* Lee Feigenbaum, Cambridge Semantics
* Timo Hannay, Nature
* William Hayes, BiogenIdec
* Ivan Herman, W3C
* Vipul Kashyap, Cigna
* Nikesh Kotecha, Stanford University
* Phil Lord, University of Newcastle
* Robin McEntire, Merck
* Parsa Mirhaji, University of Texas
* Mark Musen, Stanford University
* Vit Novacek, DERI
* Alex Passant, DERI
* Elgar Pichler, AstraZeneca
* Rosalind Reid, Harvard University
* Patrick Ruch, University of Applied Sciences Geneva
* Daniel Rubin, Stanford
* Matthias Samwald, DERI, Ireland // Konrad Lorenz Institute for
Evolution and Cognition Research, Austria
* Susanna Sansone, EBI
* Nigam Shah, Stanford University
* Amit Sheth, Wright State University
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Obo-discuss mailing list
Obo-discuss(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/obo-discuss
Hi all,
I am sorry bothering you, however I am not able to get the task manager application up and running in a wiki farm:
- Installing it in the local wiki fails because of security issues (velocity errors).
- Installing it in the central wiki fails because the pages, like "new task" are not available in the local wiki
... May I kindly ask for any hint?
Thanks a lot
mb