Hi
I'd like to propose a patch for com.xpn.xwiki.doc.XWikiDocument in order to
add a function that can allow user to create attachments.
Regards
--
Xavier MOGHRABI - Consortium ObjectWeb
Email: xavier.moghrabi at objectweb.org
Phone: +33 4 76 61 52 35
I've noticed that the version number (correctly) gets bumped for
every new comment or image upload. However, I would like a means to
show a list of revisions for _just_ content changes, i.e. exlude the
revisions which were created for new comments and attachments. How
would I do this in some velocity code?
Thanks,
Matt
Greetings,
I am new to xwiki and was wondering how some of the multi-company features of xwiki work. From my readings it sounds like one must create a separate mysql db for each new company/tenant. If this is true would this not require a seperate database connection pools for each company?
Are Oracle or Postgresql supported? I know with these two databases one can create database namespaces (something mysql does not have). This would allow the same jdbc driver to reference mulitple namespaced schemes and thus use the same pool.
Anyway, any thoughts would be apprciated. I am looking to setup xwiki in a multi company setup and was looking for some insight.
Thanks,
Sam
---------------------------------
Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
Here's an issue I feel should be addressed before the 1.0 release:
Create a wiki page with links like the following:
[Images: Good or Bad?]
[C++ Examples]
XWiki renders the first link like this:
<a class="wikicreatelink" href=""><span class="wikicreatelinktext">Images:
Good or Bad?</span><span class="wikicreatelinkqm">?</span></a>
It's completely broken. The second link is rendered like this:
<span class="wikilink"><a href="/xwiki/bin/view/Sandbox/C+++Examples">C++
Examples</a></span>
XWiki should be able to gracefully handle Wiki links with non alpha-numeric
characters.
Here are my thoughts on a solution to the problem:
1. When rendering a Wiki link, XWiki could strip out all non-alphanumeric
characters. Thus, a link like [Images: Good or Bad?] would render as <a
href="/.../ImagesGoodorBad">Images: Good or Bad?</a>. Benefits:
Straightforward to implement. Yields nice clean document names. Drawbacks:
Presents backwards compatibility problems; several different Wiki links
could map to the same document name.
2. XWiki could perform URL encoding on the Wiki links. Benefits: Better
backwards compatibility (I think). Drawbacks: Yucky document names.
Perhaps there are other solutions somewhere in between. My personal
preference is #1. Backwards compatibility could perhaps be addressed with a
configuration option switch.
I created a Jira issue for this: http://jira.xwiki.org/jira/browse/XWIKI-188
Thoughts?
Stephen
Here is a status on the development towards the next release, which
should be the one of the very last release before 1.0.
The following major feature have been added to the current SVN version
Thanks to the Summer of Code we have now
- a WYSIWYG Editor
- a Chart Wizard
- a new Query Language
Additionnally we have:
- a new title field and different rendering of document names in links
and in the header
- a backlinks feature (activated using xwiki.backlinks=1 in xwiki.cfg)
- a custom mapping feature allowing to store XWiki Objects in flat
tables for advanced developments
- new storage of XWiki classes definition in the xwikidoc table instead
of multiple tables
- the XWiki Preferences now use a custom mapping for better performance
- lot's of bug fixes, incl. access through proxies, issues with the
multilingual feature
- an import/export API (for backups and for XWiki applications) which is
needed for the Import/Export XWiki page
- improvements to the URL scheme which will allow to reduce the number
of elements in the xwiki URLs (currently some XWiki features still need
xwiki to run on the /xwiki/ path)
These are a lot of new features which needs to be well tested before
become fully usable. Most of the features can be deactivated or are
backwards compatible.
We would need some help from the XWiki community to test this new
version and report any issues in JIRA ( http://jira.xwiki.org ).
Except for the preferences storage and the xwiki classes definition
storage, it is possible to revert to an older version even if running
the new version. Now it is highly recommended to backup your database
and test with care on production data.
I'm planning to provide a test build for developers, but if you want to
test right away, you will need to build XWiki from the SVN code.
The plan for getting XWiki to 1.0 is:
- bug fixing
- bug fixing
- documentation
- very small missing features
- bug fixing
- documentation
- revamp of the XWiki interface according to the Usability report done
during the summer
- bug fixing
- documentation
Any help or comments is welcome.
For now it would be usefull to identify bugs that would absolutely need
to be fixed before releasing this version to replace 0.9.840. The
objective is to provide an improvement versus 0.9.840 and allow working
with the new features, not necessarily to provide a perfect version.
Thanks and happy testing
Ludovic
--
Ludovic Dubost
XPertNet: http://www.xpertnet.fr/
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost AIM: nvludo Yahoo: ludovic
What about adding a permanent XWiki bounties section, to somehow
perpetuate the idea of the Google Summer of Code in the fall?
This page pointed out by Marc gives a structured bounty process:
http://www.ubuntulinux.org/community/bounties/document_view
I'd be happy to sponsor a few ones if this makes sense to you too.
By the way, since the move from SourceForge to ObjectWeb, is there still
a way to make donations to the project?
Stéphane
build.xml builds the exo fileset with the xwiki-normal.cfg into the
xwiki-N.N.N.war and xwiki.war targets and vice versa into
xwiki-exo-N.N.N.war.
Jim
--
Jim Stuttard
Hi,
I'm just trying to check out the actual xwiki source with IntelliJ
5.0.1. I can browse the repository but when I want to checkout
IntelliJ says: Cannot checkout from svn: Unknown command 'get-
locations'.
Is this an IntelliJ or svn repository problem?
Thanks
Yves
I defined a class with several properties and I created some
documents based on this class. Now I added some new properties to
this class but I'm not able to supplement the new properties in the
existing objects (field is read-only, no input field). When I create
a new one the property can be set.
Is this a normal behaviour?
Yves
XTeam:
I hope you don't mind me giving you a name. :-) Sort of like the "A-Team".
I hope it gives you a sense of pride. You are working on one very
important software system. Why? Because Xwiki answers certain to needs
that no other wiki does. In this respect, it is trully a unique system
that has both great capability now and extraordinary promise for the
future.
A few noteworthy facts:
Siebel Systems is using XWiki. Siebel is a worldwide leader in customer
relationship management systems.
More than one team at IBM leverages XWiki. IBM is a world leader in
software, hardware, and business consulting services.
XWiki has even taken life inside of the corporate offices of UPS, the
worlds largest package delivery company.
Give yourselves a big pat on the back! But not too big; I need your help.
I have only recently joined the "XTeam" and my first goal is to fill a
task that many do not often enjoy - creating and editing documentation. I
do not necessarily enjoy writing documents, but I know that the importance
of good documentation is too often overlooked. I believe that good
documentation will help the evolution of XWiki more potently than most
realize.
I believe that...
People judge XWiki before even trying it based soley on the quality of the
documentation.
First impressions are critical. If administrators have a poor installation
experience (due to poor docs, for example), they will be disenchanted
immediately.
Innovative developers who can bring powerful enhancements to XWiki can
bring those improvements faster if we decrease the initial learning curve
through solid documentation.
Open source projects are typically poor in documentation. Thus, we can
look at this as a lesson and strive to use this as a point of great
differentiation.
My goal over the coming month is to play a strong role in transforming the
User Guide and Administrator Guide. To achieve this goal, I pledge to work
on documentation a little bit each day. Afterwards, I will probably roll
into the usability and user interface focus. Until then, i hope you will
accept me as a workhorse for you. Here's how you can help me (and the
XWiki evolution):
1. Take a little time out to reflect on some things you have learned about
XWiki and document them in the new guide areas.
DEV GUIDE: http://www.xwiki.org/xwiki/bin/view/DevGuide/WebHome
ADMIN GUIDE: http://www.xwiki.org/xwiki/bin/view/AdminGuide/WebHome
2. Feel free to send rough notes, comments, or thoughts to me and I will
do the dirty work of cleaning them up and finding an adequate home for
them in the guides,
3. Explore the organization of the new guides. Look for empty holes. Ask
yourself what you might be able to contribute there and contribute
something if you can.
I am sure that before the month is over, we may reorganize the guides more
than once just to get them "just right", so expect to see some changes and
some movement of documents. Ludovic has already gotten a reorg started; it
isn't perfect, but it is better. Progress must be iterative. Expect
frequent questions from me here as I struggle to learn and ensure accuracy
of the documentation. At a minimum, please remember that source code
documentation can be extremely valuable for other XTeam members.
Otherwise, just keep up the great work on the software and do what you can
to review and improve the accuracy of the new docs that will be going up
over the month (as time permits).
==================================
Cody Burleson
cburleso(a)us.ibm.com
I'm forwarding to the list part of a discussion currently starting in
the Eclipse-Phoenix project mailing-list.
The Phoenix project consists in providing a new infrastructure for
Eclipse online infospace: http://eclipse.org/phoenix/
Most requirements of the project are listed there:
http://dev.eclipse.org/mhonarc/lists/phoenix-dev/msg00053.html
Any support is welcome for comparing XWiki with other wiki engines and
for discussing further with Phoenix team! Teaming up with them would be
great for the future of both projects!
Stéphane
--
Stéphane Laurière
slauriere(a)mandriva.com
Unbelievable what I had to go through to get some of the backup system to
work on Windows!
The classpath in the env.sh file is so long that when you convert it to a
Windows .bat file, Windows doesn't even accept it! I had to copy all my
libraries into C:\lib just to get the classpath line short enough.
I executed the export script (groovy export).
The utility created a db folder with files in it, so it seems to work (I
guess).
Except for the following error in my xwiki.log file:
17:26:53,428 WARN main Configurator:configure:126 - No configuration
found. Configuring ehcache from ehcache-failsafe.xml found in the
classpath: jar:file:/C:/lib/ehcache-1.1.jar!/ehcache-failsafe.xml
A few questions now:
1. Does anyone know why I am getting this ehcache-failsafe warning?
2. Does backup's export/import handle the binary attachments?
3. If I backup from one wiki and import in another, am I overwriting the
wiki or appending to it?
4. Is there a plan to incorporate the backup feature into the XWiki user
interface (because all of this special configuration on Windows is quite
troublesome)?
==================================
Cody Burleson
So, I am having trouble figuring out how to use the new backup feature.
Can someone throw me a bone?
Here is what I have done:
1. Upack the latest Groovy binaries to C:\groovy-1.0-jsr-03 (download from
Groovy site)
2. Set GROOVY_HOME env variable to GROOVY_HOME that directory
(C:\groovy-1.0-jsr-03)
3. add C:\groovy-1.0-jsr-03\bin to your PATH environment variable.
4. Put C:\Tomcat 5.5\webapps\xwiki\WEB-INF\lib\xwiki.jar; on CLASSPATH
5. Test on cmd: Type groovyConsole to make sure groovy works
5. Copy libs from xwiki "backup" into lib folder of xwiki/web-inf
6. copy "hibernate.cfg.xml" from backup to xwiki/web-inf/classes
7. copy import.groovy and export.groovy to webapps/xwiki/
Then, when I type the following on the CMD line, I get an error (see
below)
C:\Documents and Settings\Administrator>cd C:\Tomcat 5.5\webapps\xwiki
C:\Tomcat 5.5\webapps\xwiki>groovy export.groovy
General error during class generation: No such class: XWikiContext in
constructor call for class: xwiki.export.export. At [7:11] export.groovy
1 Error
The XWiki war I am using is from a build I did last night off of all the
latest code from the Trunk branch. But why is my XWikiContext not
recognized? I have even put xwiki.jar on the classpath.
??????
==================================
Cody Burleson
Hi
I'm looking for a way to define some kind of associations between
classes. Let me explain by an example what I mean exactly:
I want to collect structured data for countries and its regions. To
achieve this I define to classes, CountryClass and a RegionClass (incl.
the sheets and templates). Now the user should be able to create new
country objects _and_ he should have the possibility (in the form
itself) to define which regions belong to a country.
I tried to achieve this by adding a database list property to the
country class with an appropriate hibernate query which selects all
region documents. This let the user select one or more regions for a
country. This is fine so far but
- Is there any more general or a better way to achieve this associations
(e.g. without hibernate queries)?
- How can I adapt my ClassSheet so that the selected region associations
are hyperlinked to the appropriate region objects?
Thanks
Yves
All,
I have a project to add new Knowledge Management functionalities in xwiki, the first one I have selected is the collaborative categorization also known as folksonomy.
The point is to allow the wiki users to categorize the wiki topic with keywords as what you can do in http://del.icio.us/ .
Does anybody have ideas on this subject?
Thierry Magnard
Hi
I'm new to XWiki and would like to know,
how can I integrate another rendering engine into XWiki (especially
Wikipedia rendering based on Radeox)?
Is there an online guide available?
Can someone point me to the main interesting classes?
Is there a "synchronizing API" with another XWiki instance available?
Does someone has experience in integrating XWiki into a roller blog system?
--
Axel Kramer
http://www.plog4u.org - Wikipedia Eclipse Plugin
http://www.bliki.info
I am happy to announce the release of the project P2PXWiki developed as
part of Google SoC. P2PXWiki contains a central registry (for
registering a new XWiki) which can be updated by peers using JXTA
network. It also includes support for replication, allowing a wiki to be
replicated among peers.
Please checkout the project page
http://www.xwiki.org/xwiki/bin/view/Dev/P2PXWiki . Comments are welcome.
-Bikash