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" <vincent(a)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 <vincent(a)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
> <vincent(a)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 how to remove stuff, would be great
> if you
> >> guys
> >>>> could start a guide on xwiki.org about how to remove stuff and
> stip
> >> down
> >>>> xwiki!
> >>>>
> >>>> Thanks
> >>>> -Vincent
> >>>>
> >>>> On Sep 8, 2011, at 8:51 AM, Wouter de Vos wrote:
> >>>>
> >>>>> Hi Scott,
> >>>>> I am not aware of a "Strip down Guide" but I had the same issue
> here.
> >>>>>
> >>>>> What I did is just simply build op a space for the endusers, in
> which I
> >>>>> created 3 Custom Panels for navigation purposes, nothing more.
> >>>>> This you can easily do when you go to the space preferences and
> look at
> >>>> the
> >>>>> panel wizard.
> >>>>> Here you can edit panels and place them 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
> <serrs(a)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(a)xwiki.org
> >> http://lists.xwiki.org/mailman/listinfo/users
> >>
> >
> >
> >
> > --
> > Guillaume Fenollar
> > XWiki SysAdmin
> > Tel : 01.83.62.65.97
> > _______________________________________________
> > users mailing list
> > users(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/users
>
> _______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
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
Hello,
I've build my own XAR file to import pages from Oracle Database into Xwiki. The importation is OK but the pages are never indexed by Lucene. Even if I use the administration form and re-buil the index, it doesn't work.
If I create a new page directly in my Xwiki, it is indexed without any problem.
What's wrong with the importation ?
I use the stand alone installation.
Thank you very much for help
Françoise Cadin
2011/9/7 Grüner Heinrich <gruener.heinrich(a)googlemail.com>:
> Thanks,
> and how is this parameter set in a java-written component?
If you're writing a component then I advise you to use the
SkinExtension component ( see
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…
). Take a look at how the Gallery macro is using it:
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…
. Use the method that takes a map of parameters if you want to specify
the defer parameter.
Hope this helps,
Marius
>
> Am 07.09.2011 10:40, schrieb Marius Dumitru Florea:
>>
>> On Wed, Sep 7, 2011 at 10:26 AM, Stefan Bernsdorf
>> <gruener.heinrich(a)googlemail.com> wrote:
>>>
>>> Hi Marius,
>>> it would be sufficient for me, to turn off this flag when calling
>>> plugin.use('blah.js',context);
>>
>> Then, in Velocity, you simply need to write:
>>
>> $xwiki.jsfx.use("path/to/your.js", {'defer': false})
>>
>> Hope this helps,
>> Marius
>>
>>> Thanks,
>>> Stefan.
>>>
>>> Am 07.09.2011 09:00, schrieb Marius Dumitru Florea:
>>>>
>>>> Yes, see http://jira.xwiki.org/browse/XSKINX-49 .
>>>>
>>>> Hope this helps,
>>>> Marius
>>>>
>>>> 2011/9/7 Grüner Heinrich<gruener.heinrich(a)googlemail.com>:
>>>>>
>>>>> Hi,
>>>>> when I use the jsfx-plugin all script-tags will be rendered with the
>>>>> defer flag.
>>>>> Can I turn off this flag?
>>>>>
>>>>> Thanks, Stefan.
>>>>> _______________________________________________
>>>>> users mailing list
>>>>> users(a)xwiki.org
>>>>> http://lists.xwiki.org/mailman/listinfo/users
>>>>>
>>>
>
>
I've created a proxy redirection with apache2 wiki.mydomain.com to
access my wiki wich is normaly accessible through mydomain:8180/xwiki
I loose all the CSS when i access through wiki.mydomain.com ...
Somebody has an idea of what i can do ?
--
Antoine SEILLES
Doctorant (phd student)
LIRMM CNRS
Membre de l'association imagiLAB
LIRMM CNRS UM2:
UMR 5506 - CC 477
161 rue Ada
34095 Montpellier Cedex 5
FRANCE
http://www.lirmm.fr
Association imagiLAB
http://www.imagilab.fr
Tel: +33 (0)6 20 453 288
09 51 14 59 65
antoine(a)imagilab.fr
antoineseilles(a)gmail.com
Antoine.seilles(a)lirmm.fr
http://www.natoine.frhttp://natoine.developpez.com
Hello Folks,
If anybody can help me ...
I've tried to install Xwiki latest version 3.1 in tomcat through the
xwiki.war distribution.
I've followed the steps listed there :
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation
And I've the following error in catalina.out (of course tomcat/xwiki
doesn't work ^^) :
INFO: Deploying web application archive xwiki-enterprise-web-3.1.war
Sep 5, 2011 3:31:49 PM org.apache.catalina.core.StandardContext processTlds
SEVERE: Error reading tld listeners javax.servlet.ServletException:
Exception p\
rocessing TLD at resource path /WEB-INF/struts-form.tld in context
/xwiki-enter\
prise-web-3.1
javax.servlet.ServletException: Exception processing TLD at resource
path /WEB-\
INF/struts-form.tld in context /xwiki-enterprise-web-3.1
at
org.apache.catalina.startup.TldConfig.tldScanTld(TldConfig.java:555)
at
org.apache.catalina.startup.TldConfig.execute(TldConfig.java:301)
at
org.apache.catalina.core.StandardContext.processTlds(StandardContext\
.java:4307)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:\
4144)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBas\
e.java:760)
at
org.apache.catalina.core.ContainerBase.access$0(ContainerBase.java:7\
44)
at
org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(Contai\
nerBase.java:144)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:7\
38)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544\
)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:831\
)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:72\
0)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:49\
0)
at
org.apache.catalina.startup.HostConfig.check(HostConfig.java:1217)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.jav\
a:293)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecyc\
leSupport.java:120)
at
org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBa\
se.java:1306)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.\
processChildren(ContainerBase.java:1570)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.\
processChildren(ContainerBase.java:1579)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.\
run(ContainerBase.java:1559)
at java.lang.Thread.run(Thread.java:636)
Sep 5, 2011 3:31:49 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Sep 5, 2011 3:31:49 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/xwiki-enterprise-web-3.1] startup failed due to
previous erro\
rs
Sep 5, 2011 3:33:15 PM org.apache.struts.action.RequestProcessor
processMapping
SEVERE: Invalid path was requested /login
Sep 5, 2011 3:33:48 PM org.apache.catalina.core.StandardContext processTlds
SEVERE: Error reading tld listeners javax.servlet.ServletException:
Exception p\
rocessing TLD at resource path /WEB-INF/struts-form.tld in context
/xwiki-enter\
prise-web-3.1
javax.servlet.ServletException: Exception processing TLD at resource
path /WEB-\
INF/struts-form.tld in context /xwiki-enterprise-web-3.1
at
org.apache.catalina.startup.TldConfig.tldScanTld(TldConfig.java:555)
at
org.apache.catalina.startup.TldConfig.execute(TldConfig.java:301)
at
org.apache.catalina.core.StandardContext.processTlds(StandardContext\
.java:4307)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:\
4144)
at
org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java\
:1173)
at
org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServ\
let.java:549)
at
org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServ\
let.java:105)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl\
.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce\
ssorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:24\
4)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:537)
at
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:\
276)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil\
.java:162)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(App\
licationFilterChain.java:262)
at
org.apache.catalina.core.ApplicationFilterChain.access$0(Application\
FilterChain.java:192)
at
org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFil\
terChain.java:171)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Application\
FilterChain.java:167)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapper\
Valve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContext\
Valve.java:172)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentic\
atorBase.java:525)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.\
java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.\
java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVa\
lve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.ja\
va:174)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.jav\
a:874)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.\
processConnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndp\
oint.java:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFo\
llowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Thread\
Pool.java:689)
at java.lang.Thread.run(Thread.java:636)
Sep 5, 2011 3:33:49 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Sep 5, 2011 3:33:49 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/xwiki-enterprise-web-3.1] startup failed due to
previous erro\
rs
--
Antoine SEILLES
Doctorant (phd student)
LIRMM CNRS
Membre de l'association imagiLAB
LIRMM CNRS UM2:
UMR 5506 - CC 477
161 rue Ada
34095 Montpellier Cedex 5
FRANCE
http://www.lirmm.fr
Association imagiLAB
http://www.imagilab.fr
Tel: +33 (0)6 20 453 288
09 51 14 59 65
antoine(a)imagilab.fr
antoineseilles(a)gmail.com
Antoine.seilles(a)lirmm.fr
http://www.natoine.frhttp://natoine.developpez.com
HI!
Xwiki 3.1. Attachment versioning turned off. Storage is set to file system, Works fine with relatively small files.
I uploaded 700M file - no problem, a bit to wait, but works fine.
I tried then to delete this file. The result was also successful, but took nearly 1.5 minutes to finish. Is there any way to run file operations faster?
Thanks a lot.
Dmitry Bakbardin.
Hi!
By default, XWiki doesn't have "resume" ability for downloads. Is there any way to turn it on? From the moment file system storage was implemented into XE it makes sence.
And another question-idea:
On uploading big (all) files, XWiki creates hash for torrent, stores it together with file.
On Download request - user gets torrent file and starts download.
Server side strats seeding and after download is complete - kills seeding process from torrent-client.
Upload can be done almost the same way.
The question is:
Does existing XWiki functionality allow to implement such a upload-download technology?
Thanks in advance,
Dmitry Bakbardin