Hi,
I'm trying to increase the maximum attachment size like it says here :
http://www.xwiki.org/xwiki/bin/view/FAQ/Howtoincreasethemaximumattachmentsi…
import a larger xar 40MB)
but, when I save the XWiki.XWikiPreferences object
I get :
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
java.lang.String.substring(String.java:1762)
java.lang.String.substring(String.java:1735)
com.xpn.xwiki.web.ActionFilter.getTargetURL(ActionFilter.java:167)
com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:105)
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295)
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
Why is that?
Tomcat version: apache-tomcat-6.0.18
XE version: xwiki-enterprise-web-2.0.2
Thanks,
Anamaria
On Nov 11, 2009, at 10:47 AM, Ecaterina Valica wrote:
> Vincent,
>
> Since you changed
> platform/web/trunk/standard/src/main/webapp/templates/macros.vm
>
> you also need to change the CSS in toucan and albatros, not just
> colibri.
Right... I'm working on implementing the new strategy agreed on so far
with H1/H2 but I need more input to ensure everyone agrees - please
comment on http://jira.xwiki.org/jira/browse/XWIKI-4552
I'll update the CSS in other skins at the same time.
Thanks
-Vincent
fyi... a candidate to replace our direct lucene usage (to be compared
vs compass).
-Vincent
Begin forwarded message:
> From: Grant Ingersoll <gsingers(a)apache.org>
> Date: November 10, 2009 5:01:27 PM CEST
> To: solr-user(a)lucene.apache.org, general(a)lucene.apache.org, solr-dev(a)lucene.apache.org
> , announce(a)apache.org
> Subject: [ANN] Solr 1.4.0 Released
>
> Apache Solr 1.4 has been released and is now available for public
> download!
> http://www.apache.org/dyn/closer.cgi/lucene/solr/
>
> Solr is the popular, blazing fast open source enterprise search
> platform from the Apache Lucene project. Its major features include
> powerful full-text search, hit highlighting, faceted search, dynamic
> clustering, database integration, and rich document (e.g., Word, PDF)
> handling. Solr is highly scalable, providing distributed search and
> index replication, and it powers the search and navigation features of
> many of the world's largest internet sites.
>
> Solr is written in Java and runs as a standalone full-text search
> server
> within a servlet container such as Tomcat. Solr uses the Lucene Java
> search library at its core for full-text indexing and search, and has
> REST-like HTTP/XML and JSON APIs that make it easy to use from
> virtually
> any programming language. Solr's powerful external configuration
> allows it to
> be tailored to almost any type of application without Java coding, and
> it has an extensive plugin architecture when more advanced
> customization is required.
>
>
> New Solr 1.4 features include
> - Major performance enhancements in indexing, searching, and faceting
> - Revamped all-Java index replication that's simple to configure and
> can replicate config files
> - Greatly improved database integration via the DataImportHandler
> - Rich document processing (Word, PDF, HTML) via Apache Tika
> - Dynamic search results clustering via Carrot2
> - Multi-select faceting (support for multiple items in a single
> category to be selected)
> - Many powerful query enhancements, including ranges over arbitrary
> functions, and nested queries of different syntaxes
> - Many other plugins including Terms for auto-suggest, Statistics,
> TermVectors, Deduplication
>
> Getting Started
> --------------------
> New to Solr? Follow the steps below to get up and running ASAP.
>
> 1. Download Solr at http://www.apache.org/dyn/closer.cgi/lucene/solr/
> 2. Check out the tutorial at http://lucene.apache.org/solr/tutorial.html
> 3. Read the Solr wiki (http://wiki.apache.org/solr) to learn more
> 4. Join the community by subscribing to solr-user(a)lucene.apache.org
> 5. Give Back (Optional, but encouraged!) See http://wiki.apache.org/solr/HowToContribute
>
> For more information on Apache Solr, see http://lucene.apache.org/solr
I have a problem again.
I start my xwiki server.
I login into it. It get logged in successfully and goes to welcome page.
But whenever I try to click on any of the spaces or history or any link
available on the welcome page, it redirects to login page.
I tried with different users logins but the problem is same and I am not
able to do anything. Whenever I click somewhere it redirects to login
page.
Have I missed something?
Regards
Jasvent Singh
Hi, everybody.
I'm new here and trying XWiki right now. I used TWiki before and
considering switching from it. The main reason is better I18N support.
And the underlying code and architecture seem to be more solid.
But I found some serious bugs. Some of them are related to I18N. I've
submit them to the JIRA. But before the next major release, I hope
someone can post a patch or walkaround. Thanks.
1. In inlined form edit mode, can't select --- normal --- format.
====== http://jira.xwiki.org/jira/browse/XWIKI-4562
2. Ctrl+G with Asian characters cause AJAX: "Internal Server Error"
====== http://jira.xwiki.org/jira/browse/XWIKI-4561
3. i18n. In Blog Application. Can't create a catagory with Asian
characters. http://jira.xwiki.org/jira/browse/XABLOG-86
Problem 1 is a very sever bug. Other than that, I encountered some
problems with picture alignment and something else here&there. It's
seems to have more bugs than the normal wysiwyg editor mode.
So please someone tell me how to disable it in favor of the normal
mode wysiwyg editor.
Thanks again.
-- ZhaolinFeng.
--
-- Currahee! We stand alone together!
Hi devs,
We've always tried to follow standards in the XWiki project. I'd like
to propose that we start adhering to the WCAG ones to make XWiki even
more accessible.
The reason I'm proposing this is because XWiki SAS has been contacted
by some Dutch organization promoting the usage of standards in
Netherlands and they're interested in using XWiki for their site. As
such they need that the wiki they use also follows the guidelines...
They've found XWiki since it was one of the wikis out there that
follows most closely the guidelines.
This is our opportunity to meet the WCAG guidelines and go even beyond
(since the Dutch guidelines go slightly further I believe, see http://www.webrichtlijnen.nl/english/guidelines/)
. We would be the first wiki to meet this!
If we agree we'll need to find some ways to automate the execution of
the verifications. Right now we can test pages using this validator:
http://www.webrichtlijnen.nl/english/test/
I've started verifying this page:
http://playground.xwiki.org/xwiki/bin/view/Main/
Result:
http://www.webrichtlijnen.nl/english/test/report/74721/179372/
Some examples of failing stuff:
1) Style attribute forbidden. Everything from CSS.
Ex from home page:
<div id="globallinks"> <form action="/xwiki/bin/view/Main/WebSearch"
style="margin: 0; padding: 0;"> <div id="globalsearch"> <input
id="globalsearchinput" type="text" name="text" value="search..."
size="15" class="withTip"/><input class="button" value="Go"
type="image" src="/xwiki/resources/icons/xwiki/search.png"/> </div> </
form> </div>
...
<div class="hidden" id="spSpaceCreateForm"><form action="/xwiki/bin/
view/Main/?xpage=create" method="post"> <div> <input name="tocreate"
type="hidden" value="space"></input> <input class="panelinput"
name="title" onblur="if(this.value=='') this.value='Space name'"
onfocus="if(this.value=='Space name') this.value=''"
style="margin:auto;" type="text" value="Space name"></input> <input
type="submit" value="Create"></input> </div> </form> </div>
...
<p style="font-size:0.75em;padding-left:8px;"><a href="/xwiki/bin/
inline/Panels/QuickLinks">(Edit this panel)</a></p>
2) Need to run CSS Level 2.1 validation. Lots of error. For ex on home
page: http://bit.ly/4x9YlM
3) Apparently we made a mistake by choosing to have 2 H1 (one for
title and for headers). "The document hierarchy contains more that one
h1 tags .".
Before going further I'd like to ensure that we all agree to follow
these guidelines and put in our best practices (and ensure we verify
with some automated tests later on).
Here's my +1
Thanks
-Vincent
Hi,
I was looking for yesterday for a widget/macro/application in XWiki that
could provide a nice looking slideshow for some images (with transitions)
with no success. I finally wrote a macro by myself using velocity and
Javascript (all browsers compatible) and I would like to contribute. Thx !
--
Hoani CROSS
Globotraders Tahiti Founder [http://globotraders-tahiti.com]
Hi,
Should we make the lucene search the default search or not?
In the default XAR the Lucene search is marked as experimental. This
has been the case for a long time now.
I think we need to do something about this. Do you think the Lucene
search is working well enough to be set as the default?
WDYT?
Thanks
-Vincent
Hello all,
We are happy to inform you a new Top Level Project as been created :
XWiki Contrib. (see http://www.xwiki.org/xwiki/bin/view/Main/Forge for a
list of all Top Level Projects).
As its name state, The *XWiki Contrib Project* provides hosting for
projects related to XWiki. These projects are not part of the official
XWiki distributions and are not maintained by the XWiki development team.
The idea is that anyone with a project can be hosted in the XWiki
Contrib project. XWiki Contrib can provide projects with:
* A SVN directory in the XWiki repository
* Issue tracking on XWiki's JIRA instance
* Documentation pages on xwiki.org websites.
To find out more about it and get the all the details, we encourage you
to read the XWiki Contrib introduction at http://contrib.xwiki.org/
Now don't hesitate to request hosting for your project on the dev list
or to bother us with any question related to this project.
Thanks,
Jerome, on behalf of the XWiki Development Team.
Hi, everybody.
I'm doing some translations in l10n.xwiki.org. I found there is a link
"Get as application resource".
Its contents are:
## XWiki Translation for language zh
#Mon Nov 09 13:55:45 CET 2009
Blog.BlogClass_blogType=\u535A\u5BA2\u7C7B\u578B
Blog.BlogClass_blogType_global=\u5168\u5C40\u535A\u5BA2\uFF08Wiki\u7684\u603B\u8BC4\u8BBA\uFF09
Blog.BlogClass_blogType_local=\u7A7A\u95F4\u535A\u5BA2\uFF08\u4EC5\u7A7A\u95F4\u8BC4\u8BBA\uFF09
Blog.BlogClass_description=\u63CF\u8FF0
Blog.BlogClass_displayType=\u7D22\u5F15\u663E\u793A
Blog.BlogClass_itemsPerPage=\u6BCF\u9875\u6587\u7AE0\u6570\uFF08\u53EA\u5728\u5206\u9875\u663E\u793A\u6A21\u5F0F\u4E2D\u6709\u6548\uFF09
Blog.BlogClass_title=\u535A\u5BA2\u6807\u9898
I guess there is a way to import my translation back into my wiki,
isn't there? Or would I have to wait for the next release for my
translation to be applied?
-- ZhaolinFeng
--
-- Currahee! We stand alone together!
Hello,
I am working on creating blog entries using xwiki. I was wondering if it would be possible to create a template for the blog entries so that they will be more structured?
Thank you for your time and help!
Hande Aksac
Hello devs,
got a really newbie question and sitting on it for hours.
Your help will be appreciated. All I am trying to do is
- writing a Java class which has a method - when called
with doc name/ID will return the document title. That is all.
The following code is what Itried:
import com.xpn.xwiki.XWikiContext;
import com.xpn.xwiki.api.Api;
import com.xpn.xwiki.api.XWiki;
import com.xpn.xwiki.doc.XWikiDocument;
public class SampleService extends Api
{
public SampleService()
{
super(); /// I guess there should be XwikiContext parameter in
the constructor
}
public String myDocTitle(String:name)
{
com.xpn.xwiki.doc.XWikiDocument docu =
context.getWiki().getDocument("theSpace.theDoc", context); // I do
not where to get this context from
return docu.getTitle();
}
}
Hello all,
Following the initial discussion at
http://markmail.org/thread/kachlhm3d26g22jb I by this mail throw a vote
to move on and create the contrib project.
After giving it some more thoughts in a discussion with Vincent, here is
what I propose :
1) Create a "contrib" top level project, so create :
- The "contrib.xwiki.org" wiki with the draft at
http://dev.xwiki.org/xwiki/bin/view/Drafts/Contrib-Main-WebHome as
initial content for it's Main.WebHome
- List this wiki in the Main.Forge page on www.xwiki.org, and also
refactor a little this page using the content at
http://dev.xwiki.org/xwiki/bin/view/Drafts/Www-Main-Forge (The main
noticeable difference is the change of wording between "XWiki Products
and Extensions" to "XWiki [Top Level] Projects", and the fact platform
now belongs to the list).
- Create a contrib directory at svn.xwiki.org/svnroot/, with the
following architecture :
contrib/
|__people/
|__projects/
|__retired/
|__sandbox/
*people* will be a directory for "personal tests" projects (such as
http://svn.xwiki.org/svnroot/xwiki/sandbox/xdom/). The idea is behind is
to give whoever requests it a personal space where he can experiment
with XWiki code, and that space is private (i.e. an implied rule is that
people are not supposed to commit code in others projects, thus making
it different from sandbox projects). Each sub-folder of people/ will be
composed of the name of the person that requests his project, for
example "jvelociter".
*projects* will hosts the actual contrib projects, that are active
(meaning that they still do make sense as projects in the XWiki
ecosystem, they are not abandoned, etc.)
*retired* will be the "place where dead project go ;(" for example
http://svn.xwiki.org/svnroot/xwiki/sandbox/xeclipse-gsoc/ since it's now
replaced by the XEclipse top level project.
*sandbox* will be the new place for the current sandbox. We therefore
propose to move all sandboxed projects here (except for the retired ones
that will go straight to california).
2) Create a "XWiki Contribs" JIRA project with projects from "sandbox"
and "projects" as components. Note that we want to leave open the
possibility for big projects to have their own JIRA on our installation
as well. We will move existing issues that are right now correctly
componentized in the current XSANDBOX to the new project, and lose the
other ones (which are a couple of old closed issues AFAIR).
Here is my +1
Please let me know what you think of all this. If we agree I'd like to
make the move during the week.
Thanks,
Jerome.
Hi Everyone,
Is there any Hibernate database interface that I can use to store my own
data like design rationale object?
Hi Marius for last time I asked your that:
Could you explain a little how WYSIWYG editor can restore data using
Hibernate? Is there is a API for that or something else. Could you also
point me the package which handle the data restore?
Here is me at Graduate Forum handout XWiki flyers and people are interested
in XWiki :-)
Link:
http://picasaweb.google.com/lh/photo/mNzlYPKesLmiRRfwb2GTiA?feat=directlink
Thank you everyone! XWiki is awesome!
Hi Sergiu, all
I see in the XWikiHibernateStore that #countDocuments do distinct
documents by language while #searchDocuments does not.
I would have expect both to have the same behavior, so that we can use
them safely using the same query as input (for example for pagination).
Is there a reason for originally doing "select count(*)" versus select
"count(distinct doc.fullName)" ?
I think in any case we should have this API that does not distinct by
language. Should it replace the current behavior ? or should we add a
new API #countDocuments(String wheresql, boolean distinctFullname,
XWikiContext context) ?
Thanks,
Jerome.
Embed HTML elements pose some problems:
* they are loaded asynchronously and any attempt to access even the
simplest DOM property like nodeType through JavaScript raises an
exception if the object is not fully loaded (closed to
https://bugzilla.mozilla.org/show_bug.cgi?id=331672 ).
* they can't be fully controlled from JavaScript. The specific plugin
that handles each of them decides the display and behavior (e.g.
https://bugzilla.mozilla.org/show_bug.cgi?id=250855 a flash movie might
auto start in edit mode and, unless you want to see a movie while
editing, that's not nice).
* they aren't reloaded after they are detached and reattached to the DOM
tree using JavaScript which means that any DOM manipulation involving
one of the ancestors of a embed node can lead to the disappearance of
the embedded object. Sadly, appendChild, insertBefore and replaceChild
detach the target node before attaching it to the new location. As a
consequence there's no way to move an embed node inside the DOM tree
without detaching it.
So I propose we replace the embed HTML elements with static image
placeholders just after the edited document finishes loading. The
placeholder will have the same size as the embedded object in view mode.
Note, ckeditor already does this. You can check by copying the HTML from
http://jira.xwiki.org/jira/browse/XWIKI-3975 to the source of
http://ckeditor.com/demo .
I'm +1.
Thanks,
Marius
Hi Marius,
Thanks for your fast reply!! You were right, in my lib folder I didn't have
the same files I have in enterprise. I can see that when I did mvn install
in \plugins\skinx\target there is xwiki-plugin-skinx-1.12-SNAPSHOT.jar.
Where is meant to configure that xwiki load
xwiki-plugin-skinx-1.12-SNAPSHOT.jar and the other plugins? Because when I
imported war file in eclipse, xwiki-plugin-skinx-1.12-SNAPSHOT.jar does not
appear in plugins folder.
Now my xwiki.cfg has:
xwiki.plugins=\
com.xpn.xwiki.monitor.api.MonitorPlugin,\
com.xpn.xwiki.plugin.calendar.CalendarPlugin,\
com.xpn.xwiki.plugin.feed.FeedPlugin,\
com.xpn.xwiki.plugin.ldap.LDAPPlugin,\
com.xpn.xwiki.plugin.google.GooglePlugin,\
com.xpn.xwiki.plugin.flickr.FlickrPlugin,\
com.xpn.xwiki.plugin.mail.MailPlugin,\
com.xpn.xwiki.plugin.packaging.PackagePlugin,\
com.xpn.xwiki.plugin.query.QueryPlugin,\
com.xpn.xwiki.plugin.svg.SVGPlugin,\
com.xpn.xwiki.plugin.charts.ChartingPlugin,\
com.xpn.xwiki.plugin.fileupload.FileUploadPlugin,\
com.xpn.xwiki.plugin.image.ImagePlugin,\
com.xpn.xwiki.plugin.captcha.CaptchaPlugin,\
com.xpn.xwiki.plugin.userdirectory.UserDirectoryPlugin,\
com.xpn.xwiki.plugin.usertools.XWikiUserManagementToolsImpl,\
com.xpn.xwiki.plugin.zipexplorer.ZipExplorerPlugin,\
com.xpn.xwiki.plugin.autotag.AutoTagPlugin,\
com.xpn.xwiki.plugin.lucene.LucenePlugin,\
com.xpn.xwiki.plugin.diff.DiffPlugin,\
com.xpn.xwiki.plugin.rightsmanager.RightsManagerPlugin,\
com.xpn.xwiki.plugin.skinx.JsSkinExtensionPlugin,\
com.xpn.xwiki.plugin.skinx.JsSkinFileExtensionPlugin,\
com.xpn.xwiki.plugin.skinx.CssSkinExtensionPlugin,\
com.xpn.xwiki.plugin.skinx.CssSkinFileExtensionPlugin
And in \WebContent\WEB-INF\lib I have xwiki-plugin-skinx-1.12-SNAPSHOT.jar
but it occurs the same :(.
Thanks!!
Hi Luis,
Luis Ruiz wrote:
> Hello,
>
> I have compiled xwiki-web-standard-2.1-
SNAPSHOT + Oracle 10G but when I run
> it, everything it's ok but I can see things like this in every page:
>
> $xwiki.jsfx.use('js/scriptaculous/effects.js', true)
> $xwiki.jsfx.use('js/xwiki/widgets/modalPopup.js', true)
> $xwiki.ssfx.use('js/xwiki/widgets/modalPopup.css', true)
> $xwiki.jsfx.use('js/xwiki/widgets/jumpToPage.js', true)
> $xwiki.ssfx.use('js/xwiki/widgets/jumpToPage.css', true)
> $xwiki.jsfx.use('uicomponents/widgets/confirmationBox.js', true)
> $xwiki.ssfx.use('uicomponents/widgets/confirmationBox.css', true)
> $xwiki.jsfx.use('uicomponents/widgets/confirmedAjaxRequest.js', true)
> $xwiki.jsfx.use('uicomponents/widgets/notification.js', true)
> $xwiki.ssfx.use('uicomponents/widgets/notification.css', true)
>
> $xwiki.jsfx.use('js/xwiki/viewers/attachments.js', {'forceSkinAction':
true,
> 'language':
> ${context.language}})$xwiki.ssfx.use('js/xwiki/viewers/attachments.css',
> true
>
>
> I haven't imported an .xar yet. I even tested with a correct xwiki.cfg
from
> an enterprise windows installation but it continues doing the same. I have
> googled and I have read that I must include jsfx and ssfx plugins, but
> where?
In xwiki.cfg, there is a xwiki.plugins property whose value should contain:
com.xpn.xwiki.plugin.skinx.JsSkinExtensionPlugin,\
com.xpn.xwiki.plugin.skinx.JsSkinFileExtensionPlugin,\
com.xpn.xwiki.plugin.skinx.CssSkinExtensionPlugin,\
com.xpn.xwiki.plugin.skinx.CssSkinFileExtensionPlugin,\
Also, can you confirm you have the xwiki-plugin-skinx jar in your
WEB-INF/lib directory?
Hope this helps,
Marius
Hello all,
We need to be able to expose APIs to scripting languages. Following the
idea initially expressed by Vincent in this thread
http://lists.xwiki.org/pipermail/devs/2009-August/013934.html, I would
like to propose the following :
- We add a org.xwiki.script.ScriptService component role, which is an
empty tag interface that services class implements
- A org.xwiki.script.ScriptServiceManager implementation gets all
services injected in a roleHint/service map
- This script service manager gets injected where script bindings are
initialized and is bound "as is" with under "services" name. Currently
in two places : in the XWikiScriptContextInitializer and in the
DefaultVelocityManager (since velocity is treated separetely from JSR223
scripting languages for the moment).
I've uploaded an initial patch on
http://jira.xwiki.org/jira/browse/XWIKI-4551 if you want to give a look.
My +1
Jerome.