Oh, i see...
I've created the database user in advance to make sure he has the proper tablespace for data. It worked for my "wikitemplate" user.
Think i'll change the wiki manager skript just to inform me about already present database users and allow the creation of the virtual wiki.
Thanks a lot,
Rudi
>Hi,
>
>>On Mon, Sep 29, 2008 at 3:55 PM, Rudolf Tronicek <Tronicek at web.de> wrote:
>>
>>
>> Hi,
>>
>> i've got a problem with Virtual Wiki Manager.
>>
>> After deletion of a virtual wiki named "wikiit" it's not possible to create a new one with this name.
>>
>> $xwiki.wikimanager.isWikiNameAvailable("wikiit") returns "false".
>
>This methods looks directly into the database so I think the problem
>here is that there as some problem at delete and the database has not
>been deleted.
>
>>
>> I'm using XE 1.5.2, Wiki Manager 1.4, JBoss AS 4.2.1, Oracle 9iR2 Database.
>>
>> Where can i make the old name available again (document / object)? I've searched the database but hit no record - looking up velocity code was not successfull.
>>
>> Thanks for any help,
>>
>> Rudolf Tronicek
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
Dan Svoboda wrote:
> Hi Jerome,
>
> Something just occurred to me.
>
> In the tutorial, you say: "XWiki Workspaces XAR contains several pages
> that needs to be saved with programming rights to work properly."
>
> But then, the only alteration to the XAR that you describe is to
> change the backupPack property from true to false. What are these
> "several pages", and how do I change the programming rights?
I have no complete list of such pages as of today, I'll try to make it
when I have some time. The back up pack property affects the fact that
the author of imported page is the original one (the one written in the
XAR) when set to true, or the user actually doing the import, when set
to false.
You can give programming rights from the RMUI of the manager wiki.
(http://platform.xwiki.org/xwiki/bin/view/Features/RightsManagement)
Regards,
Jerome
>
> Cheers,
>
> Dan
>
> Begin forwarded message:
>
>> *From: *Dan Svoboda <dsvoboda(a)structbio.pitt.edu
>> <mailto:dsvoboda@structbio.pitt.edu>>
>> *Date: *September 29, 2008 10:44:29 AM EDT
>> *To: *jerome(a)xwiki.com <mailto:jerome@xwiki.com>
>> *Subject: **Re: virtual workspaces*
>>
>> Jerome,
>>
>> Thanks for taking the time to write the tutorial.
>>
>> I believe that I've followed the instructions to the letter, but
>> still have the same result as before.
>>
>> I was a bit confused by the instruction to:
>> "Connect to your newly create wiki, and *login with the credentials
>> of an administrator of the manager wiki*."
>>
>> After creating the empty wiki from the wiki manager (logged in as
>> Admin), I then go directly to the new, empty wiki. I'm now able to
>> import the archive that was prepared according to your instructions,
>> by navigating to "/bin/admin/XWiki/Import". (Am I already logged in
>> correctly, or do I have to log out and re-log in as some other user
>> name? I tried xwiki:Admin, and that gave an error.)
>>
>> After importing the archive, I still can't create workspaces, the
>> Admin user is still listed as a Simple Member, and the arrows to
>> promote members to Power User or Global Admin are still not present.
>>
>> Cheers,
>>
>> Dan
>>
>>> Hello Dan,
>>>
>>> Thank you for your interest in XWiki Workspaces.
>>> I took advantage of your question to write a complete tutorial on
>>> how to
>>> setup a XWiki Workspaces farm:
>>> http://workspaces.xwiki.org/xwiki/bin/view/AdminGuide/VirtualXWikiWorkspace…
>>>
>>> You had all the initial steps right, so you can jump directly to the
>>> last section
>>> (http://workspaces.xwiki.org/xwiki/bin/view/AdminGuide/VirtualXWikiWorkspace…)
>>> where I explain that several pages from the Workspaces XAR needs to be
>>> saved with programming rights, and how you can "prepare" the XAR to
>>> have
>>> this done automatically when importing it.
>>>
>>> A last step would be to create a template wiki or XAR package for a
>>> smoother creation of XWiki Workspaces virtual instances. Unfortunately
>>> we are sometimes facing an issue when doing this with XWiki Workspaces,
>>> so I will only add this section once this is resolved.
>>>
>>> Regards,
>>> Jerome.
>>
>>>
>>>
>>> Dan Svoboda wrote:
>>>> First time question.
>>>>
>>>> I've been using workspaces with success for several months. I'm
>>>> trying
>>>> to have several virtual xwiki-workspaces sites under the enterprise
>>>> manager system.
>>>>
>>>> Here's what I've done:
>>>>
>>>> 1. created a site from a war file using xwiki-workspaces-web-1.2-
>>>> milestone-1.war
>>>> 2. added the enterprise manager jar file to WEB-INF/lib
>>>> 3. added a line in xwiki.cfg to activate enterprise manager plugin;
>>>> set xwiki.virtual=1
>>>> 4. created 'xwiki' database in mysql, gave xwiki user all rights on
>>>> everything
>>>> 5. started tomcat, and navigated to bin/main/view/WebHome
>>>> 6. clicked on 'Administration' link, and arrived at the import page
>>>> 7. imported xwiki-enterprise-manager-wiki-administrator-1.3.xar
>>>> 8. created new site, giving Admin user all rights on new site,
>>>> uploading xwiki-workspaces-wiki-1.2-milestone-1.xar
>>>> 9. navigate to new site, and log in as Admin
>>>>
>>>> I used the workspaces war file for the main application since it uses
>>>> v1.5.2 and enterprise manager war file would only supply v1.5.1
>>>>
>>>> Here's the problem:
>>>>
>>>> While the Admin user on the workspaces site can edit things,
>>>> workspaces cannot be created. Moreover, on the user administration
>>>> page, Administrator is listed as a simple member. Also, the arrows to
>>>> promote members to power user or global admin are missing. I'm able
>>>> to
>>>> create users, but they're simple users as well.
>>>>
>>>> Thank you in advance for any help you can provide.
>>>>
>>>> Dan
>>>
>
>
>
Hi,
i've got a problem with Virtual Wiki Manager.
After deletion of a virtual wiki named "wikiit" it's not possible to create a new one with this name.
$xwiki.wikimanager.isWikiNameAvailable("wikiit") returns "false".
I'm using XE 1.5.2, Wiki Manager 1.4, JBoss AS 4.2.1, Oracle 9iR2 Database.
Where can i make the old name available again (document / object)? I've searched the database but hit no record - looking up velocity code was not successfull.
Thanks for any help,
Rudolf Tronicek
"50 erste Dates" mit Adam Sandler u. Drew Barrymore kostenlos anschauen!
Exklusiv für alle WEB.DE Nutzer. *http://www.blockbuster.web.de* [http://www.blockbuster.web.de]
First time question.
I've been using workspaces with success for several months. I'm trying
to have several virtual xwiki-workspaces sites under the enterprise
manager system.
Here's what I've done:
1. created a site from a war file using xwiki-workspaces-web-1.2-
milestone-1.war
2. added the enterprise manager jar file to WEB-INF/lib
3. added a line in xwiki.cfg to activate enterprise manager plugin;
set xwiki.virtual=1
4. created 'xwiki' database in mysql, gave xwiki user all rights on
everything
5. started tomcat, and navigated to bin/main/view/WebHome
6. clicked on 'Administration' link, and arrived at the import page
7. imported xwiki-enterprise-manager-wiki-administrator-1.3.xar
8. created new site, giving Admin user all rights on new site,
uploading xwiki-workspaces-wiki-1.2-milestone-1.xar
9. navigate to new site, and log in as Admin
I used the workspaces war file for the main application since it uses
v1.5.2 and enterprise manager war file would only supply v1.5.1
Here's the problem:
While the Admin user on the workspaces site can edit things,
workspaces cannot be created. Moreover, on the user administration
page, Administrator is listed as a simple member. Also, the arrows to
promote members to power user or global admin are missing. I'm able to
create users, but they're simple users as well.
Thank you in advance for any help you can provide.
Dan
Hi,
i just tried to install the DocumentTree Plugin but it doesn't seem to work.
i followed the instructions here.
http://code.xwiki.org/xwiki/bin/view/Plugins/DocumentTreePlugin
Downloaded the jar doctree-1.5.jar here
http://code.xwiki.org/xwiki/bin/view/Snippets/ChildPageSnippet
But when i restart my xwiki it doesn't work anymore.
In the log i find:
INFO: Starting service Catalina
23.09.2008 07:57:21 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.16
23.09.2008 07:57:21 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive ROOT.war
23.09.2008 07:57:21 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error in dependencyCheck
java.util.zip.ZipException: invalid entry size (expected 1538260992 but got
25 bytes)
at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:393)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:165)
at java.util.jar.JarInputStream.read(JarInputStream.java:194)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
at java.util.jar.JarInputStream.getBytes(JarInputStream.java:105)
at java.util.jar.JarInputStream.<init>(JarInputStream.java:82)
at java.util.jar.JarInputStream.<init>(JarInputStream.java:60)
at
org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:373)
at
org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:184)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4167)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
So it seems the jar provided for download is not working or did i make an
mistake?
Thanks
Helmut
--
View this message in context: http://n2.nabble.com/DocumentTree-Plugin-tp1111723p1111723.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi,
Could somebody explain to me what risk we have when Xwiki application
developped on windows/mySql/jetty would be deployed on
linux/postgresql/apache/tomcat?
I have the "naieve" assumption that if the xwiki out-of-the-box
application runs on this Linux environment it can run "any" xwiki
application?
Gerritjan
On 9/26/08, Paul Libbrecht <paul(a)activemath.org> wrote:
>
>
> Le 26-sept.-08 à 15:28, Bey Youcef a écrit :
>
>> Note that you can also define in the administration-settings XWiki
>> documents that are resource-bundles, they will override the things below.
>> Somewhere close to these settings you can also define the supported
>> languages (and define whether it's multilingual!).
>>
>> Thanks so much.
>>
>> Translating all strings is time-consuming, the best way thus to get quick
>> idea about the arabic localization is MT (Machine Translation).
>> The MT can be used for the experimentation.
>>
>
> Honestly, it's a donkey work but if you type fast it should not take you
> more than 3-4 hours for XWiki I think.
> Curriki translation took a few days to our translators and it is several
> orders of magnitudes bigger.
As we are starting to collaborate together, I don't appreciate the word
*donkey*!
No harm.
But it seems that you're not award about the advantage of MT nowadays. It
can be used to save more than 50% in some fields. Personally, I translated
web sites using Google MT into Arabic. Let me say that it helped to save
more 50% of translation time (especially for editing) and the quality is
quit acceptable! The statistical MT are also more powerful.
As first step, I want to show the technical problems that can be produced
when shifting into Arabic, especially those related to RTL, css, ... The
translation as well as revision can be done efficiently by occasional
translators (e.g me and other communities). I'm not worried about this
issue.
> How about the translation of installation Wiki pages? They are not
>> in the resources! For example, where could we find strings of the main
>> pages
>> when XWiki is installed for the first time?
>>
>> The web-pages are content, they are wiki-editable.
>> Once multilingual, your wiki always offers you the possibility to
>> translate a page at editing time, that's what you want to use.
>>
>> This mean that the end-users have to translate these pages? I don't thing
>> so!
>> Not all of them are translators or willing to translate.
>>
>
> All users? Just one... the translator...
The translation must be done in translation environments rather in the
application itself.
Even XWiki offers open editing, it is not computer-aided translation tools
to be used for translation. Translating a Wiki page from English into
another language in Wiki editor is not good method. The source and target
document must be displayed in the same interface. This concept is proposed
by Alen Melby since 1982, when he proposed the concept of translation memory
(TM). This is very known for professional translators.
Strings must be stored in separated resource files, which can be translated
in specific environments like OmegaT, Pootle, poedit, etc.
Mozilla is translated into 70 languages in high quality. The translation is
never done in Mozilla itself, especially for documents. All strings are
saved in ".po" files and in object formats. This is why the translation is
efficient!!
The localization, once done, it must be done for all text in documentation
>> and GUI.
>>
>
> it is well known that translating documentation is long. It generally is
> delayed ;-))
Not exactly. It depends on size of documents. The translation of XWiki pages
(not documentation) can be done in acceptable time. I'm talking about the
Wiki pages, like the main page, and some help pages.
The scenario is simple : strings must be stored in separte files.
Translators recover these files and translate them in computer-aides
translation environments (e.g OmegaT). Once the translation is done, these
files are integrated into XWiki. The last step is QA!
The XWiki was not designed for localization that's why the resources
properties are used for conversion. In fact, these resources can't be used
for managing format of document. They don't support metadata...This is one
among another reasons for which LISA proposed the XLIFF standard.
Anyway, thanks for your help!
Youcef
Hi,
Is there a way to add users and manipulate permission via the XWiki API?
Can someone point me to documentation on how to do it (if it exists)?
Thanks,
Evan
Hi Paul,
On Fri, Sep 26, 2008 at 9:17 AM, Paul Libbrecht <paul(a)activemath.org> wrote:
> Hello Youcef,
>
>
> Le 26-sept.-08 à 02:42, Bey Youcef a écrit :
>
>> I installed the "xwiki-workspaces-distribution-hsqldb-1.0" version with
>> windows installer. As I'm using XWiki since many years, I'ven't faced any
>> problems with new versions.
>>
>> But I'm trying to find the application resources that you pointed out in
>> your mail. I couldn't found them. May I have to download and install them
>> to
>> get the localized version.
>>
>
> It's in (webapps)/xwiki/WEB-INF/lib/xwiki-core-xxxx.jar
>
> I think that it's easy for you to expand this jar, copy the properties
> files there to WEB-INF/classes and edit them there.
>
> I believe a restart is needed at every change.
>
> Note that you can also define in the administration-settings XWiki
> documents that are resource-bundles, they will override the things below.
> Somewhere close to these settings you can also define the supported
> languages (and define whether it's multilingual!).
Thanks so much.
Translating all strings is time-consuming, the best way thus to get quick
idea about the arabic localization is MT (Machine Translation).
The MT can be used for the experimentation.
>
>
> Another important things related to its localisation, It is known that
>> localization is not only limited on the translation of resources files
>> (Key=Value). The process is little bit more complex: How about the
>> consistency between documents and GUI strings and those of the system
>> messages?
>>
>
> XWiki tries its best... it is not fully achievable though depending on the
> availability of content.
Ok.
>
> How about the translation of installation Wiki pages? They are not
>> in the resources! For example, where could we find strings of the main
>> pages
>> when XWiki is installed for the first time?
>>
>
> The web-pages are content, they are wiki-editable.
> Once multilingual, your wiki always offers you the possibility to translate
> a page at editing time, that's what you want to use.
This mean that the end-users have to translate these pages? I don't thing
so! Not all of them are translators or willing to translate.
The localization, once done, it must be done for all text in documentation
and GUI.
>
> [...] The encoding of these files are not UTF-8, then how it will be
>> possible to
>> manage multilingual content by shifting from one language to another
>> during
>> runtime?
>>
>
> You definitely should make sure everything is utf-8 (e.g. in xwiki.cfg).
> Note that IRIs are not fully achieved though so document names with some
> arabic letters will give very ugly URLs (and may often fail) (note: URL is
> not title!).
> For some old legacy reasons there are still xwiki distributions that run
> other encodings, in particular iso-8859-1, but you should not take these in
> account or?
>
> There's one more dimension of Arabic translation which may byte and I am
> interested to see if that one is doable:
> left-to-right layout.
> I do not think XWiki developers have considered it thorougly thus far and
> only a good translation first approach can see what are the limits. The
> velocity files may need to be changed I think.
Thank you very much.
I'll let you know as soon as I do progress.
-- Youcef
Hi,
Could somebody explain to me what risk we have when Xwiki application
developped on windows/mySql/jetty would be deployed on
linux/postgresql/apache/tomcat?
I have the "naieve" assumption that if the xwiki out-of-the-box
application runs on this Linux environment it can run "any" xwiki
application?
Gerritjan
