G'day one and all,
I'm looking at using xwiki for our intranet and was wondering how existing
taxonomies can be implemented/imported into xwiki
Regards,
Stephen....
Hi!
We have a problem with the new "Import Office Content" functionality in
XWiki Enterprise 1.9.2.22089.
The problem exists with Internet Explorer 6.0.2800.1106; with Firefox
3.0.7 everything is working fine ....
After copy&paste of some word content into the import office panel some
xml tags are visible in the imported text:
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office"
/>
To reproduce:
1. In Edit mode, selected Import Office Content.
2. In Office Importer, select Clipboard, copy&paste some word text and
select Import. (filter styles / don't filter styles doesn't matter)
3. Preview / Save and view
What is the problem that only Internet Explorer is affected ?
Thanks in advance
Matthias Gsottberger
This might be useful for those wanting to do server administration functions
(start/stop tomcat, reboot, stats, etc) out of an Xwiki doc (make sure your
doc is password protected or more, if it allows people to reboot your
server!; Anything needing root or tomcat user would use /etc/sudoers to
grant specfic permissions to specific programs needed by user
tomcat-ssh-slave):
Input:
> ==== Use Groovy Script run server processes and display result ====
> See [[SshHelperClass?viewer=code]], [[
> http://blog.asyd.net/2008/12/xwiki-cest-decidemment-magique/]]
> ==== Call parseGroovyFromPage("Groovy.SshHelperClass") ====
{{velocity}}
#set( $sshHelper = $xwiki.parseGroovyFromPage("Groovy.SshHelperClass") )
$sshHelper.openSession("127.0.0.1", "22", "tomcat-ssh-slave",
> "/usr/share/tomcat6/.ssh/id_dsa", "")
{{/velocity}}
> ==== Output from 'uname -a'====
##{{velocity}}$sshHelper.runCommand("uname -a"){{/velocity}}##
> ==== Output from 'free' ====
##{{velocity}}$sshHelper.runCommand("free"){{/velocity}}##
> ==== Output from 'ps -l U tomcat-ssh-slave U tomcat U apache' ====
##{{velocity}}$sshHelper.runCommand("ps -l h U tomcat-ssh-slave U tomcat U
> apache"){{/velocity}}##
> ==== Output from 'df -H' ====
##{{velocity}}$sshHelper.runCommand("df -H"){{/velocity}}##
> ==== Output from 'top -b -n 1' ====
##{{velocity}}$sshHelper.runCommand("top -b -n 1"){{/velocity}}##
> ==== Close the connection and exit tomcat-ssh-slave shell ====
warning: if something breaks above, hopefully this will get called otherwise
> we
get a left-over sub-process tomcat-ssh-slave
##{{velocity}}$sshHelper.close(){{/velocity}}##
Output:
> Use Groovy Script run server processes and display result
>
> See SshHelperClass ,
>> http://blog.asyd.net/2008/12/xwiki-cest-decidemment-magique/
>
> *Call parseGroovyFromPage("Groovy.SshHelperClass")*
>
> *Output from 'uname -a'*
>
> Linux ce 2.6.27.29-170.2.78.fc10.x86_64 #1 SMP Fri Jul 31 04:16:20 EDT
>> 2009 x86_64 x86_64 x86_64 GNU/Linux
>
> *Output from 'free'*
>
> total used free shared buffers cached
>
> Mem: 1928992 1778932 150060 0 47272 532128
>
> -/+ buffers/cache: 1199532 729460
>
> Swap: 3866616 78776 3787840
>
> *Output from 'ps -l U tomcat-ssh-slave U tomcat U apache'*
>
> 5 S 92 18792 18788 0 80 0 - 22060 select ? 0:00 sshd:
>> tomcat-ssh-slave@notty
>
> 0 R 92 18879 18792 1 80 0 - 22453 - ? 0:00 ps -l h U tomcatssh-slave U
>> tomcat U apache
>
> 0 S 91 31695 1 0 80 0 - 463955 futex_ ? 7:47 /usr/java/default/bin/java
>> -server -Xms160m -Xmx1024m -XX:PermSize=160m -XX:MaxPermSize=320m ...
>
> *Output from 'df -H'*
>
> Filesystem Size Used Avail Use% Mounted on
>
> /dev/mapper/VolGroup00-LogVol00 242G 26G 204G 12% /
>
> /dev/sda1 200M 15M 175M 8% /boot
>
> tmpfs 988M 353k 988M 1% /dev/shm
>
> *Output from 'top -b -n 1'*
>
> top - 11:17:20 up 2 days, 16:21, 3 users, load average: 0.78, 0.68, 0.56
>
> Tasks: 150 total, 2 running, 148 sleeping, 0 stopped, 0 zombie
>
> Cpu(s): 7.7%us, 1.7%sy, 0.0%ni, 90.2%id, 0.3%wa, 0.1%hi, 0.1%si, 0.0%st
>
> Mem: 1928992k total, 1794420k used, 134572k free, 47304k buffers
>
> Swap: 3866616k total, 78776k used, 3787840k free, 532356k cached
>
> ...
>
>
Special Installation Instructions
To make this run (Fedora Linux):
1. sudo yum install trilead-ssh2 trilead-ssh2-javadoc
2. sudo ln -s /usr/share/java/trilead-ssh2-213.jar
/usr/share/java/tomcat6/trilead-ssh2.jar
3. Make sure "tomcat" user exists in /etc/passwd, and create an additional
uid=92 gid=92 account "tomcat-ssh-slave":
• tomcat:x:91:91:Apache Tomcat:/usr/share/tomcat6:/bin/sh
° "tomcat" user created as "disabled" by installing tomcat6-6.0.18-6.2.fc10
• tomcat-ssh-slave:x:92:92:User for SSH Subprocesses From
Tomcat:/home/tomcat-ssh-slave:/bin/bash
° create this using fedora admin utility 'system-config-users' or by
hand-editing /etc/passwd...
4. sudo passwd -u tomcat
• unlock tomcat account temporarily
5. sudo passwd tomcat
• set password for tomcat account
6. Login to "tomcat" account using SSH from current account terminal.
7. ssh-keygen -t dsa
• Leave "empty for no passphrase" for decrypting the DSA-key produced by
ssh-keygen, although it can be specified as last parameter for
sshHelper.openSession("localhost", "22", "tomcat-ssh-slave",
"/usr/share/tomcat6/.ssh/id_dsa", "").
8. From the "tomcat" account, run "ssh tomcat-ssh-slave(a)127.0.0.1"
• answer Yes: "Are you sure you want to continue connecting (yes/no)? yes"
• enter password for tomcat-ssh-slave set above via system-config-users.
• exit the connection.
• The purpose of this step is to test the account, and init
/usr/share/tomcat6/.ssh/known_hosts
9. sudo cp /usr/share/tomcat6/.ssh/id_dsa.pub
tomcat-ssh-slave/.ssh/authorized_keys
10. From the "tomcat" account, do "ssh tomcat-ssh-slave(a)127.0.0.1" again
• verify that login happens w/o password prompt, which is what happens when
authorized_keys is set to the
public key of the account accessing SSH.
• exit from tomcat-ssh-slave account. It's now ready to run out of tomcat.
11. passwd -l tomcat
• lock the tomcat account from further logins, now that it's been setup and
the dsa public/private keys have been generated.
1. *TODO:* remove password from user tomcat-ssh-slave ('!!' in passwd field
of /etc/shadow) password not needed for login
2. *TODO:* alternately, is there a local customization to ensure certs only
used for login to the account? I know this can be done globally in
/etc/ssh/sshd_config: "PasswordAuthentication no" and "PermitEmptyPasswords
no"
3. *TODO:* for user tomcat-ssh-slave, integrate "limited command processing"
by replacing /bin/sh as login shell with /usr/local/bin/tomcat-ssh-shell (or
equiv):
#!/bin/sh -noprofile
###############################################################################
#
# File: sshslave-shell
# RCS: $Header: $
# Description: Shell to allow execution of remote commands from a tomcat
server.
# For security purposes, this "login" is limited in commands it can
# perform, and runs as a separate user from the tomcat server, separating
# the ability to directly modify tomcat state from the functionality
provided
# by user tomcat-ssh-slave. This shell is run as the "login shell" (via
# /etc/passwd) for account tomcat-ssh-slave, which is accessed via SSH.
# The account is preferably a nonprivileged user account with pid>500, Home
# directory /home/tomcat-ssh-slave must exist, with correct permisssions.
# /home/tomcat-ssh-slave contains scripts referred to via
fully qualified
# filenames in this script. The directory would also store the accounts'
# .ssh settings, keys, etc. Secure, password-less access to the
tomcat-ssh-slave
# account can be achieved by having tomcat's SSH public identity
/usr/share/tomcat6/.ssh/id_dsa.pub
# installed as /home/tomcat-ssh-slave/.ssh/authorized_keys (and
keeping id_dsa secret)
# This would prevent use of tomcat-ssh-slave "account" from being used by
anything
# other than preauthorized accounts.
#
# Here's some example commands:
#
# ssh -x tomcat-ssh-slave(a)127.0.0.1 cleanlog
# ssh -x tomcat-ssh-slave(a)127.0.0.1 getlog
# ssh -x tomcat-ssh-slave(a)127.0.0.1 setdbglvl 'INFO'
# ssh -x tomcat-ssh-slave(a)127.0.0.1 getdbglvl
# ssh -x tomcat-ssh-slave(a)127.0.0.1 tomcat-restart
# ssh -x tomcat-ssh-slave(a)127.0.0.1 apache-restart
# ssh -x tomcat-ssh-slave(a)127.0.0.1 tomcat-start
# ssh -x tomcat-ssh-slave(a)127.0.0.1 apache-start
# ssh -x tomcat-ssh-slave(a)127.0.0.1 top
# ssh -x tomcat-ssh-slave(a)127.0.0.1 ps
# ssh -x tomcat-ssh-slave(a)127.0.0.1 df
# ssh -x tomcat-ssh-slave(a)127.0.0.1 free
# ssh -x tomcat-ssh-slave(a)127.0.0.1 reboot
# Author: Niels P. Mayer
# Created: Monday 8/10/2009
# Modified:
# Language: Shell-script
# Package: N/A
# Status: Production
#
# (C) Copyright 2009, Niels Mayer, all rights reserved.
#
###############################################################################
# make sure nothing funny goes on
PATH="/bin:/usr/bin"
# make sure they rsh or ssh in with a single command
if [ -z "$1" ] || [ "$1" != "-c" ]
then
echo You must use ssh -c to access this account
exit 1
else
shift
SSHSLAVE_COMMAND="$@"
fi
# only let them run specific commands, eg.
# ssh -x tomcat-ssh-slave(a)127.0.0.1 cleanlog
# ssh -x tomcat-ssh-slave(a)127.0.0.1 getlog
# ssh -x tomcat-ssh-slave(a)127.0.0.1 setdbglvl 'INFO'
# ssh -x tomcat-ssh-slave(a)127.0.0.1 getdbglvl
# ssh -x tomcat-ssh-slave(a)127.0.0.1 tomcat-restart
# ssh -x tomcat-ssh-slave(a)127.0.0.1 apache-restart
# ssh -x tomcat-ssh-slave(a)127.0.0.1 tomcat-start
# ssh -x tomcat-ssh-slave(a)127.0.0.1 apache-start
# ssh -x tomcat-ssh-slave(a)127.0.0.1 top
# ssh -x tomcat-ssh-slave(a)127.0.0.1 ps
# ssh -x tomcat-ssh-slave(a)127.0.0.1 df
# ssh -x tomcat-ssh-slave(a)127.0.0.1 free
# ssh -x tomcat-ssh-slave(a)127.0.0.1 reboot
case ${SSHSLAVE_COMMAND} in
cleanlog \
getlog \
getdbglvl \
tomcat-restart \
apache-restart \
tomcat-start \
apache-start \
top \
ps \
df \
free \
reboot \
) #single argument commands -- exact match to SSHSLAVE_COMMAND
exec "/home/tomcat-ssh-slave/${SSHSLAVE_COMMAND}"
;;
setdbglvl* \ #e.g., setdbglvl 'INFO' ... multiple argument command.
Beware command injection.
)
exec `echo "/home/tomcat-ssh-slave/${SSHSLAVE_COMMAND}" | cut -f1 -d" "`
`echo "${SSHSLAVE_COMMAND}" | cut -f2- -d" "`
;;
* )
exec echo You are not authorized to do that.
;;
esac
Niels
http://nielsmayer.com
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.9.3.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This is a bug fix and enhancement release mainly around security and
the tag and mailsender applications.
Changes since XWiki Enterprise 1.9.2.
Improvements:
* XWIKI-4065 New Footnote macro
Important Bugs fixed:
* XWIKI-4109: Guest users are sometimes logged in with another user account
* XWIKI-3827: GWT wysiwyg editor has dark background with Albatross skin
* XPMAIL-17: Wrong characters in non-ascii emails
* XATAG-21: List documents with tag, rename/delete tag fails with
specific versions of MySQL5
* XATAG-22: Rename and delete actions fail with tag containing non-ascii chars
* XABLOG-27: Article date not displayed properly in IE6
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise193
Thanks,
The XWiki dev team
On Wed, Aug 12, 2009 at 09:34, Niels Mayer <nielsmayer(a)gmail.com> wrote:
> The proximity or default actions associated with the menus "edit" "show"
> "print" "action" or "watch" are often accidentally triggered by careless
> mouse-clicks intended for the "browser-tabs" or "toolbar", usually situated
> directly above the document in many browsers. I also think it is unaesthetic
> to have the current menus overlay"active space" in the LHS panels. It seems
> like the new design still has a lot of action very "close" to the
> browser-tabs and toolbar, which can lead to unintended browser accidents.
>
> I'd like to see the menu positioned away from the very top of the window,
> and instead, be placed at the bottom ofthe 220x70
> header-image /xwiki/bin/download/XWiki/DefaultSkin/*.jpg, over the
> "breadcrumbs" displaying the
> path to the document. Alternately, consider that the right-hand-side of the
> top of the document is under-used, and the left-hand-side is cluttered: you
> end up overlaying menus on the left-had-side column should that feature be
> enabled.
>
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Skin20P1/gener…
More about the skin proposal at http://markmail.org/message/nagihrc2xqpzw4dz
Hello. Please let me know if I'm using the wrong mailing list.
I am currently evaluating XWiki (along with several other wikis) for use within our small development team. We will be sharing the wiki with clients as well, so we have several criteria that MUST be met:
1. WYSIWYG editing
2. Clean interface, small learning curve
3. Fine-grained user access to pages
4. Security (the wiki will be on a server exposed to the internet, but will be private)
5. Good support base
In trying out XWiki Enterprise and looking through the documentation I think it meets these requirements (definitely 1-3).
My questions are:
1. We will want to segregate the clients from each other (ie. they won't be aware of each other), but our development team would need one-login access to all content, across clients. ie. if a developer logs in, they would have access to all content; if client A logs in, they would only see client A's content, etc. Am I understanding correctly that with User Groups and proper ACL we could achieve this?
2. I'm trying to get an idea of the support base behind XWiki: does the support and development rely on a small number of developers (or only one), or on a true community of developers? I noticed the "XWiki Project Health" page is quite out of date (only going up to Nov/07).
3. We do not currently have Java server experience; will XWiki be easy to install/run/manage securely without exposing ourselves and our clients to risks out of ignorance of the underlying technology? Is it inherently more secure than using PHP on an Apache webserver (as I have read), or does it just come down to security awareness?
Any comments or additional information would be welcome. Excuse me if I have asked questions that are readily available on the website -- I have looked through the online documentation but have also evaluated many wikis and my eyes are starting to blur.
Thanks very much,
Trevor
Hi,
We made a XWiki default installation, nothing special. We are using a
MySQL5 database which has
been configured as following:
<!-- MySQL configuration.
Uncomment if you want to use MySQL and comment out other
database configurations.
Note that the database will be created automatically if it
doesn't already exist.
We need to set the sql_mode to a less strict value, see
XWIKI-1945
-->
<property name="connection.url">jdbc:mysql://localhost:33065/xwiki?
useServerPrepStmts
=
false
&
;useUnicode
=true&characterEncoding=UTF-8&sessionVariables=sql_mode=''</
property>
<property name="connection.username">username</property>
<property name="connection.password">password</property>
<property name="connection.driver_class">com.mysql.jdbc.Driver</
property>
<property name="dialect">org.hibernate.dialect.MySQLDialect</
property>
<property
name
=
"connection
.provider_class">com.xpn.xwiki.store.DBCPConnectionProvider</property>
<property name="connection.pool_size">2</property>
<property name="statement_cache.size">2</property>
<mapping resource="xwiki.hbm.xml"/>
<mapping resource="feeds.hbm.xml"/>
XWiki is running in a Tomcat6 container with jdk1.5.0. For some reason
I do not understand, I am not able to
see the users list when logged as administrator (which all
consequences this implies...). However I see the number of
users that are registered (see attached picture)!! Does anyone
understand what the problem could be? I tried
to display this page with Firefox and Safari. Nothing, and apparently
no JS error.
Any help would be greatly appreciated. I wish you a wonderful day and
a nice week-end. Best,
christian
--
Canoo - Your Solution Provider for Rich Internet Applications
Christian Ribeaud
Canoo Engineering AG
Kirschgartenstrasse 5
CH-4051 Basel
Tel: +41 61 228 94 44
Fax: +41 61 228 94 49
christian.ribeaud(a)canoo.com
http://www.canoo.com/
> I think we should rename "Actions" back to "More Actions" since the
> second is more common (I can think of gmail for example).
>
i'm ok with that.
I would also like to have "Create" instead of the "Add" action. You can *add
* comments and tags, but I think it's more appropriate to *create* pages.
> > 1. We need to decide the way we handle the actions we are able to do
> > (depending on the rights we have): enable/disable them or hide them.
>
> Why do we keep the "view" entry ?
> I personally use "edit" to see the source of a page, may be others do the
> same.
> Anyway it's still useful to people without edit rights, in this case
> we could keep "edit" activated and display the source with a message
> saying something like "You need to login to edit this page, etc" or
> "You're not allowed to edit this page" depending on the situation.
>
I was thinking with Marta and G, would it be ok to add "History" and
"Information" to the "View" submenu? Something like
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Skin20Menu/vie…
Information in this case has been rename in "Related Pages".
> 2. You can select to have an simple or advanced menu (View and Edit
> submenus
> > affected)
>
> I wouldn't like that we use a tab layout for buttons that are actually
> not tabs, for example "view" and "edit" in simple mode.
In simple mode "view" and "edit" are not buttons, but actually tabs, you
change the view (tab) from one action to another, they aren't form buttons.
> The menu must be revamped but I'd prefer that we stick to the dropdown
> layout since it allows:
> - to mix single buttons and dropdown lists
in my opinion is the same thing, just the aligment (horizontally,
vertically) is different. The problems with dropdowns I understood that it's
not well supported if you don't have JS activated, and also dropdowns can
block some of the page content.
The advantage of the dropdown is when you have many items in the menu - but
it's not really the case and anyway menus that are very crowded are hard to
use.
Another thing is that using this kind of menu, you integrate the tabs in
Edit (Wiki, WYSYWIG, Objects ...) with the menu, instead of having the
panel. This way you give an unique access point to the editing.
- to use icons more easily
in the mockups icons are not presented, but I don't see how the dropdown
menu can have a better support for icons than then horizontal menu. it's the
same thing, we could have also icons in this kind of menu.
> - to create categories more easily (for example in "Actions")
>
you can have categories also in horizontal menus.
Thanks for all your comments,
Caty