I am trying to use Velocity to dynamically create the output for my form. If
a field doesn't have any value, then I want the code to not display. So I
came up with the following:
#if ($doc.getValue('processOverview')!='')
= PROCESS OVERVIEW =
<div style="padding-left: 25px;">
$doc.display('processOverview')
</div>
#end
However, this is not working. Velocity is ALWAYS finding something in the
field even though when I go to edit it, there is nothing there. Am I
missing something?
As a work around, I have tried to find a Trim function in velocity and also
a Lenth function. I haven't been able to find either of those. Anyone have
any suggestions?
--
View this message in context: http://xwiki.475771.n2.nabble.com/Detect-Empty-Fields-tp7589773.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
I'm working on "XAForum application" (
github.com/xwiki-contrib/application-forum2<https://github.com/xwiki-contrib/application-forum2m2>)
and I found some issues due to "Ratings application" (
github.com/xwiki-contrib/application-ratings) dependency, examples :
- Rating stars are displayed on every page (maybe the admin who installed
the application doesn't expect or want this behavior. It has already been
reported as an issue too :jira.xwiki.org/browse/XAFORUM-26)
- XAForum app vote and ratings app vote use the same object (same XClasse)
which may lead to a wrong result. XAForum vote expects only +1 (== means I
like) on a topic, however Rating app vote expects 1 to 5 (5 stars) on a
page, which means if a user rate a topic page +5, this means too, there are
5 other users like this topic, which is wrong !!
To avoid these issues, I think we need to remove the ratings app dependency
from XAForum app and implement a specific vote for this (XAForum) app.
WDYT ?
Thanks,
Sofiane Baloul
+0, snippets in XWiki 1.0 syntax are not good examples for our users.. How
many such snippets do we have on e.x.o.?
Thanks,
Marius
On Mar 21, 2014 9:52 AM, "vincent(a)massol.net" <vincent(a)massol.net> wrote:
>
> Hi devs,
>
> Sergiu implemented http://jira.xwiki.org/browse/XWIKI-8988 a while ago
and I didn't agree with it (see my comment there).
>
> I have 2 arguments:
> 1) Lots of code snippets on e.x.o are still in syntax 1.0 and if you need
to test them you still need to be able to create pages in 1.0 syntax
> 2) We shouldn't hardcode anything and right now we have hardcoded the
knowledge of the xwiki/1.0 syntax in DocumentInformation.xml:
>
> #foreach ($syntax in $availableParserSyntaxes)
> #if ($configuredSyntaxes.contains($syntax.toIdString())
&& !$syntax.toIdString().equalsIgnoreCase('xwiki/1.0'))
>
> The important part for me is that the xwiki/1.0 syntax is NOT enabled by
default in xwiki.cfg and thus users won't use it by mistake. Only those who
really need to use it would be able to use it.
>
> I'd like to reinstate the ability to use xwiki/1.0 syntax in XWiki 5.x by
removing the hardcoded check.
>
> WDYT?
>
> Thanks
> -Vincent
>
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
Hi,
One of the objectives of 6.0 is to review the existing applications on
extensions.xwiki.org, improve them and see how they would integrate in the
new Flamingo skin (while also making improvements suggestions).
This mail covers the Flamingo integration for the MoccaCalendar
application.
You can see the proposal at:
http://design.xwiki.org/xwiki/bin/view/Proposal/CalendarApplicationDesign
Any feedback is welcomed (especially from Denis and Clemens :) ).
Thanks,
Caty
+1
We have tons of if(syntax==xwiki/1.0), one less would be nice
especially when it's not that useful.
On Fri, Mar 21, 2014 at 8:52 AM, vincent(a)massol.net <vincent(a)massol.net> wrote:
> Hi devs,
>
> Sergiu implemented http://jira.xwiki.org/browse/XWIKI-8988 a while ago and I didn't agree with it (see my comment there).
>
> I have 2 arguments:
> 1) Lots of code snippets on e.x.o are still in syntax 1.0 and if you need to test them you still need to be able to create pages in 1.0 syntax
> 2) We shouldn't hardcode anything and right now we have hardcoded the knowledge of the xwiki/1.0 syntax in DocumentInformation.xml:
>
> #foreach ($syntax in $availableParserSyntaxes)
> #if ($configuredSyntaxes.contains($syntax.toIdString()) && !$syntax.toIdString().equalsIgnoreCase('xwiki/1.0'))
>
> The important part for me is that the xwiki/1.0 syntax is NOT enabled by default in xwiki.cfg and thus users won't use it by mistake. Only those who really need to use it would be able to use it.
>
> I'd like to reinstate the ability to use xwiki/1.0 syntax in XWiki 5.x by removing the hardcoded check.
>
> WDYT?
>
> Thanks
> -Vincent
>
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
Hi devs,
Sergiu implemented http://jira.xwiki.org/browse/XWIKI-8988 a while ago and I didn’t agree with it (see my comment there).
I have 2 arguments:
1) Lots of code snippets on e.x.o are still in syntax 1.0 and if you need to test them you still need to be able to create pages in 1.0 syntax
2) We shouldn’t hardcode anything and right now we have hardcoded the knowledge of the xwiki/1.0 syntax in DocumentInformation.xml:
#foreach ($syntax in $availableParserSyntaxes)
#if ($configuredSyntaxes.contains($syntax.toIdString()) && !$syntax.toIdString().equalsIgnoreCase('xwiki/1.0'))
The important part for me is that the xwiki/1.0 syntax is NOT enabled by default in xwiki.cfg and thus users won’t use it by mistake. Only those who really need to use it would be able to use it.
I’d like to reinstate the ability to use xwiki/1.0 syntax in XWiki 5.x by removing the hardcoded check.
WDYT?
Thanks
-Vincent
Could anyone point me to documentation for the ForumApplication extension
located here...
http://extensions.xwiki.org/xwiki/bin/view/Extension/ForumApplication
I would like to replace the instance of BulletinBoard in my install of Xwiki
with ForumApplication. I am able to add various forums via this page...
/xwiki/bin/view/ForumCode/ForumsHomePage
However, I seem to not be able to add more than one "new topic" per forum
via
*/xwiki/bin/view/Forums_OKC/WebHome?action=addconversation
There are some other cosmetic/administrative things I would like to do as
well, but I am thinking if there is documentation I could read it may point
me in the right direction.
Thanks in advance.
--
View this message in context: http://xwiki.475771.n2.nabble.com/Any-available-documentation-for-the-Forum…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Reviving http://markmail.org/message/hlnqke3igkbec332 for as an official vote.
We have waited way too long and I think we really need to find a
solution even if none of the committers use Windows since a long time.
Every time a Windows dev even think of contributing he is very quickly
discouraged...
As a reminder the issue is that working on XWiki source code is a pain
for MS Windows developers because of the (impossible to understand I
agree) limitation on path size.
So the idea is to find a new logical rule to drastically shorten our
paths and Sergiu proposed the following: remove duplicated information
from our paths to maven modules.
Here is an example:
xwiki-platform-core/xwiki-platform-rendering/xwiki-platform-rendering-transformations/xwiki-platform-rendering-transformation-macro
(131 chars)
would become
core/rendering/transformations/macro (36 chars)
So WDYT ?
Here is my +1
I also find it nicer when navigating using cd and tab in a unix shell anyway.
Planning to do it in 5.1 if everyone agree.
--
Thomas Mortagne
Hi devs,
Today let’s try to do a Code Coverage Day. It’s our first one and I didn’t get the time to prepare it so I propose something simple:
- The goal is to increase the jacoco TPC threshold in pom.xml files
- Everyone notes down the TPC increase they’ve brought to a module so that when we prepare the day’s report we can add them there
Reminder: to check the current TPC, run “mvn clean install -Pquality -Dxwiki.jacoco.instructionRatio=1.00”
WDYT?
Thanks
-Vincent