[xwiki-users] rename page during it's object's inline edit save?
I have a page that is creating sub-pages with a button called Create History Log. I create the sub-page name like HistoryLog-2011-09-27 from the current date programatically. These sub-pages have a HistoryLogClass object on them which I begin editing in the inline editor. During the save operation on this object, I'd like to rename the page if the user has changed a date property on the object. Is there a way to do this? I'd like it to work when creating a new page or editing and existing page with the inline editor. Reasoning: The user is creating a HistoryLog page (with object) a few days after the fact, so they need to manage the date manually sometimes. I like having the date in the page name, to make a unique and sortable page list. The user would like to not go through the extra step of renaming the page manually. Sort of like this for page creation: $doc.name = HistoryLog- + $obj.getProperty(date).getValue() Would I need to run $doc.rename() code when editing? Is there a clever solution? Thanks, Scott ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] possible bug - inline editor evaluates form hidden variables on save
- Marius Dumitru Florea mariusdumitru.flo...@xwiki.com wrote:
On Thu, Sep 29, 2011 at 9:19 PM, Scott Serr se...@theserrs.net
wrote:
I ran into an interesting side effect of having a form in my Class
Sheet.
input type=hidden name=parent value=${doc.fullName} /
The above line is in a form which posts to the current page, but
then redirects to a sub-page. The process is exactly like the FAQ
Example. The trouble is, when doing Inline Editing on a page with the
class object. No matter what you put in as the parent in the UI for
the parent property, it gets reset to itself on save. The wiki and
WYSYWIG editors don't do this of course.
I think this is a problem because...
1. Should this form (and form element) really be evaluated? No one
hit the submit button.
How did you save without hitting the submit button? (You said it
gets
reset to itself on save).
2. It doesn't seem very safe for variable spaces to mix so easily.
Unless this is a feature.
Inline form edit mode is used to edit object properties. If you use
$doc.display method to generate your form fields then you'll see that
the field IDs/names look like this:
ClassName_objectIndex_propertyName
, so they don't interfere with the rest of the (hidden) fields like
parent which is used to set the document title. If you generate the
form fields yourself then indeed you have to take care to use unique
IDs/names to prevent conflicts.
Hope this helps,
Marius
Thanks for the reply.
My page has a form like {{{html}}}form/form{{{/html}}} if you look at the
wiki code. I'll call this the embedded form. So when the page is viewed,
then the embedded form is available. An aside, the embedded form creates
sub-pages. The page also has an object and I'm fine with editing those
properties in the inline form editor. And, of course the embedded form on my
page is not displayed because the inline editor only shows and edits the
object. My trouble comes here, when I save that object in the inline editor, I
get the embedded form's hidden post variables evaluated. I did not click my
embedded form's submit, I clicked the inline editor's save. It behaves as if I
clicked the embedded form's submit just before the inline editor's save.
I know it sounds crazy. I'll try to isolate it to a minimal test case.
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] possible bug - inline editor evaluates form hidden variables on save
I ran into an interesting side effect of having a form in my Class Sheet.
input type=hidden name=parent value=${doc.fullName} /
The above line is in a form which posts to the current page, but then redirects
to a sub-page. The process is exactly like the FAQ Example. The trouble is,
when doing Inline Editing on a page with the class object. No matter what you
put in as the parent in the UI for the parent property, it gets reset to itself
on save. The wiki and WYSYWIG editors don't do this of course.
I think this is a problem because...
1. Should this form (and form element) really be evaluated? No one hit the
submit button.
2. It doesn't seem very safe for variable spaces to mix so easily. Unless this
is a feature.
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] $datetool appears to be a DateTool and not a ComparisonDateTool
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. 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?
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] $datetool appears to be a DateTool and not a ComparisonDateTool
- Scott Serr se...@theserrs.net wrote:
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. HH:mm')
Does not work:
$datetool.difference('2005-07-04','2007-02-15')
Apparently I can't pass String as Object, I have to pass Date?
Anyway, sorry for the traffic.
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] data model and velocity
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 ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] livetable only on objects/pages under parent
- Vincent Massol vinc...@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#HFilterorganizationsbydomain 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 ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] livetable only on objects/pages under parent
- Scott Serr se...@theserrs.net wrote: - Vincent Massol vinc...@massol.net wrote: Hi Scott, snip See the example at http://extensions.xwiki.org/xwiki/bin/view/Extension/Livetable+Macro#HFilterorganizationsbydomain 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 I'm sorry, I just tried again as not logged in and it worked. I think there must be some heavy loading on the xwiki server or something which causes the code macro not to execute some of the time. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] livetable only on objects/pages under parent
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 ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] scripting - attachment combined with object
[I'm hoping that scripting belongs here an not in the dev list] I'm trying to tie an attachment to an object. Say, I want to create several TrackingClass objects on a page. But one of the properties I'd like to be a PDF and link. (Or fake it to look like it) I know the properties of a class are primitives plus a few like DbList etc. The table would have these headings: Tracking Date| Description | PDF Link At the bottom of the page I'd have an Add object form: Tracking Date: Description: Attach PDF: [Add Button] This is like the Creating a FAQ Application example, but with an attached file in the same form submit. I'm wondering how one might solve this problem? Thanks, Scott ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] minimal xwiki configuration SPACES
I have created a space Engineering. I have changed the default space in xwiki.cfg to Engineering, this works. A few questions: - Is this the best way to change the default space? - Is there a way to change the default space per group? - Can I effectively trap a group of users into one space? - I can hack the theme so the logo takes you back to Engineering instead of Main, but is this the best way? Thanks, Scott - Scott Serr se...@theserrs.net wrote: Vincent and Wouter -- thanks for the great responses. I'll try to take your advice and tweak just a space for normal users. One thing I've identified that would be nice, but I don't know how to do... I'd like the Document Metadata panel that is below the content panel to _not_ appear, unless someone selects Comments, Annotations, Attachments, History, Information in the top right corner of the content panel. I think this must be possible, the reason, why else would there be two ways to navigate to it -- top right of content _and_ tabs on meta panel. (I'm aware of turning off each Doc Metadata tab from the Page Elements... but I don't want them off, just not expanded out.) ^ That would simplify the look quite a bit. I've started some notes so I can reproduce what I'm doing at some point: (scripting myself) Create a new group Wiki Users Create some users as Wiki Users Login as them to see what a non-admin sees Probably have 2 different browsers to keep flipping back and forth Create a new Space, one which will be the normal user's default Keep default skin so you don't stray from supported world Go to Administer Wiki - Look Feel Presentation you can change the color of the default skin Page Elements - turn off left panel, turn on right panel, etc Panel Wizard - choose what you want in the right panel There are more things I'd like to do: Backlinks has redundant pages something like | sort | uniq is needed. A bug? Add Search in right panel and remove X-WIKI header of page. Header must be somewhere in the skin? Thanks guys -- I hope to help out with the minimal config page. - Vincent Massol vinc...@massol.net wrote: Hi Guillaume, On Sep 8, 2011, at 10:37 AM, Guillaume Fenollar wrote: Hi, Finally, I think it would be great to have some available .xar packages to download, not only one. It would give us the choice to build xwiki according to the features we're looking for. What you're talking about is the Exension Manager ;) … which already exists and which you can try in XE 3.2 (it's missing a nice UI but the features are there). We need the max # of people to try it out and report issue if any. Thanks -Vincent Regards Guillaume 2011/9/8 Vincent Massol vinc...@massol.net Hi Wouter, On Sep 8, 2011, at 9:25 AM, Wouter de Vos wrote: Hi Vincent, Sounds like a good plan to me, since it will make Xwiki more easy to use for content managers with no coding background, it will lower the treshold for people wanting to use xwiki. Xwiki is great, no question, but it offers so many possibilities that for people like me who focus primarily on content management and usability and are by no means PHP and JAVA geniuses, it tends to get a bit complicated. IMO approach 2) is to be preferred because of the same reason you stated allready. Maybe we can collect ideas on stripping down over the userlist, sort them, and use them to create the guide? yep that's the idea. Is there a standard layout for guides like this allready? No but the guide could be put in the Admi Guide ultimately: http://platform.xwiki.org/xwiki/bin/view/AdminGuide/ Now the practice is to start writing this stripping down guide in the draft section and as soon as it contains something we judge nice enough to move it to the final location (AdminGuide): http://dev.xwiki.org/xwiki/bin/view/Drafts/ Because then we would create it accordingly. Great. Feel free to create a page in the Draft space: http://dev.xwiki.org/xwiki/bin/view/Drafts/ Thanks -Vincent Thanks for the thoughts, Wouter On Thu, Sep 8, 2011 at 9:07 AM, Vincent Massol vinc...@massol.net wrote: Hi guys, It would be nice to have a guide on xwiki.org about this topic of stripping the default XE. Basically you have 2 approaches: 1) Don't import the default XE XAR (ie you start with an empty wiki, no pages) 2) Start with the default XE XAR and make modifications to it Choosing 1) or 2) really depends if 2) is close to what you need or not. Choosing 2) is the easiest though since it's easier to remove things than to create new stuff from nothing :) If you can tell us what you don't want, we could maybe tell you how to turn them off/make them disappear. Once we figure out together
Re: [xwiki-users] minimal xwiki configuration
accordingly in your layout. You should be aware of the fact that the users go to the main wiki (non-enduser in your case) by clicking the logo, you might want to change this, the same goes for the displayed search results. You can also predefine if endusers should see the Comment box at the bottom of the page or not, etc. IMO the great thing of Xwiki is exactly this, you are in total control of what the endusers can see and are allowed to do. I hope this helps a bit, if you have more questions please feel free to let me know. Kind regards and good luck, Wouter On Wed, Sep 7, 2011 at 10:11 PM, Scott Serr se...@theserrs.net wrote: I'd like some guidance on heading towards a very minimal xwiki configuration, at least for end users. The default xwiki UI is pretty complex. I'd like users to see this: content (edit, print) search box minimal side bar backlinks (and not much more) Is there a guide on how to strip down what a normal user sees to the bare essentials? Thanks, Scott ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Guillaume Fenollar XWiki SysAdmin Tel : 01.83.62.65.97 ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] evaluating xwiki for our needs
Greetings XWiki Users, We are a small company of 3 people. For internal use and portal, I've rolled out Trac... Then Redmine... then back to Trac. I have fond memories of my Trac install and usage 3-4 years at the big company but now that the 3 of us are on our own it doesn't seem to be that helpful. Interconnecting Wiki, Issues/Tickets, and SCM Change Sets has great powers in Trac. But we don't seem to be taking advantage of that now. A year ago, I rolled out Plone for our external web. I managed to tweak an attractive Skin/Theme. I added necessary content. Now it sits -- getting old and tired. I'm starting to evaluate XWiki. So many options on a page is a bit overwhelming, but other than that it looks very usable. My idea is to merge our external web and internal portal -- so there isn't such a distinct line drawn between our knowledge base and our customer facing pages. I think we can manage (Trac) Issues/Tickets less formally on a wiki page. The SCM integration was nice, but a simple Source Repository Viewer might be all we need. We are all familiar with Java and normally use Linux. The WebDav fs features look nice. I'm concerned about vitality. Maybe half of the references for XWiki are stale -- site being dead or running something else now. I'm concerned about security. I'm concerned about resource footprint. (I imagine it's just App Server + a little, but migrating to a VPS would costly.) Maybe I need some encouragement as I go along. :) And ideas about how to make pages look less busy. Thanks, Scott ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
