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
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,
Here's my proposal for internationalizing XWiki apps. The idea is to
propose several solutions for XWiki apps writers:
* Use case 1: I have lots of text on my page
- solution: use XWiki's mechanism for translating page by creating
several editions of the page in the different languages
* Use case 2: I want translation resources for my application only
and I'd like to share resources between pages
- solution: use: $msg("mykey",
"MySpace.MyTranslationDocForThisApplication")
- MySpace.MyTranslationDocForThisApplication is a standard
document to which a XWiki.PropertiesClass object is attached
- It'll search first in that doc's PropertiesClass and if not
found in XWiki's registered document bundles and if not there in
XWiki's static resource bundle files
* Use case 3: I want translation resources only for a given page
- solution: use: $msg("mykey", $doc)
- You'll need to have attached a PropertieClass object to the page
where $msg is used
- It'll search first in that object and if not found in XWiki's
registered document bundles and if not there in XWiki's static
resource bundle files
* Use case 4: I want to have a global translation resources for all
my apps in the wiki
- solution: use: $msg("mykey")
- You'll need to have created ad registered resource bundle
documents in the Wiki preferences
- It'll search first in XWiki's registered document bundles and if
not there in XWiki's static resource bundle files
Implementation details:
* Add XWikiMessageTool.get(String, String) API
* Add XWiki.PropertiesClass class in XE in the Administration
Application + a class sheet for presenting the properties nicely
WDYT?
Thanks
-Vincent
Hi all,
Sorry, these are only two very simple questions I do need to clarify to
try to go ahead to understand how to build XWiki from source.
1. Is the picture showing the list of repositories in the following link
updated?
http://www.xwiki.org/xwiki/bin/view/Community/SourceRepository
2. By using Eclipse 3.3.1.1 on a MacBook running Mac OS X 10.5.1
Leopartd must I be able to create a new project by using the New Project
wizard and checking out the proyect from SVN or this will simply
download the source?
I am a bit lost and I am not able to say if the available documentation
is updated and suitable or it will need some changes.
Thanks for your help,
Ricardo
--
Ricardo Rodríguez
Your XEN ICT Team
Hi,
As most of you should have seen by now we have a new skin on http://www.xwiki.org
.
The next step is to make that skin available as part of the XWiki
distributions and thus commit it in our SVN.
Thus we need to name it. Following our rule, we need to use bird name.
See http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HUsingbi…
for some suggestions.
So, let the vote start!
Here's my proposal: Sparrow
Thanks
-Vincent
Hi everyone,
I've committed this afternoon an Eclipse bundle "org.xwiki.appserver" in
the xwiki-sandbox, which was written by Mikhail Kotelnikov and which is
available under the Apache License.
The component declares an extension point "org.xwiki.appserver.webapps"
for registering webapps that are then loaded by the Eclipse component
"org.eclipse.tomcat". Using this component, we can then easily run the
XWiki webapp entirely from a set of Eclipse plugins + XWiki components.
A step by step tutorial for doing this is available from there:
http://www.xwiki.org/xwiki/bin/view/Community/XWikiAndEclipse_Setup
We went through this tutorial this afternoon with Fabio and everything
went fine.
The bundle may be useful for deploying easily the XWiki offline module
together with XWiki-Eclipse. We may consider replacing it by Dysoweb at
some point, which looks more powerful, but I don't have experience with
Dysoweb for now: http://dysoweb.requea.com/
Cheers
Stéphane
--
Stéphane Laurière
slauriere(a)xwiki.com
XWiki http://www.xwiki.comhttp://concerto.xwiki.comhttp://nepomuk.semanticdesktop.org
Hi,
I'm proposing again the 1.2 RC2 release, after a long delay. Since the
previous vote, a lot of bugs have been solved, mainly dealing with the
database upgrade process and the new Rights Management UI. I think that
the current code is stable enough to make it a release candidate, which
will hopefully be the last one.
Here's my +1.
Sergiu