Dear friends,
I request help on a few changes that we are making to our internal XWiki
installation.
We run XWiki 1.7 over a tomcat 6.0.18 & mysql 5 installation.
I see that the blog application has publication date feature which I believe
runs as a scheduled job. Is there a possibility to add publication date to a
page created in any other space. On the face of it, pages created in both
blog space or any other space appear to be the same. So there should be some
possibility that we can add scheduled publication dates to pages without
making major changes to the present XWiki installation.
Also, can we extend the category & sub category feature to any page outside
the Blog space.
Any help on this would be greatly appreciated.
Also, if I may suggest a name for the new skin, I would suggest 'sparrow'.
It kind of rhymes with 'arrow' & the bird is small, light & even the colors
seem to match.
Thank you all...
The XWiki development team is pleased to announce the release of XWiki
Enterprise 2.0 Milestone 3.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This is the third and last milestone for the 2.0 version.
The main goal of 2.0 is to make XWiki fully XWiki 2.0 syntax.
Main changes from 2.0 Milestone 2:
* Lots of improvements and new features in the new WYSIWYG editor
* Lots of improvements and bugfixes in the rendering engine and
the syntax converter
* Upgrade to SmartGWT 1.2
* New experimental network event distribution module
* Several blog application improvements
* Several tags application bug fixes
* Translations updated for de, fr, lv, nl, ru
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise20M3
Thanks
-The XWiki dev team
Hi Florian,
I discovered this horrible problem as well when I upgraded to "XWiki
Enterprise 1.9.21179", the page I was editing was unrecoverable and
luckily I still had my old version of the xwiki running on a different
server so I copied it back from there. I turned off the section editing
to prevent my users from losing their pages. You can do this in the
xwiki.cfg file, by setting xwiki.section.edit=0:
#-# This parameter will activate the sectional editing
xwiki.section.edit=1
Good luck,
Regan
>
> 1.) I have troubles with my wysiwyg Editor:
> I have a bigger artivle with severyl headlines. Therefor I can click
on
> the
> pen symbol tot he right of teh articel to open only a part oft he
> article.
> If I do this and store the article the parts above of the articles are
> away!
> Then I have to restore the old version than the old text is again
shown
> but
> not the new one. What can be the reason for that? If I use the editor
> without wysiwyg the same result!
Hello,
I have a few questions about how to contribute to the dutch
application_resource file.
Yesterday I have added some translations to the dutch translation of the
XE resources
at the I10n.wiki.org site. Is there any documentation about this site? I
am unsure about
what some functions do and the effects they may have on others. For
instance the link
'Import/reimport default language file', Admin actions like 'Import' and
'Prepare'. Also
I noticed that when I get the dutch translation as a application
resource file, it only has
the resources filled in if a dutch translation exists. This seems
logical, but as long as not
all strings have a dutch translation, my xwiki contains lots of empty
strings. Is there a
way to build a resource file with dutch translations where available,
and the default
english strings when not? Another thing that is not clear to me is the
functionality around
reviewing and validation. If I find a translation that is incorrect of I
thing there is a better
one, can I just change it, or should I somehow make a review request to
somebody
authorized to accept or reject the change? Is there any way to know who
is contributing
to the same translation in order to achieve some common ideas about how
to translate
xwiki terms?
Thanks,
Henk
--
==
Henk F. Schouten, ICT-architect, Dienst ICT
room: SL 2.32, phone (31) 70 4457611, email: H.F.Schouten(a)hhs.nl
De Haagse Hogeschool, Johanna Westerdijkplein 75, 2521 EN the Hague (NL)
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
... done
http://jira.xwiki.org/jira/browse/XWIKI-4161
thanks
Matthias
>Coukd you provide a sample file in a JIRA bug report so that we can
>check it out ?
>Ludovic
>
>>Matthias.Gsottberger at o2.com a écrit :
>> Hi!
>>
>> We have a problem with the new "Import Office Content" functionality in
>> XWiki Enterprise 1.9.2.22089.
>> 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
>>
>> _______________________________________________
>> users mailing list
>> users at xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/users
>>
>>
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