On Jun 26, 2008, at 7:00 PM, Evelina Slatineanu wrote:
> Hi all,
>
>
>
> For the new Administration application to work properly in an empty
> wiki
> (create users, groups, set rights etc), the following files have to
> be moved
> from XE to Administration:
>
>
>
> Xwiki.Admin
>
> Xwiki.Users
>
> Xwiki.XwikiUserSheet
>
> Xwiki.XWikiUserTemplate
>
> Xwiki.AdminGroup
>
> Xwiki.AllGroup
>
> Xwiki.Groups
>
> Xwiki.XwikiGroupSheet
>
> Xwiki.XwikiGroupTemplate
>
> Xwiki.Rights
>
> Xwiki.GlobalRights
>
> Xwiki.DefaultSkin
>
> Xwiki.Skins
>
> Xwiki.XwikiPreferences
>
>
>
> I already sent the patch to JV, we only need votes. I'm +1
+1
However we need a info box to install the Admin app when the database
doesn't contain it and when the user clicks on Administration. This is
while we wait for the Setup Wizard which should force the installation
of the admin app.
Thanks
-Vincent
Hi all,
The hsqldb standalone zip distribution for XWiki Watch 1.0 RC 1 has been
released with wrong hibernate configuration file so you should use the
.jar installer until the XWiki Watch 1.0 Release Candidate 2 will be
released with the correct configuration (which is not very far in the
future).
Regards,
the XWiki Watch development team
Hi guys,
I know the installation/update is not that complicated and I discussed that
on this list some time ago, too. Nevertheless I have an (incomplete) idea to
this topic. Maybe you had this already, maybe it's not a good idea at all,
however:
Recently I had to modify the login.vm file on the server as I found no way
to change this page within XWiki. By this time I realized that I have to
write down my modification for the next update. So I thought maybe it would
be possible to change the update process a bit.
What about a web-updater? If you would create a web-updater you could show
the troublesome files and show the differences (maybe by generating for each
and every file a MD5 hash by the time you release a version) and let the
user decide how to proceed (like in Linux when an update tries to change
grub). In addition to that you could stream important release information
into this 'update'-area (new version, security stuff, etc. and, if the user
is willing to provide them, some usage-statistics). Maybe you could even
differentiate between core and plugin updates...
Cheers,
Squirrel
On Jun 26, 2008, at 1:58 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-06-26 01:58:47 +0200 (Thu, 26 Jun 2008)
> New Revision: 10823
>
> Modified:
> xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> pdf/impl/PdfExportImpl.java
> Log:
> XWIKI-2498: Exporting a page with an image to PDF fails on Jetty
> Fixed.
>
>
> Modified: xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/
> xwiki/pdf/impl/PdfExportImpl.java
> ===================================================================
> --- xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> pdf/impl/PdfExportImpl.java 2008-06-25 23:35:34 UTC (rev 10822)
> +++ xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> pdf/impl/PdfExportImpl.java 2008-06-25 23:58:47 UTC (rev 10823)
> @@ -26,6 +26,7 @@
> import com.xpn.xwiki.objects.BaseObject;
> import com.xpn.xwiki.pdf.api.PdfExport;
> import com.xpn.xwiki.util.Util;
> +import com.xpn.xwiki.web.Utils;
> import com.xpn.xwiki.web.XWikiRequest;
> import info.informatica.doc.dom4j.CSSStylableElement;
> import info.informatica.doc.dom4j.XHTMLDocument;
> @@ -221,7 +222,15 @@
> try {
> tempdir.mkdirs();
> context.put("pdfexportdir", tempdir);
> + boolean useLocalPlaceholders = !
> Utils.arePlaceholdersEnabled(context);
> + if (useLocalPlaceholders) {
> + Utils.enablePlaceholders(context);
> + }
> String content =
> context.getWiki().parseTemplate("pdf.vm", context);
> + if (useLocalPlaceholders) {
> + content = Utils.replacePlaceholders(content,
> context);
> + Utils.disablePlaceholders(context);
> + }
Shouldn't this be done in the rendering engine code?
For example in the new rendering we don't need this so it would be
easier to integrate the new rendering if this code was only found in
the old rendering code.
WDYT?
Thanks
-Vincent
>
Hi all,
For the new Administration application to work properly in an empty wiki
(create users, groups, set rights etc), the following files have to be moved
from XE to Administration:
Xwiki.Admin
Xwiki.Users
Xwiki.XwikiUserSheet
Xwiki.XWikiUserTemplate
Xwiki.AdminGroup
Xwiki.AllGroup
Xwiki.Groups
Xwiki.XwikiGroupSheet
Xwiki.XwikiGroupTemplate
Xwiki.Rights
Xwiki.GlobalRights
Xwiki.DefaultSkin
Xwiki.Skins
Xwiki.XwikiPreferences
I already sent the patch to JV, we only need votes. I'm +1
Thanks, Evelina
Hi,
In the new rendering code I need to call some code that transforms
[[[wiki:][Space.]][Doc]] into a link. I'm proposing to introduce 2 new
classes/components in Core:
* DocumentName: Represents a Document's Name. It'll have 3 properties:
- String wiki
- String space
- String page
* DocumentNameFactory: Create a DocumentName from a string
representing a Document's name. Transforms [[[wiki:][Space.]][Doc]]
into a DocumentName object.
* The DocumentNameFactory would depend on the Execution component so
that it can use the current wiki, current space and current document
if these are not specified.
* This raises the question as to whether we should continue passing a
String representing a document name in our APIs in the future or
instead pass a DocumentName. I'm not yet sure what is the best answer
to this...
* Other question: In the Document object do we store the DocumentName
object or do we store instead only Space and Wiki objects? If it's the
latter then we need to fetch them from the DB which takes time. We
could also decide to only fetch them when requested with getSpace()
and getWiki() (i.e. lazy loading).
* BTW this also raises the question as to whether we want to have a
representation for space and wiki or not and instead only use tags, in
which case a document name is simply a String like "mypage". But then
it should be unique. So it could also be made of a list of identity
tags as in: "space=sp1,sp2:wiki:wiki1:language=fr:mypage". Or we could
standardize it as "wiki1:sp1,sp2:fr:mypage" and have the
DocumentNameFactory transform it into tags. In that case the
DocumentName object would be a Map of tags + the document name
("mypage"). I think we need to decide ASAP if we want to keep the
strict and hardcoded notion of Wiki>Space>Document>Object>Property or
instead go full tags since this changes completely the v2 interfaces
and code we're writing.
Let me know what you think.
Thanks
-Vincent
Yes you are right. But in toucan skin they using png for panel design.
If i change the style its reflecting for all the panels. And in the
style.css they have handled those style.
--
Prathap
On Thu, Jun 26, 2008 at 1:26 PM, Vincent Massol <vincent(a)massol.net> wrote:
Yes it's possible. Just look at the generated page in your browser in
source view to know to what class/id to attach to.
-Vincent
On Jun 26, 2008, at 9:46 AM, Prathap Pandian wrote:
> Hi,
>>
> Is it possible to apply separate CSS for each panels in the xwiki.
>
> If its possible can any one help me to change.
>
> When i am changing the CSS is applying for all the panels.
______________________________
>
> _________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
Hi,
Is it possible to apply separate CSS for each panels in the xwiki.
If its possible can any one help me to change.
When i am changing the CSS is applying for all the panels.
--
Prathap
On Jun 26, 2008, at 1:35 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-06-26 01:35:34 +0200 (Thu, 26 Jun 2008)
> New Revision: 10822
>
> Modified:
> xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> doc/XWikiDocument.java
> Log:
> Fixing the build
ooops sorry... i had started the build to check it worked but forgot
to look at the results...
Thanks
-Vincent
Dear all,
the new version of XEclipse is almost ready and I am planning to
release it in a week.
In order to publish it through Eclipse's standard update mechanism I
need to put an "update site"[1] somewhere (see also http://jira.xwiki.org/jira/browse/XECLIPSE-51)
.
I thought about different scenarios:
1) Put the update site directly in the SVN (like http://code.google.com/p/q4e/wiki/Installation)
2) Put the update site on http://maven.xwiki.org/
3) Put the update site elsewhere.
I don't think 1) is a good idea because we would put the plugin jars
under version control, but it is nevertheless interesting because
"publishing" a new version will consist in doing a simple commit,
making the process more automatic and traceable[2]
2) is not a good idea because an update site has nothing to do with
maven.
3) is ok but I don't know where "elsewhere" could be.
So the idea is to have two update sites, one for
"releases" (http://.../xeclipse/update) and one for snapshots
(http://.../xeclipse/update/dev) where to put in a XEclipse builds. I
know that this overlaps with the maven infrastructure, but this is
what Eclipse-oriented people expect (see http://jira.xwiki.org/jira/browse/XECLIPSE-90)
And probably 1) is a good solution.
WDYT?
-Fabio
[1] An update site is simply a directory with a site.xml and all the
plugin jars, published on the web.
[2] Side-note about update sites. As far as I know there is no way for
building them in an automatic way (unless a hackish, tricky, ant-based
way). The Maven PDE plugin doesn't support it, and the artifacts
generated by the maven build cannot be assembled together in an update
site (at least not without a lot of tricky steps I am not fully aware
of). So basically the safest way to generate an update site is to do
it in the IDE and "scp -r" the result to the target location. By
putting the update site in the SVN things would be easier, because
once the update site is generated, a commit would publish it directly.
Hi,
I'd like to discuss about filtering document names when they are
created, i.e directly in the XWikiDocument.setFullName()/setName()/
setSpace()/setDatabase() methods.
We could filter out (i.e. remove) the following characters:
* pipe: |
* greater than: >
* brackets: [ and ]
* apostrophe: '
* quote: "
* colon: :
* dot: .
* forward slash: /
Any other?
The reason for ., :, |, >, [ and ] is because these are reserved
characters in wiki link format.
Another option is to allow some escaping for these chars when writing
a wiki link.
Last we need to think about documents in the DB and which already have
these chars. Should we write a migrator to filter these chars too?
Probably.
WDYT?
Some related jira issues:
* http://jira.xwiki.org/jira/browse/XWIKI-1443
* http://jira.xwiki.org/jira/browse/XWIKI-2501
Thanks
-Vincent
Hi,
I am having this weired problem.
This is the velocity line
#set($esctext = $text.replaceAll("\\s+",""))
This should suppose to remove all the whitespaces in the text.
If I execute same in java code it works fine.
However if I use it in velocity code the same not working, we get $esctext
same as $test.
Now when I change the velocity code to
#set($esctext = $text.replaceAll(" ",""))
this is working all fine, and if the $text has single whitespaces, then this
gets replaced.
Thus bottom line is that replaceAll method is working fine and there is some
issue with regexp only.
Could someone please let me know if this is general issue with velocity or
something to do with xwiki.
Any reasons why its happening so?
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Reg-exp-not-working-in-velocity-code-tp18112487p18112…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
How to restrict already existing user while registering. Currently its not
showing
any alert(information) while adding the existing user from the
administration page.
--
Prathap
Hi,
After creating a new user i want to send a mail to the particular user to
notify the registration.
Can anyone help me to do this. I think this one should be handled in server
side.
I am dump in server side.
--
Prathap
Hi fabio,
I have made the necessary modifications to the sample plugin and committed
to
the sandbox as org.xwiki.eclipse.editor.I have only refactor the code .
No additional functionality was added to the previous plugin I have send to
you by mail
I'll start looking at the vinsents parser as you requested.
Is there any news from Venkatesh also
cheers
-- Malaka Ekanayake
CSE UOM
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.5 Milestone 2.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
Last milestone of the XWiki Enterprise 1.5 version.
Main changes:
* [Experimental] New ability to set the wiki syntax used in a page
(Confluence,MediaWiki,TWiki,JSPWiki,Creole), thanks to the new
Rendering Engine
* Brand new Administration Application (see http://tinyurl.com/4qym7w)
* Universal Edit button support (see http://universaleditbutton.org/)
* Reduced execution time of Selenium tests (from 12-15 minutes to 7 minutes)
* An administrator can modify a user profile or password when
visiting a user profile page
* The copy page feature is now available from the top menu (Actions > Copy)
* XWiki properties names are now translatable
* new renamePage method in the XML-RPC API
* Slightly modified header
* New Croatian translation
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise15M2
Note that the general goals of XE 1.5 are :
* More bug fixes
* Better performance
* More automated tests
* Overhaul of the Administration
Thanks,
The XWiki dev team
Ok fine thanks
--
Prathap
On Wed, Jun 25, 2008 at 4:57 PM, Evelina Slatineanu <
evelina.slatineanu(a)xwiki.com> wrote:
> Hi,
>
> Yes, this is a known issue that will be fixed as soon as possible.
>
> Thanks,
> Evelina
>
> -----Original Message-----
> From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] On Behalf Of
> Prathap Pandian
> Sent: Wednesday, June 25, 2008 1:57 PM
> To: XWiki Developers
> Subject: [xwiki-devs] Registration Alert
>
> Hi,
>
> How to restrict already existing user while registering. Currently its not
> showing
> any alert(information) while adding the existing user from the
> administration page.
>
> --
> Prathap
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 3216 (20080625) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 3216 (20080625) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
Sergiu,
I think it would be beneficial to document below that the filters must
be run on this order and explain why. WDYT?
Thanks
-Vincent
On Jun 24, 2008, at 2:00 PM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-06-24 14:00:10 +0200 (Tue, 24 Jun 2008)
> New Revision: 10662
>
> Modified:
> xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/web.xml
> Log:
> XWIKI-891 and XWIKI-1771: Fix regression caused by wrong filter
> order (non-ASCII chars in ISO-8859-1 are lost).
>
>
> Modified: xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/
> web.xml
> ===================================================================
> --- xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/
> web.xml 2008-06-24 10:52:43 UTC (rev 10661)
> +++ xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/
> web.xml 2008-06-24 12:00:10 UTC (rev 10662)
> @@ -9,15 +9,6 @@
> <display-name>xwiki</display-name>
> <description>XWiki Application</description>
>
> - <!-- A filter that allows requests to be saved and reused later.
> For example when the current request contains an expired
> - authentication token, and the authorization module redirects
> to the login page, all the information sent by the
> - client would be lost; this filter allows to save all that
> information, and after a successful login, injects the
> - saved data in the new request. -->
> - <filter>
> - <filter-name>RequestRestorer</filter-name>
> - <filter-class>com.xpn.xwiki.web.SavedRequestRestorerFilter</
> filter-class>
> - </filter>
> -
> <!-- Filter that sets a custom encoding to all requests, since
> usually clients don't specificy
> the encoding used for submitting the request, so by default
> containers fall back to the
> encoding globally configured in their settings. This allows
> XWiki to use a custom encoding,
> @@ -41,12 +32,21 @@
> </init-param>
> </filter>
>
> + <!-- A filter that allows requests to be saved and reused later.
> For example when the current request contains an expired
> + authentication token, and the authorization module redirects
> to the login page, all the information sent by the
> + client would be lost; this filter allows to save all that
> information, and after a successful login, injects the
> + saved data in the new request. -->
> + <filter>
> + <filter-name>RequestRestorer</filter-name>
> + <filter-class>com.xpn.xwiki.web.SavedRequestRestorerFilter</
> filter-class>
> + </filter>
> +
> <filter-mapping>
> - <filter-name>RequestRestorer</filter-name>
> + <filter-name>Set Character Encoding</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
> - <filter-name>Set Character Encoding</filter-name>
> + <filter-name>RequestRestorer</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
hi Vincent/Fabio,
*According to my knowledge partitions should not be overlap.But the XDOM
model is nested.
I think this might be a problem. The sample plugin I have made is also
base on partitioning the entire document to non overlapping reagents so each
partition can be then subjected to syntax coloring.
*I tried to use the existing api(rule bale partitions) to nested syntax as
well .But it turned out difficile
*I need help on this.
*WDUT ?
Thanks
-Malaka
--Malaka Ekanayake
CSE UOM
I configured my Chinese Wiki, but in the wysiwyg editor I can only select
some English font-family. What can I do if I want to add some Chinese
font-families? Should I modify some .js files in tinymce.
Please anyone knows that give me some suggestion, thanks a lot.
--
View this message in context: http://www.nabble.com/How-to-add-new-font-family-to-XWiki-tinymce-tp1805443…
Sent from the XWiki- Dev mailing list archive at Nabble.com.