I cut at end of line (and remove empty line)

I replaced your piece of comment "#* Disabled until the content can be cleanly 
cut." in #macro(getEntryContent  of  Blog.BlogCode doc
by this one

    #if($onlyExtract)
     #set($result = '')
     #set($resultArray = 
$entryObj.getProperty('content').value.split('\s*\n\s*',10))
     #foreach ($value in $resultArray)
     #if( $velocityCount > 5 )
       #break
     #end
   #set($result = "$result
$value")
 #end
   #set($result = "${result} 
[[...>>${entryDoc}||title='$services.localization.render('xe.blog.code.readpost')']]")
#end





________________________________
 De : "[email protected]" <[email protected]>
À : XWiki Users <[email protected]> 
Envoyé le : Lundi 6 octobre 2014 17h16
Objet : Re: [xwiki-users] 2 lists = 3 differents sorts on xwiki 6.2.1 and 
improve blog
 



On 6 Oct 2014 at 16:40:26, Pascal BASTIEN 
([email protected](mailto:[email protected])) wrote:

> Hello,
> On my space Webhome I have 2 lists with the same sort (modification date):
>  
> {{spaceindex space="$doc.space" sort="modificationDate"/}}
>  
> and
>  
> {{activity spaces="$!aSpace" rss=true /}}
>  
> I edited one doc with minorEdit and I obtain 3 differents sort.
>  
> I can understand why spaceindex sort is different than "activity spaces" but 
> why "activity spaces" sort is different than Main.WebRss?)
>  
>  
> Here some screenshots:
> http://snag.gy/l6iQt.jpg
> http://snag.gy/JwMVu.jpg
>  
>  
> NB: I modified BlocCode to display 5 first lines of content blog post on 
> Blog.WebHome if the blog post have an empty summary, do you interested?

We used to have this and removed it since it causes too many problems. How can 
you ensure you’re cutting at some place that doesn’t cause a problem when 
rendered?

Thanks
-Vincent


_______________________________________________
users mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/users

Reply via email to