In the dev mailing list, I saw years ago that $datetool was changed to point to ComparisonDateTool. This gave it added functionality. Also, the documentation on http://platform.xwiki.org/xwiki/bin/view/DevGuide/Scripting says it is a ComparisonDateTool.
My problem is, it doesn't act like a ComparisonDateTool, it acts like DateTool.
Works:
$datetool.get('dd.MM.yyyy HH:mm')
Does not work:
$datetool.difference('2005-07-04','2007-02-15')
Is there a way to get a ComparisonDateTool object? And is it known that it's simply a DateTool again, or am I wrong?
Hi,
I'm trying some basic functionality on a multilanguage Wiki (3.1)
I create a class
I create the default Class sheet and add a object on it (like suggested in the default)
I create the default Class template and add a object on it (like suggested in the default)
Then I create a object;
It creates a page containing the object, I use the inline form editor to enter some data and save.
Now I want to create a translation in another language?
How should I do that?
The inline form editor does not have a "translate option", when I create a translation with the wiki editor i'm probably
create a new wiki document with a different language, but it seems to point to the SAME object. when I change the content of the object in the other language, these changes also show when I navigate back to the english page
It looks like I should instantiate a new object of the class, but then the page language is still 'en'
And how do we manage then that these objects still relate to each other? If I change the english version of a record this should be related to the content of the translations!
Gerritjan
Hi All,
I have successfully implemented XWiki 3.1 with LDAP authentication. Since
user name and password managment is addressed by the LDAP provider it doesnt
make sense to have these enabled on the LOGIN page.
What is the best way to remove these links/options from that page.
Thank you!
Chris
I have a data model that follow this page structure:
Detectors
-> Detector1
-> Detector1History1
-> Detector1History2
-> Detector2
(Implemented with my DetectorClass and DetectorHistoryClass)
The Detectors is like a dashboard for Detectors and their history. It's mostly working. My issue is that my Velocity code on that top dashboard page is looking pretty ugly. It has nested loops and I don't know how to do any encapsulation. If I could do things like detector1.getNewestHistory() that would be very helpful. But my Detector Object Class is limited to what I can define in XWiki. To my knowledge, XWiki's "user defined" classes aren't able to encapsulate code. Am I wrong?
It seems like defining my Velocity macros would help, but my understanding is a macro can't return anything, just evaluates to output.
If I'm wrong-headed, please correct me.
Thanks,
Scott
The XWiki development team is proud to announce the availability of
XWiki Enterprise 3.2 Milestone 3, the last milestone of the XWiki
Enterprise 3.2 version (see the roadmap at
http://enterprise.xwiki.org/xwiki/bin/Main/Roadmap ). Main new features
include:
* improved Lucene scoring
* new implementation of the sheet system
* support for OpenOffice 3.3 as the backend of the office importer
* better support for IE9 in the WYSIWYG editor
* many improvements in the extension manager and extension repository
* the removal of the Albatross skin from the distribution
* ... and quite a lot of dependency upgrades and bug fixes
See the full release notes at
http://www.xwiki.org/xwiki/bin/ReleaseNotes/ReleaseNotesXWikiEnterprise32M3
for more details.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
----- "Vincent Massol" <vincent(a)massol.net> wrote:
> Hi Scott,
>
> On Sep 27, 2011, at 12:34 AM, Scott Serr wrote:
>
> >
> > Can I limit livetable to display only the objects/pages under a
> certain parent page?
> >
> > Looks like this:
> >
> > Detectors (space)
> > Detectors.Detector1 (page)
> > Detectors.Detector2 (page)
> > Detectors.Detector1History1 (page with parent set to Detector1)
> > Detectors.Detector1History2 (page with parent set to Detector1)
> >
> > I have livetable on both pages Detector1 and Detector2, trying to
> display only their children history. But livetable displays all
> DetectorHistoryClass objects. (The Detector2 page shows Detector1's
> history objects) Is there a way to limit the results to only children
> of the calling page?
> >
> > I know you can do all this manually with foreach and filtering them
> out one at a time, but I'd like to use livetable.
>
> See the example at
> http://extensions.xwiki.org/xwiki/bin/view/Extension/Livetable+Macro#HFilte…
>
> Hope it helps,
> -Vincent
Thanks Vincent, I'll give it a try.
Those in charge of the xwiki web sites:
If I am not logged in, just looking at the pages the code macro can't execute!
Failed to execute the [code] macro
Thanks,
Scott
Hi all,
While gathering information on the simplify my wiki subject, I stumbled upon
the RSS makro and tried it out, works great.
But is there a way to have the RSS Links that the RSS Makro displays open in
a new window?
I know there are discussions on the sensibility of opening links in a new
window, but in this project I will have to do so.
I tried putting rel="blank" in somewhere, but nothing worked.
I tried putting a java class objekt in, but I guess since the rss feed is in
a makro, this did not work either.
Is it possible, and if yes, how?
Thanx in advance,
Wouter
Can I limit livetable to display only the objects/pages under a certain parent page?
Looks like this:
Detectors (space)
Detectors.Detector1 (page)
Detectors.Detector2 (page)
Detectors.Detector1History1 (page with parent set to Detector1)
Detectors.Detector1History2 (page with parent set to Detector1)
I have livetable on both pages Detector1 and Detector2, trying to display only their children history. But livetable displays all DetectorHistoryClass objects. (The Detector2 page shows Detector1's history objects) Is there a way to limit the results to only children of the calling page?
I know you can do all this manually with foreach and filtering them out one at a time, but I'd like to use livetable.
Thanks,
Scott
On Sep 23, 2011, at 3:20 PM, Laurence Caraccio wrote:
>
> Yes its a good 5 or 6 years old now I think but it loads and thats all that
> matters, the point of me looking into it is so that I can update everything
> to the latest versions and remove old content, cheers.
ok, good to know! :)
Thanks
-Vincent
> Regards,
>
>
>
> Laurence Caraccio