Hi,
I'd like to give the rights for the wikimodel project to reuse our
LocalEntityResolver class even though xwiki is under the LGPL 2.1
license and wikimodel under the Apache 2.0 license.
This is to fix http://code.google.com/p/wikimodel/issues/detail?id=37
I guess we need agreement from all contributors to this class. I guess
the main authors are Ludovic and myself.
So here's my +1
Thanks
-Vincent
Hi,
I just finished the implementation of full OpenID support for XWiki (see
http://jira.xwiki.org/jira/browse/XWIKI-2630). You can now create an user
account without password by using a OpenID from Yahoo, AOL, MyOpenID or any
other OpenID provider out there.
The other feature is that every XWiki user now gets a OpenID that he can use
on other OpenID sites to create an account without the need for yet another
username and password.
More infos about OpenID can be found on the official site:
http://www.openid.net/
Please test my work as much as you can. Thanks a lot
Have a nice weekend,
Markus
Hi,
We need to decide if we want our component implementations (the class
implementing the interface of a component) to be user-public or not.
By user-public I mean allowing user of the code to use them (for
composition, for inheritance). The alternative is to make them
internal and forbid users to import them. This means moving them to an
internal package (see http://www​.eclipse.o​rg/article​s/
article.​php?file=A​rticle-API​-Use/index​.html) and telling
our users that they change anytime so they shouldn't use them. This
would also mean we wouldn't have to go through a deprecation stage to
make any change to our components.
My initial reaction to this was that they should be public but the
more I think about it the more I think making them internal might be
the best choice.
WDYT?
Thanks
-Vincent
Hi all,
I spent some time on completing ApplicationResources and replacing hard
coded messages in templates and would like now to discuss some issues
regarding translations.
In my opinion, the bundles became large, unclear, use different syntax rules
(sometimes simple keys, sometimes with prefixes and underscores, sometimes
built like node-structure...) and it’s difficult to find out if some of them
are not in use anymore and if some are missing.
I agree with http://jira.xwiki.org/jira/browse/XWIKI-918 - we need to clean
up the ApplicationResources and I think we could restructure/reorganize
resources files using nodes-structure and separate first of all separate XE
from other applications (in my opinion, every application should have its
own bundles – that would allow to manage translations easily) – just create
new AppRes with the clear-defined structure.
Perhaps there are the better solutions, but I find even the splitting inside
XE on xwiki-web (templates) and xwiki-wiki (default xar) would be already
helpful for insert the new keys and removing the wasted ones.
WDYT?
Best Regards,
Alla
--
View this message in context: http://n2.nabble.com/Internationalization-and-Localization-tp789607p789607.…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Greetings
It's possible to rename a tag present in diferent pages at once, or the only way is opening all the pages
where it is and rename it?
Best regards
Bruno Neves
Hi Vincent,
1) add props.setPruneTags("script, style"); in DefaultHTMLCleaner.
This will remove all the script and style tags and their contents.
script and style tags are useless for the later use, IMO.
2) remove the first p tag following th li tag.
<ul>
<li><p>test</p></li>
</ul>
could not render properly in xwiki syntax 1.0 and
xhtmlparser+xwikisyntaxrendering.
It should change to
<ul>
<li>test</li>
</ul>
I have a filter with w3c dom:
http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-plugin-officeimporter/src/…
Maybe can help. If you need a jdom version, I can provide it later if necessary.
3) empty link. like <a/> <a href="">test</a> <a>something</a>
http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-plugin-officeimporter/src/…
this filter can remove empty link tag.
Thanks
Wang Ning
Hi Vincent,
Sorry for not send the mail to the dev list. I just reply the mail.
On Sun, Aug 24, 2008 at 4:15 PM, Vincent Massol <vincent(a)massol.net> wrote:
>
> On Aug 24, 2008, at 6:40 AM, Wang Ning wrote:
>
>> Hi,
>>
>> Yes, I think it's necessary, if the client want to control the output
>> directory.
>
> Ok I've thought a bit about this and here's what I propose:
>
> 1) Introduce a new ConverterOutput interface with the following methods:
> - saveImage(String imageName, InputStream imageData);
> - saveDocument(InputStream documentData);
>
> 2) Modify Converter interface to be:
>
> void convert(InputStream sourceData, OfficeDocumentType sourceType,
> ConverterOutput outputData, OfficeDocumentType outputType);
>
> 3) Provide 1 implementation of ConverterOutput for the moment (+ a mock one
> for the unit tests of the Converter): XWikiDocumentConverterOutput. This
> implementation stores the result of the conversion in a XWiki Document (it's
> name/location is passed in the constructor). In the future if we need other
> implementations we could add them (like a FileConverterOutput, etc) but
> they're not needed for now.
>
> Note 1: 3) is much cleaner and allows to move some of the code in the plugin
> to the XWikiDocumentConverterOutput class.
> Note 2: We can fully read the sourceData internally to save the input data
> to a file in a XWiki temporary directory (and thus control the output of the
> image files by jodconverter)
If want to get the xwiki temp directory to handle the output dir of
conversion in OfficeConverter, I need use
context.getWiki().getTempDirectory(context) to get the xwiki temp dir.
But I don't think I can get the xwiki temp without a xwik context.
Maybe the interface should change to
void convert(InputStream sourceData, OfficeDocumentType sourceType,
ConverterOutput outputData, OfficeDocumentType outputType,
XWikiContext context) throws OfficeConverterException;
WDYT?
--
Thanks
Wang Ning
syam_kg wrote:
>
> Hi
>
> In the Registartion section of Admin Preferences,there is a field 'Check
> Active fields for user authentication'. Could anybody please tell me what is
> meant by this. Also please explain what should be put into the fields
> 'Validation e-Mail Content ','Confirmation e-Mail Content' and 'Invitation
> eMail Content' and how xwiki validates the registration.
>
Selecting "Use email verification" causes a verification email to be
sent to the email address provided by the user at registration. Still,
this doesn't prevent the user from logging in and using his account
until following the validation link in that email.
On the other hand, selecting "Check Active fields for user
authentication" does exactly this: prevent the user from using his
account until following the validation link.
Last night I committed some values for the validation and confirmation
email, which will be part of XWiki Enterprise starting with 1.6M1. Until
1.6 is released, you can put these in your wiki:
Validation email content:
#set($wikiurl = $xwiki.getDocument("Main.WebHome").getExternalURL())
#set($wikiname = $wikiurl.substring($wikiurl.indexOf("//")))
#set($wikiname = $wikiname.substring(2, $wikiname.indexOf("/", 3)))
Subject: Validate your account on $wikiname
Hello $xwiki.getUserName("XWiki.$xwikiname", false),
This email address was used to register a new account on ${wikiname}. If
you did not make the request, please ignore this message.
In order to activate your account, please follow this link:
$xwiki.getDocument("XWiki.AccountValidation").getExternalURL("view",
"validkey=${validkey}&xwikiname=${xwikiname}")
Confirmation email content:
#set($wikiurl = $xwiki.getDocument("Main.WebHome").getExternalURL())
#set($wikiname = $wikiurl.substring($wikiurl.indexOf("//")))
#set($wikiname = $wikiname.substring(2, $wikiname.indexOf("/", 3)))
Subject: Your account on $wikiname has been activated
Hello $xwiki.getUserName("XWiki.$xwikiname", false),
Your account on $wikiname has been successfully activated. You can now
login at $xwiki.getDocument("XWiki.XWikiLogin").getExternalURL("login")
using your username ($xwiki.getDocument($xwikiname).getName()).
You must also create a wiki page at XWiki/AccountValidation and put this
content:
#if("$!{request.validkey}" != "" && "$!{request.xwikiname}" != "")
#if($xwiki.validateUser(true) == 0)
#set($loginURL = $xwiki.getURL('XWiki.XWikiLogin', 'login'))
#info("Your account has been activated. You can now <a
href='${loginURL}'>login</a>.")
#else
#warning("There was a problem validating your account. Please
contact an administrator.")
#end
#else
$response.sendRedirect($xwiki.getURL("Main.WebHome"))
#end
--
Sergiu Dumitriu
http://purl.org/net/sergiu/