Hello,
The XWiki development team is pleased to announce the release of XWiki
Office 1.1.
Go grab it at:
http://www.xwiki.org/xwiki/bin/view/Main/Download#HXWiki20Office
All active XOffice 1.0& 1.1 instances will be automatically updated to the final version.
Summary of features for XOffice 1.1:
- Optional Startup
- Document refresh and View active document in browser
- Styling support for XWord 2007 and better text formatting
- Page version checking when publishing
- Document compare and conflict resolution
View detailed release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXOffice11
For more information about XOffice visit:
http://xoffice.xwiki.org
Thanks,
-The XWiki dev team
Hi devs,
I would like to release the xwiki-model-backport project at
https://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-model-backport/ .
This project is a backport of the xwiki-model module, as it was released in
version 2.2 and in addition with http://jira.xwiki.org/jira/browse/XWIKI-4775
applied, which can be deployed on a 2.1 wiki and a 2.2 wiki (with some
extra-hacks though), so that references in general and references for objects &
properties can be used on these versions. In particular, it is useful to be able
to install the annotations extension on these 2 versions.
I would like to release it now since it won't have any improvements (this is its
final version), and it should be published in the maven repo so that projects
can depend on it.
here's my +1, WDYT?
Happy coding,
Anca
Should this be a jira top level project? I don't see what existing application it
would fit in.
Some information about the code's current form:
It allows users to invite their friends to join a wiki, it has some strict measures too handle
spam situations, the email message is saved and administrators (people with edit rights on that page)
can review sent emails. The email has an ID string which is contained in a link sent to the email
address so that the invitee can report the email as spam (this is a function of the template.)
falsely reporting messages as spam is protected because the ID string is a large random number.
Users can send to one address and admins can send to as many addresses as they like.
Email addresses are checked against a regular expression before sending and invalid addresses
will not be sent to.
If the sender is a user and can only send to one address then the address is checked against
LiveValidation as well.
If a message is reported as spam, then it is flagged on the list and when an admin views the list
they can inspect the message and select a button to indicate that the situation has been
investigated.
Caleb
Hi,
Since today is the day we're supposed to release XE 2.3M2 and since we've released 3.2M1 quite late compared to the original date we need to decide what we do from now on.
Original dates:
* XE 2.3M1: 8 March 2010 (1 month after XE 2.2 final)
* XE 2.3M2: 29 March 2010
* XE 2.3RC1: 12 April 2010
* XE 2.3 RC2/Final: 26 April 2010
Here's my proposal:
* We have enough new features already (captcha in comments, new theme editor, annotation features, any char supported un doc names, lots of rendering fixes, etc) to justify a final XE 2.3 release
* I suggest Thomas finishes putting our Lucene search as the default search since it's now working well enough. AFAIK Thomas is only missing an admin screen to finish it.
* I suggest we don't have more new features (unless someone has something that can be committed this week - Caleb: what about the invitation feature?)
* I suggest we release:
** XE 2.3M2 on the 5th of April
** XE 2.3RC1 on the 12th of April (one week after)
** XE 2.3RC2/final on the 19th of April (and in case we have problems we can delay by one week till the 26th of April)
WDYT?
Thanks
-Vincent
Hi all,
I've come across this issue today while using the code 20 macro. It seems
that there's an issue with the class loader that is unable to locate one of
the packaged python modules (os). It might explain the cause given the fact
that with Tomcat I've no issues (now using Weblogic as company wide app
server). Have you ever experienced something line this:
Caused by: Traceback (most recent call last):
File "<string>", line 1, in <module>
File "__pyclasspath__/pygments/__init__.py", line 36, in <module>
ImportError: No module named os
at org.python.core.PyException.fillInStackTrace(PyException.java:70)
at java.lang.Throwable.<init>(Throwable.java:181)
at java.lang.Exception.<init>(Exception.java:29)
at java.lang.RuntimeException.<init>(RuntimeException.java:32)
at org.python.core.PyException.<init>(PyException.java:46)
at org.python.core.PyException.<init>(PyException.java:43)
at org.python.core.PyException.<init>(PyException.java:61)
at org.python.core.Py.ImportError(Py.java:264)
at org.python.core.imp.import_first(imp.java:672)
at org.python.core.imp.import_name(imp.java:756)
at org.python.core.imp.importName(imp.java:806)
at org.python.core.ImportFunction.__call__(__builtin__.java:1232)
at org.python.core.PyObject.__call__(PyObject.java:367)
at org.python.core.__builtin__.__import__(__builtin__.java:1202)
--
View this message in context: http://n2.nabble.com/Issue-with-Pygments-Python-tp4816815p4816815.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Dear XWiki Developers,
When I execute start_xwiki_debug.sh, it gives me this:
Starting Jetty on port 8080 ...
Logs are in the ./xwiki.log file
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
[../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Aborted
However when I executed "start_xwiki.sh", it works. What should I do? Can
you give me some suggestions? Also could you please tell me more about debug
the XWiki wysiwyg editor?
When I try ./start_wysiwyg_noserver.sh, the gwt hosted mode edit gives me
"[ERROR] Unable to find 'com/xpn/xwiki/wysiwyg/Wysiwyg.gwt.xml' on your
classpath; could be a typo, or maybe you forgot to include a classpath entry
for source?".
I tried "start_wysiwyg_noserver_debug.sh". It gives me:
freeleons@EAS-BEN200-002:~/XWiki_Enterprise_2.1.1$
./start_wysiwyg_noserver_debug.sh
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
[../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
./start_wysiwyg_noserver_debug.sh: line 33: 16915 Aborted
$JAVA32_HOME/java -Xmx1024m -Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,address=5006,suspend=y -cp
$APP_DIR/WEB-INF/lib/xwiki-web-wysiwyg-$XE_VERSION.jar:$M2_REPO/com/xpn/xwiki/platform/xwiki-web-wysiwyg/$XE_VERSION/xwiki-web-wysiwyg-$XE_VERSION-sources.jar:$M2_REPO/org/xwiki/platform/xwiki-web-gwt-dom/$XE_VERSION/xwiki-web-gwt-dom-$XE_VERSION.jar:$M2_REPO/org/xwiki/platform/xwiki-web-gwt-user/$XE_VERSION/xwiki-web-gwt-user-$XE_VERSION.jar:$M2_REPO/org/xwiki/platform/xwiki-core-component-api/$XE_VERSION/xwiki-core-component-api-$XE_VERSION.jar:$M2_REPO/com/google/gwt/gwt-incubator/july-14-2009/gwt-incubator-july-14-2009.jar:$M2_REPO/com/smartgwt/smartgwt/1.2/smartgwt-1.2.jar:$M2_REPO/com/google/gwt/gwt-dev/$GWT_VERSION/gwt-dev-$GWT_VERSION-linux.jar:$M2_REPO/com/google/gwt/gwt-user/$GWT_VERSION/gwt-user-$GWT_VERSION.jar
com.google.gwt.dev.HostedMode -logLevel WARN -style DETAILED -noserver -port
8080 -startupUrl xwiki/$WYSIWYG_PATH/Wysiwyg.html
com.xpn.xwiki.wysiwyg.Wysiwyg
freeleons@EAS-BEN200-002:~/XWiki_Enterprise_2.1.1$
Thank you guys in advance!
The start_xwiki_debug.sh script is attached for your reference:
--------------------------------------------------------------------------------
#!/bin/sh
# Ensure that the commands below are always started in the directory where
this script is
# located. To do this we compute the location of the current script.
PRG="$0"
while [ -h "$PRG" ]; do
ls=`ls -ld "$PRG"`
link=`expr "$ls" : '.*-> \(.*\)$'`
if expr "$link" : '/.*' > /dev/null; then
PRG="$link"
else
PRG=`dirname "$PRG"`/"$link"
fi
done
PRGDIR=`dirname "$PRG"`
cd "$PRGDIR"
JETTY_HOME=jetty
JAVA_OPTS=-Xmx300m
JAVA_OPTS="$JAVA_OPTS -Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"
# The port on which to start Jetty can be passed to this script as the first
argument
if [ -n "$1" ]; then
JETTY_PORT=$1
else
JETTY_PORT=8080
fi
# For enabling YourKit Profiling.
# $3 must the path where Yourkit can find the agent.
# For example: "/Applications/YourKit Java Profiler 7.0.11.app/bin/mac"
# Note: you must also pass the port as $1 for now till we use getopts.
if [ "$2" = "profiler" ]; then
JAVA_OPTS="$JAVA_OPTS -agentlib:yjpagent"
export DYLD_LIBRARY_PATH="$3"
fi
echo Starting Jetty on port $JETTY_PORT ...
echo Logs are in the $PRGDIR/xwiki.log file
# Ensure the logs directory exists as otherwise Jetty reports an error
mkdir -p $JETTY_HOME/logs 2>/dev/null
# Specify port and key to stop a running Jetty instance
JAVA_OPTS="$JAVA_OPTS -DSTOP.KEY=xwiki -DSTOP.PORT=8079"
java $JAVA_OPTS -Dfile.encoding=UTF8 -Djetty.port=$JETTY_PORT
-Djetty.home=$JETTY_HOME -jar $JETTY_HOME/start.jar
--------------------------------------------------------------------------------
Jue Wang
Hi committers,
I would like to propose Denis as a XWiki core committer.
Denis is an experimented developer (20 years) and has started developing and
selling application (through his companies Softec and eGuilde) using XWiki
since version 0.9. He had used fully the XWiki model, in the context of
multilingual wikis and farms, and he have therefore a very good knowledge of
the oddities of the core in many aspects.
Denis is one of the few that knows very well deepest parts of XWiki (even
some of the new components).
Since he have build large applications over XWiki and works for customers,
he also provide good feedback and have strong ideas and proposals to improve
our current implementation. However he has been very busy these years and he
had initially postpone my wishes to vote him as a commiter in September last
year. Now he is more available and we decide to go on.
Bugs reports by Denis are verified and usually well documented, often with
patches when possible or at least some analysis of the issue. The largest
one that I have just applied is XWIKI-4627 "Reduce heap exhaustion during
export (and partly import)" (see
http://jira.xwiki.org/jira/browse/XWIKI-4627).
Some stats:
- Issues reported by Denis(62):
http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&reporterSe…
- JIRA comments by Denis (174) and Mails sent by Denis (43):
http://xwiki.markmail.org/search/?q=from%3ADenis+Gervalle
- Total patches from Denis (19), 10 have been applied:
http://xwiki.markmail.org/search/?q=Denis+Gervalle+keywords+patch
- Mails mentioning Denis on devs and users mailing lists (192):
http://xwiki.markmail.org/search/?q=Denis
So, I propose Denis to applies his own patches from now on.
Here is my +1.
Thanks
--
Thomas Mortagne
Hi Dear XWiki developers, Hi Marius,
I follow the instruction about how to debug Wysiwyg, " To debug using XWiki
in the backend you have to first start the server (normal or debug,
depending if you wish to debug server side code also) and then run the
start_wysiwyg_noserver_debug.sh script from the same directory as
start_xwiki.sh (copy it there first)."
I used the start_xwiki.sh script to start the server. Then I used
start_wysiwyg_noserver_debug.sh
script try to debug it. However, after execute the script and it says
"Listening for transport dt_socket at address: 5006". I use Eclipse Remote
Debug connect to the port 5006. Then the Google Web Toolkt Hosted Mode
windows will prompt up and it says "Unable to find
'com/xpn/xwiki/wysiwyg/Wysiwyg.gwt.xml' on your classpath; could be a typo,
or maybe you forgot to include a classpath entry for source?' I have copied
the Wysiwyg folder, which is /com/xpn/xwiki.wysiwyg and Wysiwyg.gwt.xml, to
the same folder of the start_wysiwyg_noserver_debug.sh.
Is it because Maven gwt project layout and the gwt project layout are
different? What should I do?
Thank you!
Jue Wang
Hi xwikiers,
We just found an important regression in 2.2.3 in the rights
management user interface.
This bug prevents rights to be correctly saved unless you manually
select either groups or users radio button first. See
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise223.
Work is in progress to fix it, a 2.2.4 will be released ASAP.
Really sorry about that :(
Thanks
--
Thomas Mortagne