Hello,
I am working on creating blog entries using xwiki. I was wondering if it would be possible to create a template for the blog entries so that they will be more structured?
Thank you for your time and help!
Hande Aksac
We need a deprecation strategy, i.e. decide for how long we keep
@deprecated methods/classes.
I propose to keep them for 2 full releases after the current version
is released as final.
For example if a method is deprecated in, say Core 1.3M2 then the
method will be removed in 1.6M1. Of course any major new release can
deprecate anything so a XWiki 2.0 is expected to break backward
compatibility.
So for methods deprecated in 1.0 we can remove them in 1.3M1, M2, etc.
WDYT?
If ok then I'll add this to our dev practice guide too.
Note that for this to be easy anyone deprecating methods should add
the information of when it was deprecated. For example:
/**
* @param time the time in milliseconds
* @return the time delta in milliseconds between the current
date and the time passed
* as parameter
* @deprecated replaced by {@link
com.xpn.xwiki.api.Util#getTimeDelta(long)} since 1.3M2
*/
public int XWiki.getTimeDelta(long time)
{
return this.util.getTimeDelta(time);
}
Here's my +1
Thanks
-Vincent
Hi,
Does anyone know why we have the following LANG property defined in
our startup scripts:
#!/bin/sh
export LANG=fr_FR.ISO8859-1
JETTY_HOME=.
JETTY_PORT=8080
JAVA_OPTS=-Xmx300m
java $JAVA_OPTS -Dfile.encoding=iso-8859-1 -Djetty.port=$JETTY_PORT -
Djetty.home=$JETTY_HOME -jar $JETTY_HOME/start.jar
I think this is bad as it's french and I don't think we should set it
for the user.
That said, if it's there its probably because it was required in the
past, hence my question here.
To summarize: anyone sees any issue if I remove that "export LANG" line?
Thanks
-Vincent
Hello,
I have managed to authenticate users with the Active directory through LDAP.
However, all the users i login were shown the error message
"You are not allowed to view this document or perform this action." when i
am at http://localhost:8080/xwiki/bin/view/Main/WebHome.
I pressume the users records are not in the Xwiki database.
Where and how do i create these records when the user first logon onto xwiki?
Regards,
----- Original Message ----
From: arnaud <adlz(a)netcourrier.com>
To: devs(a)xwiki.org
Sent: Thursday, 15 November 2007 2:01:06
Subject: Re: [xwiki-devs] ntlm with xwiki [END]
hello
FYI it works !!
just had to use the createUserFromLdap from Ldap plugin class
now user are recognized by xwiki and authenticated by ntlm! At last!
----Message d'origine----
>Date: Mon, 12 Nov 2007 22:20:27 +0100 (CET)
>De: "Jerome Velociter" <jerome(a)xwiki.com>
>A: "XWiki Developers" <devs(a)xwiki.org>
>Sujet: Re: [xwiki-devs] ntlm with xwiki
>
>Hi Arnaud,
>
>As far as your problem, I can't really help you much as I've never
>experimented custom auth. I don't know how LDAP binds the users to
actual
>XWiki users, but I suppose for this to work, you should at some point
feed
>XWikiUsers documents/objects with data from LDAP. (since LDAPAuthImpl
is
>only auth, maybe there is something else needed).
>Maybe you can ask this on the users list, as it is both more of a user
>issue, and you could get insights from those who actually use LDAP
>auth/user management.
>
>Good luck with this,
>Jérôme.
>
>>
>> hi again
>>
>> very sorry to disturbing you once again
>>
>> i saw that i can get request from wikicontext
>> so in my own auth class i can get my user
>> no longer need a servlet to send user to the login form
>> great everything is fine BUT
>>
>> first: i still have "you are not allowed to view this document ...."
when
>> the user log in
>>
>>
>> second : i can't log out
>>
>> problem look like xwiki don't know my user
>> (in my AuthImpl i did all that it's found in LDAPAuthImpl...)
>>
>> sorry again
>> (BTW if it's not the right place to ask this kind of questions, tell
me,
>> no problem...)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----Message d'origine----
>>>Date: Sat, 10 Nov 2007 23:19:23 +0100 (CET)
>>>De: "Jerome Velociter" <jerome(a)xwiki.com>
>>>A: "XWiki Developers" <devs(a)xwiki.org>
>>>Copie à: devs(a)xwiki.org
>>>Sujet: Re: [xwiki-devs] ntlm with xwiki
>>>
>>>Hello,
>>>>
>>>> First of all Sorry for creating a new topic
>>>>
>>>> thanks for your anwser Jerome.
>>>>
>>>> but Actually i have seen this feature
>>>>
>>>> i added jcifs and it works well
>>>> an other hand i have tested impletentetion for ldap its works too
>>>>
>>>> but i want a transparent authentication
>>>> so now the problem is :
>>>>
>>>> i would like to not have form login
>>>> i saw in code that we can define our login page with this property
in
>>>> xwiki.cfg :
>>>> xwiki.authentication.loginpage (if null default is
>>>> /bin/login/XWiki/XWikiLogin)
>>>>
>>>> i've changed this property but no changes when template call
>>>>
>>>> $xwiki.getURL("XWiki.XWikiLogin", "login", "xredirect=$logredir"))
>>>>
>>>> i still got the same url : bin/login/XWiki/XWikiLogin?
>>>
>>>Actually, it's the expected behavior : the call asks for the URL of
the
>>>XWiki.XWikiLogin document, under the login action and with a
xredirect
>>>query string parameter. If you changed your authentication login
page to
>>>XWiki.MyCustomLogin in the conf, the calls to login URL should ask
for
>>>that document IMO. Also, you may have to modidy a bit the skin if
you
>>> want
>>>the users to be redirected to the proper login page any case. If you
are
>>>using albatross skin, you can look over global.vm and login.vm,
there is
>>>also the header.vm file in the webapp/templates folder that calls
for the
>>>login URL.
>>>
>>>Hope it's clear enough, as I'm not sure what you exactly want to do
(In
>>>particuliar, I don't understand why you wany to post username to
>>>loginsubmit action, since you use third-party authentication).
>>>
>>>Tell us how it goes.
>>>
>>>Regards,
>>>Jerome.
>>>
>>>>
>>>>
>>>> the purpose of that is log-in link goes to my servlet , then i do
ntlm
>>>> authentication (it already works), then i post user name to
>>>> /xwiki/bin/loginsubmit/XWiki/XWikiLogin
>>>>
>>>> in the same time i do my own version of authentification (get user
info
>>>> (name mail,etc...) from another ldap without test of password cos
>>>> already
>>>> done with ntlm)
>>>>
>>>>
>>>> So! how can i redirect log-in page ? thanks a lot
>>>>
>>>> ------------------------------------------------------------
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Hi,
>>>>
>>>> You can implement your own version of the
>>>> com.xpn.xwiki.user.api.XWikiAuthService interface.
>>>>
>>>> There's already a LDAP impl existing (different from the XWiki
default
>>>> one), so you can look over that too as an example.
>>>>
>>>> Then, you must precise in the xwiki.cfg configuration file that
you
>>>> want
>>>> to use your own class, with something like
>>>>
>>>> xwiki.authentication.authclass =
>>>> com.mycompany.mypackage.MyXWikiAuthImpl
>>>>
>>>> Regards,
>>>> Jerome.
>>>>
>>>> _______________________________________________
>>>> devs mailing list
>>>> devs(a)xwiki.org
>>>> http://lists.xwiki.org/mailman/listinfo/devs
>>>>
>>>
>>>
>>>_______________________________________________
>>>devs mailing list
>>>devs(a)xwiki.org
>>>http://lists.xwiki.org/mailman/listinfo/devs
>>>
>>
>> _______________________________________________
>> devs mailing list
>> devs(a)xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
>
>
>_______________________________________________
>devs mailing list
>devs(a)xwiki.org
>http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
__________________________________
Yahoo! Movies - Search movie info and celeb profiles and photos.
http://sg.movies.yahoo.com/
Hi,
I'd like to attach an image to the current document but the image is
attached to another document. I couldn't find the answer in the FAQ.
It would be great if the {image:} radeox macro allowed for this.
Right now the only solution I'v found (which is a bit ugly) is to use an
HTML <img> tag as in:
<img src="/xwiki/bin/download/XWiki/Toolbar/image.gif" />
Any other solution I would have missed?
Thanks
-Vincent
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
Currently the albatross skin loads around 10 js and 10 css, which is
quite a lot.
We can improve loading time by:
- compression and cache (raffaello will provide Apache configs specific
to XWiki to help for that)
- merging and optimizations of css/js (I've published
http://www.xwiki.org/xwiki/bin/view/Code/MergeCSS to help on that)
- removing unused css/js (now we need to find which one are unused)
- conditional loading of css and js.
This last improvement can help us a lot since some of the css/js are not
even used in view mode, or are only used by a specific panel.
For this my proposal is to add a feature to the core to allow
conditional loading of CSS and JS files.
The current macros in the header would instead of putting CSS and JS add
a placeholder for additional CSS and JS.
Then everywhere where we need these CSS/JS (in a panel, in a wiki page,
in a template) we would call a macro #includecss or #includejs
This macro would add in the context the CSS and JS to add.
At the end of the template rendering the placeholder would be replaced
by the added CSS and JS.
The page would be served.
This would allow to manage the way CSS and JS are added.
WDYT ?
Ludovic
--
Ludovic Dubost
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
AIM: nvludo Yahoo: ludovic
Hi,
I see that under xwiki webapp there is a template directory, that contains
vm files. Same filenames are included in respective skins directory also.
So based on my understanding of how velocity files are called and invoked
upon user action, the vm files under templates directory play no role.
Also in some previous discussion it was mentioned that they were redundant
and there was a plan to separate common set of vm files into single
directory.
So I have two questions:
1. Can I delete the templates directory from my deployment.
2. If these files under this are no more required then what about deleting
them from svn istelf.
If have I have missed something and these files are required then please let
me know in what case would these be required.
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Is-templates-directory-required-any-more--tp15397359p…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi everyone and Jean-Vivien,
Jean-Vivien has done a lot of good work adding a tutorial on xwiki.org.
See http://platform.xwiki.org/xwiki/bin/view/DevGuide/MetadataLuceneTutorial
However I'm wondering where we should put it. Here's my current
thinking:
* This tutorial reflects Jean-Vivien's point of view only since it's
never been discussed AFAIK and there's no general agreement about its
content with the rest of the xwiki developers. As such I don't think
it can be located in at the same level as the other tutorials which
have been "endorsed" by the xwiki community.
I see 2 solutions:
1) We move it to the draft area and Jean-Vivien submits it for review
to the xwiki dev community. If the community agrees this is the right
way to implement it we put it with the other tutorials/
2) We move it to a contribution area that clearly marks the document
as a contributor's view and not as endorsed by the xwiki development
community. We don't have such a place today so we'll need to create
it. We could create it as a subpage of the Tutorial page in the
DevGuide or we could move it to the code zone to the code snippet
space since what Jean-Vivien has done is basically provide code
snippets to extend xwiki. It's a little bit more than a code snippet
since it's also a tutorial so I'm not sure the code zone is the best
place for it.
WDYT?
Jean-Vivien, some quick comments/questions on the content:
* Jens Karmer was the original author of the Lucene plugin. Since then
it's been worked on by numerous people.
* You shouldn't put ":" in titles
* The tutorial is missing a section at the beginning to explain what
the tutorial is about
* I haven't read the tutorial yet but if what you've done is useful
why not consider improving xwiki's core to support what you need? For
example it seems to me you're asking for a way to add custom metadata
to the lucene plugin. This could easily be added as part of the lucene
plugin API.
Thanks
-Vincent
Hi devs,
Last night I checked what happens when uploading a file, and why does
that action require huge amounts of memory.
So, whenever uploading a file, there are several places where the file
content is loaded into memory:
- as an XWikiAttachment as byte[] ~= filesize
- as an XWikiAttachmentArchive as Base64 encoded string ~= 2*4*filesize
- as hibernate tokens that are sent to the database, clones of the
XWikiAttachment and XWikiAttachmentArchive data ~= 9*filesize
- as Cached attachments and attachment archive, clones of the same 2
objects ~= 9*filesize
Total: ~27*filesize bytes in memory.
So, out of a 10M file, we get at least 270M of needed memory.
Worse, if this is not the first version of the attachment, then the
complete attachment history is loaded in memory, so add another
24*versionsize*versions of memory needed during upload.
After the upload is done, most of these are cleared, only the cached
objects will remain in memory.
However, a problem still remains with the cache. It is a LRU cache with
a fixed capacity, so even if the memory is full, the cached attachments
will not be released.
Things we can improve:
- Make the cache use References. This will allow cached attachments to
be removed from memory when there's a need for more memory
- Do a better attachment archive system. I'm not sure it is a good idea
to have diff-based versioning of attachments. In theory, it saves space
when versions are much alike, but it does not really work in practice
because it does a line-diff, and a base64 encoded string does not have
newlines. What's more, the space gain would be efficient when there are
many versions, as one version alone takes 4 times more space than a
binary dump of the content.
Suppose we switch to a "one version per table row" for attachment
history, with direct binary dump, then the memory needed for uploading
would be 6*filesize, which is much less.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/