If the answer is yes, then I propose that we modify the
XWiki.getUserClass() method to create a XWiki.XWikiUsers class that
has the "usertype" property by default.
I think the notion of simple/advanced user could be one that is
generic enough to be a core feature.
I'm curious to know what you think.
Thanks
-Vincent
Dear XWikiers,
I'd like to propose voting Anca Luca as a XWatch committer.
Anca has submitted several good patches for XWiki Watch. (see
http://tinyurl.com/2x3psb) She writes clean code and shows a strong focus
on design and separation of concerns. I propose she now commit her own
patches on XWatch!
Here's my +1 for Anca.
Note: For full disclosure, Anca is working for XPertNet, the company
behind the creation of XWiki. FWIW, out of the 26 committers
(http://www.xwiki.org/xwiki/bin/view/Community/HallOfFame), 9 are working
for XPertNet. Note that the XWiki project is driven as a meritocratic
project (trying to follow the Apache rules as much as possible) and thus
anyone can become a committer (see
http://www.xwiki.org/xwiki/bin/view/Community/Committership). The more the
merrier!
Regards,
Jérôme.
Hi all,
Having xwiki document with no extension in the files names is a real
mess for subversion and IDEs like Eclipse and IntelliJ IDEA and it
will also be very useful in any editor that takes extension to
determine the content or simply for most OS Explorers/Finders.
As the XWiki maven xar plugin now support files with any name when
creating the xar package (see
http://jira.xwiki.org/jira/browse/XTOOLS-19) I propose to add .xml
extension to exported document files names.
Import document with any names is already supported by xwiki core
importer plugin since at least svn1387 (October 2006) and I think
since it's creation so it seems it will not break older version
import.
--
Thomas Mortagne
Hi,
Here's my list of what remains to be done to release XE 1.2RC1:
* fix the MINOR EDIT exception that happens from time to time on
xwiki.org: http://jira.xwiki.org/jira/browse/XWIKI-1879
* continue looking at xwiki.org logs and fix exceptions that appear
* commit the stats patch submitted by Marius http://jira.xwiki.org/jira/browse/XWIKI-1845
* fix the XHTML validation issues discovered by the build
* test the stats feature on xwiki.org (enable stats with Raffaello and
monitor xwiki.org's performances)
* test the watchlist feature on xwiki.org (configure the smtp server
with Raffaello and try the feature)
If you know of other important issues for XE 1.2RC1 that cannot wait
for later please let us know.
Thanks
-Vincent
Hi Sergiu,
We need to discuss this since this is starting something new that
we've never discussed.
How do you plan to distribute the s5 application? I don't see how to
do that with a web module or do you mean that this web module will
generate a zip that the user will manually unzip in his xwiki webapp?
Should we distribute 2 files (XAR+ZIP) or one file (a single zip
containing both)?
Also this raises the question of plugins which I've started to discuss
some time ago: should they go in applications or stay in plugins/?
Thanks
-Vincent
On Nov 26, 2007, at 6:59 PM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2007-11-26 18:59:12 +0100 (Mon, 26 Nov 2007)
> New Revision: 6086
>
> Added:
> xwiki-platform/xwiki-applications/trunk/s5/wiki/
> xwiki-platform/xwiki-applications/trunk/s5/wiki/pom.xml
> xwiki-platform/xwiki-applications/trunk/s5/wiki/src/
> xwiki-platform/xwiki-applications/trunk/s5/wiki/src/main/
> Removed:
> xwiki-platform/xwiki-applications/trunk/s5/src/
> xwiki-platform/xwiki-applications/trunk/s5/wiki/src/main/
> Modified:
> xwiki-platform/xwiki-applications/trunk/s5/pom.xml
> Log:
> Create a submodule for the wiki pages, as this application should
> also contain velocity templates and skin files that will go in a web
> module.
>
[snip]
Hello,
I was wondering about the code that is by default in a class sheet - when
you create a class with the class wizard.
The class sheet has code to display all properties of one object of the
concerned class. To display each property, you use the display() method
which accesses a property through its name. Now imagine you have a page with
objects of different classes, and some of the classes have same-named
attributes. The respective class sheets are all included in the page. Then
the display() method, when used, will be confused.
How about replacing the Velocity call
$doc.display($prop.getName())
by this one :
$doc.getObject("YourClassSpace.YourClass").get($prop.getName())
? What do you think ?
--
Jean-Vivien MAURICE
Elève Ingénieur Informatique et Gestion, Polytech'Montpellier (ISIM)
E-mail : jean.vivien.maurice(a)gmail.com
Tél. : 0046 7 62 33 20 46
Skype : jean.vivien
Hi,
Since we're nearing the final XE 1.2 release I'd like that we vote on
each of the following:
1) Once Panels app 1.2 is released, separate the versioning of the
Panels app from the versioning of XE/Platform, i.e. next version will
be 1.3 without milestones. Same as for the other apps/plugins.
2) Create a branch now for XE/Platform/Panels 1.2RC1 so that work can
start on trunk for Platform 1.3M1 and XE 1.3M1.
3) Don't do a XE/PF/Panels 1.1.3 release and instead move XEM and
other products to XE/PF/Panels 1.2 final (since it's going to be
released in less than a month). This will also allow to have only 2
branches to manage: the trunk and the branch from 2). This also means
that we should probably release a XEM 1.0 quickly (that'll use PF
1.1.2) and start working on XEM 1.1 on trunk which will use PF 1.2.
Here's my +1 to all 3 items above.
Thanks
-Vincent
Hi,
Several users are saying that 10MB is too low a default value. I think
I agree with them. Now I can't think of a downside for increasing it
to a higher value. Is there any potential issue increasing it by
default to a higher value?
What could be the a better value? That's a hard question but I'd say
30MB should be fine.
WDYT?
Thanks
-Vincent
Hi,
I have the following problem with WebSearch: for some reason users without
admin rights (guest , AllWiki Group) cannot see the results of WebSearch.
The error message appears on the search page:
Topic XWiki.WebSearchCode does not exist Topic XWiki.Results does not exist.
If I’m being logged as admin, the WebSearch works fine. (it’s enough if I
login as admin after I sent the search request – the error messages
disappear and I get a table with the search results)
I tried to import XWiki.WebSearchCode and XWiki.Results once more from the
.xar archive. The import was successful, but it didn’t help.
I couldn’t find any conditions in the xwiki-code of
wiki/bin/view/Main/WebSearch, that would allow only admin-users to see the
search results
I'm running XWIKI (xwiki-web-standard-1.1.1) under OC4J on Linux server.
Thanks for any help.
adoro
--
View this message in context: http://www.nabble.com/WebSearch-works-only-for-admins-tf4862014.html#a13913…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi all,
I made all the set up xwiki on my server, and for same ip it worked fine.
But when i change and make my server ip address static it does not start and gives connection pool error.Can you tell me is this the problem of server or the database?
Also please tell me how can i solve it.
ANUJ SHARMA.
---------------------------------
Why delete messages? Unlimited storage is just a click away.
Hi,
due to the translation bug (XWIKI-1841) I spent some time looking for
inconsistent rows in our database (Postgres 8.1) and I found several
documents inserted twice into the database, which lead to problems when
editing and viewing the documents. For luck our coporate wiki has just 23
pages with problems caused by this bug (the same xwd_fullname with different
xwd_id fields / the select statement can be found at the end of this mail,
perhaps anyone is intrested in).
The thing I'm quite confused about is that there are no unique constraints set
on the the columns which could have prevented these problems. The DBMS would
have forced the XWiki core to generate an error instead of inserting
inconsistent data sets into the database.
I neither know much about Hibernate, nor I have tested whether XWiki would use
constraints with other DBMS, but would it be possible to set those
constraints in future versions?
At the moment I'm quite scared about reactivating I18N for our corporate wiki,
because an similar programming might occour again, but with a clean
constraint setup, those errors would not happend silently in the background,
but instead appear as they occur transparent to everyone.
From my point of view it should be possible to set an unique constraint on
xwd_fullname and xwd_language. Up to now I did't understand why there is a
need for the fields xwd_default_language and xwd_translation, but on the
other I didn't investigate any time in this. Wouldn't it be enough to have
the fields xwd_fullname and xwd_language? (The next thing is: Why is there a
need for xwd_web, xwd_name and xwd_fullname? - Just because I'm curious.)
Are there any similar thoughs? What do you think? For a modern DBMS (not MySQL
3.23 ;)) shoud be able to "support" XWiki and to prevent inconsistencies and
corruption of data.
But nevertheless I love XWiki 1.1! The renaming feature and the panel support
are great. Just these two new features made any problems during the migration
from 0.9.840 forgotten. :)
The mentioned query from above for searching inconsistent rows in the database
(working for Postgres 8.1):
select xwd_fullname, xwd_version
from xwikidoc
where xwd_fullname in
(select xwd_fullname
from xwikidoc
group by xwd_fullname
having count(*) > 1)
order by xwd_fullname;
--
Best regards,
Fabian.
Hi all,
I'm reverting http://jira.xwiki.org/jira/browse/XWIKI-1802 as it break
some (rare but existing) use cases.
I spoked with Vincent about some solutions to be able to export
documents without version related informations and I will look about
it a bit more. How we see that actually is to add a new parameter like
"resetVersionInfos" (or "resetTechInfos" or anything else I'm not sure
yet) which handle "author", "creationDate" etc. and force
"withVersions" to false.
See also http://tinyurl.com/2sx7s4 for initial thread on this subject.
Thanks,
--
Thomas Mortagne
Hi fellow XWikiers,
a quick e-mail to tell you that 3 XWiki team members will be at Javapolis (
http://www.javapolis.com/ ) in Antwerp, Belgium, from the 12/12 to the 14/12
2007. Javapolis is the biggest yearly Java event in Europe.
Vincent Massol, Jean-Vincent Drean and me will be there to answer every
question you may have about XWiki. You'll have the opportunity to meet
people from other OW2 projects such as eXo too.
Please let us know whether you'd be interested to attend the conference on
the dedicated XWiki Facebook Event page at
http://www.facebook.com/event.php?eid=14478490493
.
You can check out XWiki's booth location on the floor plan (available on
XWiki.org at http://www.xwiki.org/xwiki/bin/view/Blog/XWikiAtJavapolis2007
)
Looking forward to seeing you there,
The XWiki team
Hi,
Marius has just submitted a patch for the Statistics feature.
See:
- http://jira.xwiki.org/jira/browse/XE-37 (UI)
- http://jira.xwiki.org/jira/browse/XWIKI-1845 (API)
I'd like to vote for including this in 1.2RC1. Even though RC is about
improving the stability and fixing bugs I think we should include it
for the following reasons:
* It's a nice new feature, much needed
* It's independent from the rest and won't impact the stability
If we're not comfortable with having it in RC1 then we should create a
1.2M3 release and release it once the patch has been applied. However
an extra release is quite some work (a full day of work + the
associated stresss ;)) so I'd rather have it as part of 1.2RC1.
So here's my +1
Thanks
-Vincent
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.2 Milestone 2.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This is the last milestone release for the 1.2 version. It's packed
with new features and improvements. The next version will be 1.2 RC 1
and will focus on improving the stability. The roadmap is to release
1.2 final for beginning of December 2007.
Main changes from 1.2M1:
* Completely redesigned the UI for managing permissions and groups/
users. It's now a nice Ajax interface which scales to any number of
users.
* A new Mail Sender plugin has been added. It's a generic plugin that
you can use from Velocity/Groovy pages and that is also used by the
Watchlist feature below to send notification emails.
* New Watchlist feature which allows watching pages and spaces and
receive email notifications when they are modified.
* The Scheduler Plugin and the Scheduler Application have been
released in version 1.1 and are bundled with XWiki Enterprise 1.2
milestone 2. They allow you to create jobs (Groovy scripts) to be
executed in the future. They are used for example in the Watchlist
plugin to send email notifications for pages or spaces you are
monitoring.
* New displayPanelLayout Macro to display Panels in page.
* New JODA Time plugin to allow using JODA time from Velocity/Groovy
pages.
* The top level edit menu has been reorganized. Separators have been
added, the Rename and Delete actions have been moved in an Action menu
and a new Watch menu has been added.
* Entering URLs such as http://myserver/xwiki goes to the Main.WebHome
page by default (it used to display some installation instruction page).
* Panels from other virtual wikis can be used now.
* Lucene Search UI and stability has been improved.
* Removed the Presentation application from the default wiki (since it
was not maintained and was buggy).
+ bug fixes and other improvements
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise12M2
Thanks
-The XWiki dev team
Hi,
I'm building a customized version of the xwiki enterprise.
So far i've created a new skin and a new plugin.
I want to:
- define the new skin as default. I mean, instead of changing the
xwiki.cfg or the skin class i would like to make it default at
compile level. Everytime i do mvn install i should be selected as
default.
- include my new plugin in WEB-INF/lib automatically everytime i
compile (just like the other plugins - jodatime etc)
thank you very much for you attention.
regards,
Luis Ferreira
Hi all,
I'm fairly new to this list. Please forgive me for any inconvenience.
With the new XWiki version on the road I just resume my migration
assignment from v0.9 t v1.2. Let us make a little review: when trying to
import the xar file to v1.2 (take a look at
http://www.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HUpgradinganXWi…)
it fails with a java.lang.NullPointerException
As I can see it brokes at
com.xpn.xwiki.web.ImportAction.render(ImportAction.java:42), but
couldn't see why (yet?)
I plan to fill a bug report and try to fix it (humbly I'm not sure of a
success history here, but I'll try ...), so my questions are :
* I need to add a new bug report or just add more info to the one
already opened (http://jira.xwiki.org/jira/browse/XWIKI-1809). In
my case is a null pointer exception when tries to open the file,
but in the reported one its caused when tries to parse the xmlfile
* Anyone is having the same problem and have fixed it or created a
workaround ??
TIA
--
Víctor A. Rodríguez (http://www.bit-man.com.ar)
El bit Fantasma (Bit-Man) - Algorithm junkie
Perl Mongers Capital Federal (http://cafe.pm.org/)
GNU/Linux User Group - FCEyN - UBA (http://glugcen.dc.uba.ar/
Hi all,
I would like to change the feed plugin so that the content of the fetched
documents can be easily changed.
Currently, the content of the document containing a fetched article is
hardcoded to "#includeSheet('XWiki.FeedEntryClassSheet')".
I think that any code using the feed plugin should be able to set its own
sheet or whatever content is needed.
There are a couple of options to be analyzed:
1. regarding the content of the feed article document:
a) any feed article includes a sheet
b) any feed article contains some content, not necessarily a sheet inclusion.
2. regarding the way the content is set:
a) through a String variable in the feed API, that can be set by the user
through a call like xwiki.feed.setDefaultFeedDocContent("some content"),
which defaults to the current value, for compatibility with the code
already using the feed plugin.
b) through an optional parameter to the updateFeed function(s) such that,
each time the feeds are fetched the content can be specified
3. regarding the 'scope' of this default content for the feed entry document:
a) it is specific to a feed aggregator and is set in the aggregator class
b) it is specific to an update operation (as mentioned on 2.b)
c) it is specific to the feed plugin and all documents through that plugin
instance will have the same content (as specified on 2.a)
WDYT?
The XWiki development team is pleased to announce the release of
Application Manager 1.0M2, Wiki Manager 1.0M2 and XWiki Enterprise
Manager 1.0M2.
Theses releases contains lots of bugfix and improvements.
Main new features:
- introduce new XWiki Platform 1.1.2 rights management interface.
- general improvement of Application Manager, Wiki Manager and XEM
interfaces and errors reporting.
- applications translations pages are now dynamically registered
(xar imported containing applications descriptors, translation page
added to an application descriptor, etc.)
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM10M2
Thanks
-The XWiki dev team
Just to let you know that I'm -1 right now to release the XEM project
with the newly added web-database/ module.
It breaks what we had agreed on for WARs for XE.
I might change my mind if someone can convince me of course :)
Thanks
-Vincent
Hi,
Just a warning that I'm removing the emailnotification plugin in xwiki-
plugins/ since it's now been replaced by the following 3 plugins:
* scheduler
* mailsender
* watchlist
Thanks
-Vincent
Hi all,
The statistics page needs improvement. See
http://jira.xwiki.org/jira/browse/XE-37 for a brief introduction. I
propose we take the following steps:
1) Extend the xwiki core api with:
package com.xpn.xwiki.api;
/**
* Statistics api
*/
public class StatsService extends Api{
/**
* Retrieve all-time statistics for top pages
*
* @param action Can be "view", "save", etc.
* @param space The space from which to consider pages. If space is the
empty string or null then the whole wiki is considered.
* @param count The number of page stats to retrieve.
*
* @return a list of document stats
*/
List<DocumentStats> getTopPages(String action, String space, int count){}
List<DocumentStats> getMonthTopPages(String action, String space, Date
month, int count){}
List<DocumentStats> getDayTopPages(String action, String space, Date day,
int count){}
/**
* Retrieve all-time statistics for top contributors
*
* @param space The space in which to look for contributions. If space is
the empty string or null then the whole wiki is considered. NOTE:
currently the database stores statistics regarding only the whole wiki
(e.g. the number of saves a user has made in the entire wiki, but not at
space level). To implement space-level contributor statistics I need to
consider page history, which is time-consuming (e.g. for each page in
space, for each history entry ...). I go for offering (at least for the
moment) user stats only at wiki level by removing this parameter.
* @param count The number of user stats to retrieve
*
* @return The list of user stats
*/
List<VisitStats> getTopContributors(String space, int count){}
List<VisitStats> getMonthTopContributors(String space, Date month, int
count){}
List<VisitStats> getDayTopContributors(String space, Date day, int
count){}
/**
* Retrieve the evolution of the specified activity over a period of time
*
* @param action Can be "view", "save", etc.
* @param docOrSpace The (full)name of a document or space or the empty
string / null for the whole wiki
* @param startDay The start date
* @param endDay The end date
* @param dayInterval The sample rate (e.g. at every 2 days)
*
* @return A map of (date, action count) pairs.
*/
Map<Date, Integer> getActivityPerDay(String action, String docOrSpace,
Date startDay, Date endDay, int dayInterval){}
Map<Date, Integer> getActivityPerMonth(String action, String docOrSpace,
Date startMonth, Date endMonth, int monthInterval){}
Map<Date, Integer> getActivityPerYear(String action, String docOrSpace,
Date startYear, Date endYear, int yearInterval){}
}
2) Add in the com.xpn.xwiki.api.XWiki the following method:
public StatsService getStatsService(){}
3) Extend the com.xpn.xwiki.stats.api.XWikiStatsService with:
List<DocumentStats> getTopPages(String action, String space, int count,
XWikiContext context){}
List<DocumentStats> getMonthTopPages(String action, String space, Date
month, int count, XWikiContext context){}
List<DocumentStats> getDayTopPages(String action, String space, Date day,
int count, XWikiContext context){}
List<VisitStats> getTopContributors(String space, int count, XWikiContext
context){}
List<VisitStats> getMonthTopContributors(String space, Date month, int
count, XWikiContext context){}
List<VisitStats> getDayTopContributors(String space, Date day, int count,
XWikiContext context){}
Map<Date, Integer> getActivityPerDay(String action, String docOrSpace,
Date startDay, Date endDay, int dayInterval, XWikiContext context){}
Map<Date, Integer> getActivityPerMonth(String action, String docOrSpace,
Date startMonth, Date endMonth, int monthInterval, XWikiContext context){}
Map<Date, Integer> getActivityPerYear(String action, String docOrSpace,
Date startYear, Date endYear, int yearInterval, XWikiContext context){}
4) Adjust the com.xpn.xwiki.stats.impl.XWikiStatsServiceImpl
5) In com.xpn.xwiki.api.XWiki there are 2 methods related to statistics:
* getCurrentMonthXWikiStats
* getRefererText
We could duplicate this methods in the StatsService and deprecate them in
XWiki.
6) Currently the xwiki chart macro doesn't support hidden (aka not visible
in page) data sources. This is how the char macro is used now:
{chart:type=time|source=type:table;table_number:4;...}
I propose to extend the macro to allow the following usage:
{chart:type=time|source=type:table;...}
{table}
| Series1 | Series2
2001-2 | 181.8 | 129.6
2001-3 | 167.3 | 123.2
2001-4 | 153.8 | 117.2
{table}
{chart}
This extension consists in:
* add chart macro's content to the parameters map given to the data source
* adjust the TableDataSource to use this content when no table_number is
specified
7) Create the xwiki-platform-applications/statistics application to host
the statistics related pages. Different stats will be displayed using
special panels that can be inserted into a page (see
http://llunati.xwiki.com/xwiki/bin/view/Albatross/PanelInPage for a
sample). I propose to use the Panels space for this pages (e.g use the
path src/main/resources/Panels). Vincent could help me with this.
8) Create the Stats page (aka the UI). The Stats page is now in the XWiki
space, meaning it is not accessible for the regular user (event when the
statistics module is enabled). I don't really like this. I like more how
jira.xwiki.org shows me its stats even when I'm not logged in. In the
future, I think it would be great if the users could see page/space/wiki
stats much the same they see now the xwiki code of the page (e.g. Show >
Stats). For the moment I propose to make only a single stats page
(XWiki.Stats).
That's all. WDYT?
-Marius