Dear developers,
Recently I had been checking each and every step in XWiki cyrillic management.
Brief results from last to least:
1. Office integration: no way to work with cyrillic page names http://jira.xwiki.org/browse/XOFFICE-252
2. Eclipse:: no way to work with cyrillic space names http://jira.xwiki.org/browse/XECLIPSE-154
3. $response.sendRedirect() gives ??? instead of cyrillic letters, so some scripts become useless, Parent Page search suggest in edit mode gives ??? instead of cyrillic http://jira.xwiki.org/browse/XWIKI-6955
The rest works fine, or I didn't discover it yet :-))))
As far as I understand XWiki, all these bug should live somewhere in the core, maybe somewhere else also and it's not so trivial to fix it.
The question is: what are priorities in XWiki development and is it planned to make cyrillic users happy to use all XWiki features available in nearest future?
Thanks a lot for understanding.
Kind regards.
Dmitry Bakbardin
Estaré ausente de la oficina hasta el 21/09/2011.
Responderé a su mensaje cuando regrese.
Nota: Esta es una respuesta automática a su mensaje "users Digest, Vol 50,
Issue 20" enviado el: 9/16/11 5:00:04.
Esta es la única notificación que recibirá mientras esta persona está
ausente.***************************************************************************************************************************************************************** La Información presentada en este mensaje no es considerada pública, por lo tanto es de uso exclusivo para el destinatario, quedando prohibida su copia, distribución, revelación. Si usted no es el destinatario a quien se dirige el presente correo, favor de contactar al remitente respondiendo al presente correo y eliminar el correo original incluyendo sus archivos, así como copias del mismo. *****************************************************************************************************************************************************************
Thanks for hint Vincent, these options are indeed possible and I considered
them (didn't know that svn integration is already available). But trick is
to not break usability. So that you can just switch between "tagged" content
and "trunk" without a need to overwrite "trunk" by imported XAR, or update
to revision from svn, or have another server for deploying tags as this will
definitely provoke conflicts.
For simple user that's it: switch mode, navigate in tagged/baselined
content. I guess it may not even require version control system like svn
underneath if we have all history in database anyway.
Is it in general possible to introduce such a feature that will for all
read-only actions (view, export) provide only "tagged" content? If possible
how much efforts may it need?
Did someone else experience a need in such a feature for a groupware (which
wiki belongs to as for me)?
Regards,
Andrey
On Sep 14, 2011, at 10:09 PM, Crowd Covered wrote:
>
> > Hi xwiki people,
> >
> > Is there a possibility to have something like tags or baselines for
> complete
> > wiki or particular space? What I mean is possibility to use the power of
> > navigation between pages as usual with condition that all pages revision
> in
> > this mode would belong to this "tag" or just have modification date not
> > later than specified.
> >
> > I have noticed "SVN Integration (make it possible to store and edit wiki
> > pages in SVN)" in Survey on XWiki Features (
> > http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiFeatures), but this
> > topic looks obsolete as last modification was done in January 2010.
> >
> > Background is that my team currently uses xwiki for requirements
> management
> > on a software project and it is vital to have baselines. Alternatively
> > export to PDF/RTF could be used, but firstly it refuses to handle some of
> > pages as is (we've created several classes with customized sheets), and
> > secondly it would require intensive tailoring of output to get nice
> laconic
> > document (exclude pages that are not relevant, make headers correct
> > relevantly to hierarchy, etc.)
>
> I see 2 options:
>
> * Use the existing SVN integration:
> http://extensions.xwiki.org/xwiki/bin/view/Extension/SVN+Application
> * Export the wiki as a XAR export (it''ll you one XAR file which is a zip
> file containing the full wiki which can be imported in a XWiki instance at
> any time to have a running tagged documentation) when you need to tag.
>
> Hope it helps,
> -Vincent
>
> > Greetz,
> > Andrey Stoliarov
>
Hi xwiki people,
Is there a possibility to have something like tags or baselines for complete
wiki or particular space? What I mean is possibility to use the power of
navigation between pages as usual with condition that all pages revision in
this mode would belong to this "tag" or just have modification date not
later than specified.
I have noticed "SVN Integration (make it possible to store and edit wiki
pages in SVN)" in Survey on XWiki Features (
http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiFeatures), but this
topic looks obsolete as last modification was done in January 2010.
Background is that my team currently uses xwiki for requirements management
on a software project and it is vital to have baselines. Alternatively
export to PDF/RTF could be used, but firstly it refuses to handle some of
pages as is (we've created several classes with customized sheets), and
secondly it would require intensive tailoring of output to get nice laconic
document (exclude pages that are not relevant, make headers correct
relevantly to hierarchy, etc.)
Greetz,
Andrey Stoliarov
I have created a space "Engineering".
I have changed the default space in xwiki.cfg to Engineering, this works.
A few questions:
- Is this the best way to change the default space?
- Is there a way to change the default space per group?
- Can I effectively trap a group of users into one space?
- I can hack the theme so the logo takes you back to Engineering instead of Main, but is this the best way?
Thanks,
Scott
----- "Scott Serr" <serrs(a)theserrs.net> wrote:
> 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
> _______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
Hello everybody,
I think I do have a severe problem. I created a new wiki and enabled
file system storage as described here:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Filesystem+Attachment+…
As described here
(http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Attachments) I
should be able to find the attachments in
/usr/share/tomcat5.5/work/storage/xwiki/?.
Unfortunately they are all saved in a temp directory:
/usr/share/tomcat5.5/temp/work/storage/xwiki/Main/Test_for_upload/~this/attachments
After restarting tomcat all attachments seem to be gone.
What have I done wrong?
Do I need to change anything in the tomcat configs?
Any help is appreciated,
Stephanie
Dear Users,
I found bug with cyrillic letters in velocity Scripting. Does it happen only with cyrillic?
http://jira.xwiki.org/browse/XWIKI-6955
Something similar was found in this extention http://extensions.xwiki.org/xwiki/bin/view/Extension/Extract+Wikipedia+Arti…
I wrote a comment to the page. Should I report it as a bug, or its not supported by XWiki development team?
Cyrillic users would be unhappy if scripting has such "other languages" limitations. :-(
Is it possible to fix this somehow?
As to: http://jira.xwiki.org/browse/XWIKI-6955
Same Script again. The question is:
If you enter "Smith John" in the input field, script creates page "SmithJohn". Is it possible somehow to keep the space mark between Last name and first name in the page name after script?
Thanks in advance
Dmitry Bakbardin
Hello again,
I updated my xwiki instance from 3.0 to 3.1.
I deployed the new war-file and copied ?xwiki.cfg?,
Xwiki.properties?, ?hibernate.cfg.xml? and
?mysql-connector-java-5.1.5-bin.jar? from the old instance. After die
update the colibri-skin was broken. Any ideas what went wrong?
Thank you again,
Stephanie
Hello,
I tried to get the Filesystem attachments to work. Unfortunately,
after setting the appropriate config parameters in xwiki.conf and
restarting tomcat, all attachments stored in the database are not
accessible any more.
Therefore I tried to use the Filesystem Attachment
Porter(http://extensions.xwiki.org/xwiki/bin/view/Extension/Filesystem+Atta…. The importer complains that there are no files to import,
though.
Am I missing a step here?
Thank you for your help,
Stephanie
What is considered the best way to use photos published on flickr (or any media storing and sharing source) in the XWiki
a) through the image button in the Rich Text editor, so it can be done without coding, macro's
b) a macro that you can call from the button strip in the rich text editor
There used to be a Flickr integration on the XWiki extensions, but they only work in syntax 1.0
It would be great if you can also used secured photos on flickr through safe links. User must login to XWiki, but can see foto's in flickr although when going directly
to flickr that user could not see the photo's
Today we are uploading photo's two times; once to flickr and once to XWiki, where the metadata in flickr is much richer; title, description, geotag, dat/time
We would like to replace that with a much more integrated approach; upload once see everywhere.
If other foto-sharing services are better integrated with XWiki platform, we are willing to look at these (Picasa, Facebook, ...) and migrate our photo's to these services
Gerritjan
Hi Users,
After some mails with Vincent and Scott the idea was born to make a
strip-down-xwiki guide.
The reason for this is the fact that for a lot of novice users, xwiki seems
at the first glance to complex to handle.
By making a strip-down Guide we hope to make Xwiki more accessible for a
broader audience, and thus generate more users worldwide.
In order to make this strip-down Guide as complete as possible, I would like
to ask all of you to post your thoughts and ideas on this.
For starters, here are mine, if they are allready easily solved, let me
know:
-Make the search function easier to adapt.
For instance, I have multiple spaces, and i want that the search function
only searches in certain, predifened spaces and shows the results within the
space the search was started from.
-An easy way to create a template so that users cannot copy paste in
whatever form and shape they want, but it shows a line where they can type
in the header, and below the content. All in the same style.
-An easy way to show-hide the comments box on the bottom of the page. At the
moment I use a solution where I include a document with the script to do
this in, in every page. This should be dealt with globally, and possible for
people without a lot of programming knowledge.
-The sandgrains work, but not from one space to another, at the moment I use
the include Makro to maintain my saindgrain navigation intact, but it would
be far easier if documents from other spaces where I link to, adapt the
parent from the space where I started from.
-The Logo has a predefined link to the main wiki, which causes endusers in a
space, when they click on this, to get to the main wiki page, and it
confuses them. I would like an easy way (not by editing the global.vm
template!) to personalize this.
-A wide spread opinion says, that you can just give users rights to certain
documents. But if an enduser can see a document, but not open it, the
endusers feels as if there are secrets kept from him. I want an easier way
to hide these documents completey, but show them to other users who are
allowed to see them in the same space.
-Expand and collaps user generated panels
If I create panels, their initial state is allways open, I can close them,
but when I go to anothere page, it shows the panels open again. Is it
possible to make check box within each panel in the panel wizard that allows
me to change this?
Many of these points here may seem irrelevant to many of the longtime
developers, but a lot of questions within this userlist have to do with the
usability.
For your understanding, I come from a total different corner then most of
you. I come from CM, not from programming.
But I think if we can work together on this, Xwiki will gain more users in
the end.
If anyone sees this different, let me know, lets communicate so I can start
working on the Strip down Guide.
And to all you programming masterminds out there, keep up the great work, it
made Xwiki to that what is today, thank you so much for all the efforts.
With Kind regards,
Wouter
Hi!
Xwiki 3.1. Attachment versioning turned off (xwiki.store.attachment.versioning.hint = void)
Storage is set to file system, Recicle Bin is ON.
1. xwiki/bin/view/Main/AllDocs?view=attachments - gives empty table. How one can see all attachments in a Live table?
2. To verify attachment versioning: attach several times the same file - one copy is stored as a file in a storage, version upgrades correctly - no problem.
3. I deleted an attachment. It shoild be in recycle bin:
~GLOBAL_DELETED_ATTACHMENT_ID_MAPPINGS.xml appeared in /store folder.
XML inside shows were to find files. Files are on their places as descriebed.
BUT
Recycle bin gives terrible surprise: it stores TWO COPIES of deleted file:
first is: <filename>.<extension>
second is: <filename>~v1.1.<extension>
Please note, that attachment VERSIONING is turned OFF. For big attachments (1GB and more) such a behaviour is a disaster for two reasons:
- unreasonable disk space consumption
- (probably) huge delay while user deleting attachment.
What is correct way to disallow XWiki such file duplication?
4. XWiki.DeletedAttachments gives empty table. How one can see all deleted attachments in a Live table?
Thanks a lot
Dmitry Bakbardin
Thanks a lot for for assistance, Ludovic.
Looks complicated, but at first glance at least manageable.
Will you recommend any Java-based sync tools to build completely platform independent system?
Ideal solution for me looks smth like:
- Master Wiki accepts file and stores it in FS storage
- Master Wiki initiates an event and sends it to Sync Tool / Mirror Wiki
- Sync Tool / Mirror Wiki requests file, gets it, stores it and writes success sync event in log.
Do we need to tie XWiki events with sync events, or it is safe for XWiki, when mirror database has a "new-file" record and file is not in the storage yet?
"1/ A redundant RAID5 network storage shared over Fiber Channel and NFS. This is for clustering"
Is it possible to configure XWiki to use ANY folder as a storage, OR default one is an only option? If Yes, HOW?
Some bugs are found in 3.1 with FS on. It causes attachment management problems.
http://jira.xwiki.org/browse/XWIKI-6918
http://jira.xwiki.org/browse/XWIKI-6917
Is there any fast solution? Or there is no simple solution and we should wait at least 3.2 release to manage attachments? Because for now, we don't have "legal" XWiki access to deleted attachments.
Best Regards,
Dmitry Bakbardin
09 сентября 2011, 12:51 от Ludovic Dubost <ludovic(a)xwiki.com>:
Hi Haru,
2011/9/9 Haru Mamburu <haru_mamburu(a)mail.ru>
Hi!
I was going to build on the XEM base a library with files 1Kb-1Gb inside . But on digging deeper I'm a bit desperate now: XE is an excellent platform to run the project from one side, from other - completely unclear how to make it safe :-(
Great that you working on a big database with XEM.. Sounds like a nice project
File System storage does have it's drawback, which is why we initially chose to be "all-database", but we faced the limitation of database storage for very large attachments..
Backup and Clustering are indeed more complex, but it's possible..
On filesystem storage implementation, there are several sufficient question are still beyond of understanding:
1. Clustering and/or mirroring XWiki.
When data was stored completely in the Database Engine - it was more or less clear how to build following system:
Customers -> Master Server --> Mirror Server
If Master Server is down - we easily switch customers to Mirror Server. Afterwards we restore full configuration and get back necessary redundancy.
With filesystem storage mirroring mission becomes impossible?
I suggest either
1/ A redundant RAID5 network storage shared over Fiber Channel and NFS. This is for clustering
2/ A "rdist" process that will replicate regularly the FS for mirroring only
2. Backup process.
Database data backup is also more or less clear. When filesystem storage turned on, there is painful moment of synchronizing backup moment both for data in Database AND data in Filesystem. The only Idea I have for now: stop everything, backup everything, run everything. IMO it's not the best solution due to quite annoying downtime.
Are you going to implement such a functionality inside? What is the best pactice to implement backup in a right way?
I would suggest:
1/ rdist replication + mysql replication
2/ when backuping, blocking both replication and performing the backup
At XWiki SAS we always use a MySQL replication which is the DB being backed-up. This is important to have the minimal impact on the production system. If you backup the production database directly you can have locking issues that block XWiki from operating properly.
Ludovic
If you already have a solution, kindly ask you to share the information. :-)
Best regards,
Dmitry Bakbardin
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi!
I was going to build on the XEM base a library with files 1Kb-1Gb inside . But on digging deeper I'm a bit desperate now: XE is an excellent platform to run the project from one side, from other - completely unclear how to make it safe :-(
On filesystem storage implementation, there are several sufficient question are still beyond of understanding:
1. Clustering and/or mirroring XWiki.
When data was stored completely in the Database Engine - it was more or less clear how to build following system:
Customers -> Master Server --> Mirror Server
If Master Server is down - we easily switch customers to Mirror Server. Afterwards we restore full configuration and get back necessary redundancy.
With filesystem storage mirroring mission becomes impossible?
2. Backup process.
Database data backup is also more or less clear. When filesystem storage turned on, there is painful moment of synchronizing backup moment both for data in Database AND data in Filesystem. The only Idea I have for now: stop everything, backup everything, run everything. IMO it's not the best solution due to quite annoying downtime.
Are you going to implement such a functionality inside? What is the best pactice to implement backup in a right way?
If you already have a solution, kindly ask you to share the information. :-)
Best regards,
Dmitry Bakbardin
Hello again,
I just noticed that the WYSIWYG-Editor seems also to be broken after
the update to version 3.1. At least it doesn't load anymore.
Any help is appreciated I am realy lost here.
Thanks,
Stephanie
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.