Hi All,
I am creating a new Class using the 'AppWithinMinutes' dialogue that will hold information on projects.
Within which I am trying to add a Database List.
This list is supposed to enable users that are creating a new 'Project' page to link the page with one or more 'Clients' (each 'Client' has its own page within a 'Clients' space).
I can get a list of all the clients from which the user can select from using the following HQL:
"select doc.name, doc.name from XWikiDocument as doc where
doc.space = 'Clients' and
doc.name <> 'WebHome' and
doc.name <> 'ClientsClass' and
doc.name <> 'ClientsTemplate' and
doc.name <> 'ClientsSheet' and
doc.name <> 'WebPreferences'
order by doc.name"
however the returned list is just text, and i would like it if they were 'links' to the actual Client Page.
Is this even possible? as i've been search for hours!
Thanks in advance.
Rob Southwell
Professional Services
Helyx SIS Ltd
M: 07762 767575
T: 01684 273725
F: 01684 853430
E: r.southwell(a)helyx.co.uk<mailto:r.southwell@helyx.co.uk>
W: www.helyx.co.uk<http://www.helyx.co.uk/>
Registered in England No: 04464638. Registered Office: Millennium House, 65 Walton Street, Aylesbury, Buckinghamshire, UK, HP21 7QG
DISCLAIMER AND CONFIDENTIALITY NOTICE
The content of this email (and any attachments to it) is confidential and may contain privileged information. It is intended solely for the use of the individual(s) or entity to which it is addressed. If you are not an intended recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose, or store or copy the information on any medium.
The views expressed in this e-mail are those of the individual and not necessarily the views or opinions of Helyx SIS Ltd. Please note that the author of this e-mail is not authorised to conclude any contract on behalf of Helyx SIS Ltd by e-mail.
Hello, I'm trying to create an attachment on a page from a URL to an image,
using JavaScript and the RESTful API.
I'm not sure I'm doing it correctly of if this can be done but here's where
I'm at:
httpRequest.open('PUT', '/xwiki/rest/wikis/XWiki/spaces/Main/pages/Daily
All-Source Digest – 2013-01-05T07:30P24/attachments/Blade Header
UnClassified-S.png');
httpRequest.setRequestHeader('Content-Type', 'application/xml');
httpRequest.send('<?xml version="1.0" encoding="UTF-8"
standalone="yes"?><attachment xmlns="http://www.xwiki.org"><name>"Blade
Header
UnClassified-S.png"</name><mimeType>"image/png"</mimeType><xwikiAbsoluteUrl>"https://domain/xwiki/bin/download/ColorThemes/Nightfall/Blade%20Header%20Un…"</xwikiAbsoluteUrl></attachment>');
This example is actually using a URL to a preexisting Attachment, just
seeing if I'm getting permission errors on the server some how. I've also
tried random publicly accessible images.
I get a 200 response signaling an attachment is created and a link appears
on the page in the attachment section but the image won't display because
'it contains errors'.
Can I submit attachments this way? Do I need the actual image data, encoded
somehow?
--
View this message in context: http://xwiki.475771.n2.nabble.com/create-attachment-with-Rest-API-tp7583867…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
I have the need for two things that I don't see how to do with the current
APIs:
1/ I do not know when I call the rest API if I'm still authenticated
In the response I haven't seen a way to know if I'm still authenticated
when I do a request. If I'm not I might get little or zero result but I
usually will still get a response.
What could we do to help on this. Would it be possible to add the logged in
user in the header of the response or in the xml or json returned ? Or did
I miss something.
2/ How can I easily build the URL of an user's photo activated on his
profile ?
Currently I make a request which lists me documents with their author. In
cati's screenshot I should display a thumbnail of the user's photo. However
it seems to be the users photo does not have a fixed name and it wouldn't
be practical to have to make a query for each user to find out the photo.
Could we build a REST or XWiki api that would automatically send the
correct photo. This way just by building the URL we could have the photo of
the user in the mobile app.
Any ideas on this ?
Ludovic
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi devs,
Cathy has made a great proposal for a new skin based on bootstrap which she
call skin 4.x (
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Skin4x), the name
is already a bit outdated, and it will be in fact our 5th generation skin.
So after dodo -> albatross -> toucan -> colibri -> what next ?
Here are some proposals:
Flamingo
Pelican
Falcon
Buzzard
Eagle
Bustard
Trumpeter
Buttonquail
Jacana
Gotwit
Guillemot
Cockatoo
Cuckoo
Condor
feel free to propose others...
Currently, my own preference is Condor which is an endangered species like
the Albatross, but Guillemot or Buttonquail sounds good to me as well.
WDYT ?
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
Was reading http://platform.xwiki.org/xwiki/bin/view/DevGuide/Creating+a+form+with+vali…
This part seems weird...
The following code is needed in the form to launch the validation for a standard "Save" to validate the form:
<input type="hidden" name="xvalidate" value="1" />
I have to put that in the form? Why me? Where do I put that to get it in the form? Why does the wiki not just look for non-blank validation regular expression and if present, then put the above code in the rendered form?
Sorry if I am missing something obvious.
--
Mark Wallace
Principal Engineer, Semantic Applications
Modus Operandi, Inc.
709 S. Harbor City Blvd., Suite 400
Melbourne, FL 32901-1936, USA
(321) 473-1400 ext 1442
mwallace(a)modusoperandi.com<https://apps.rackspace.com/a/webmail.php?wsid=d82c52eb1782849dce8492e22617e…>
http://www.modusoperandi.com/
CONFIDENTIALITY NOTICE: The information transmitted (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521. This transmission is intended only for the person(s) or entity/entities to which it is addressed and may contain confidential and/or proprietary material. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient or have received this transmission in error, please contact the sender by reply e-mail and destroy all copies of the original message.
Hi,
I wanted to discuss about the future of the mailsender plugin ?
I've been working on a small tool to be able to send a Calendar Invitation
by email from a Meeting Notes AppWithinMinutes application and I found some
limitation in the mailsender plugin, namely you cannot add multipart
alternative email parts in addition to the text and html parts already
supported by the plugin.
I was able to hack the mailsender plugin to add a vcalendar part but it
does not really sound right to do that since we should support any part of
any content type, but this is a bigger refactoring.
I was wondering what the future is for the mailsender plugin. Do we plan to
make it a component and keep the same functionality ? Is there a plan for
an alternative component ?
And what would be the approach to add a vcalendar part in emails sent by
the current mailsender ? This would be needed to support the feature of
sending invitation emails which would be very powerfull.
Ludovic
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
The XWiki development team is proud to announce the availability of XWiki 4.5.
This version brings improvements and stabilization to the Extension Manager and Distribution Wizards. It also adds the ability to internationalize applications created with the App Within Minutes tool, and continues the improvements of the new experimental Solr search integration. This is the last release of the XWiki 4.x cycle.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki45
Thanks
-The XWiki dev team
Hello fellow XWiki developers,
I was wondering if anyone had taken the time to have a joint install of XWiki and OpenFire, apparently a fairly scalable XMPP server with nice feature completeness.
Something should be done at the UI level, such as candy-chat probably.
My question is more about the server side, there seems to be a way to write an adapter to fetch user-information from a database, so that exposing users of XWiki might be simple.
Did anyone try this already?
Did it scale?
thanks in advance
paul
Hi devs,
We've moved more and more toward an UTF-8-only application, and XWiki
has only been tested with this configuration for several years.
I propose that we require UTF-8 for a valid, supported installation.
This means:
- JVM encoding (-Dfile.encoding=UTF8)
- Container default URL encoding (Tomcat has ISO-8859-1 by default)
- Database encoding (MySql is still configured with latin1 on some distros)
There's one big site to update on our side: xwiki.org.
Here's my +1. This is a move toward a future web, since more and more
standards require (or at least assume as a default) UTF-8.
After thinking a bit more, it would make sense to require a valid
Unicode encoding, including UTF-16, which is preferable in countries
that don't use a latin alphabet. However, XWiki doesn't currently work
under 16-bit encodings at all.
--
Sergiu Dumitriu
http://purl.org/net/sergiu
Hi,
I'd like to propose to use the following naming conventions for the extensions from commons/rendering/platform that are exposed on e.x.o:
- "API" suffix for api modules. e.g. "Text API" , "Velocity API" instead of currently "Text Module", "Velocity Module", etc
- "Application" suffix for ui modules, e.g. "Wiki Manager Application", "Logging Application", "IRC Bot Application", etc
- "Macro" suffix, e.g. "JIRA Macro", etc
Technically this means using the following in pom.xml:
<properties>
<!-- Name to display by the Extension Manager -->
<xwiki.extension.name>Wiki Component API</xwiki.extension.name>
</properties>
WDYT?
Thanks
-Vincent