I really love the look and use of the xwiki products, but the lack of
documentation and broken functionality is very frustrating. After finally
getting smtp authorisation working in Enterprize I find the email which is
generated is not forming URLs properly - grrr.
So now I'm back to exploring Workspaces milestone 1.2 and I have found that
setting Public Registration to Allow or Deny makes no difference -
registration is just a matter of supplying a name and email address and
you're in. No admin approval required. This is not acceptable for an admin
setup intended for staff only.
Can anyone explain to me how this might be fixed please?
Cheers
Chris Ellis
Lorne-Aireys Inlet P-12 College
Hello,
sometimes after inserting Links in the WYSIWYG-Editor and saving the
Document,
mistakes occur on the site.
Example before:
Nach einer korrekten [[Benutzeranmeldung am
WebClient>>BenutzeranmeldungAmWebClient]] einschließlich einer
Autorisierungsprozedur hat der ...
Example with mistake:
Nach einer korrekten
org.xwiki.gwt.dom.client.Element#placeholder[[BenutzeranmeldungAmWebClient]][[">Benutzeranmeldung
am WebClient>>/xwiki/bin/view/CSC_AfTD_Hilfe/BenutzeranmeldungAmWebClient]]
einschließlich einer Autorisierungsprozedur hat der ...
I hope that you can help me soon.
Looking forward to your reply.
Best wishes
Norbert
[Germany]
--
View this message in context: http://n2.nabble.com/Problems-with-links-tp4435123p4435123.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi everyone (devs and users),
While we have a clear governance for write access to our source
repository (http://dev.xwiki.org), we're missing a clear governance
for xwiki.org. The idea is to address mainly the following 2 questions:
1) who "owns" it and thus "controls" (or rather provides direction
for) its content
2) can it be used for business advertising (support, paid packages,
consulting services)
Bit of History about XWiki SAS
========================
- XWiki SAS (http://xwiki.com) is the company founded by Ludovic
Dubost the creator of XWiki (I'm the CTO of XWiki SAS in addition to
being a committer here).
- Most of the active contributors are also employed and paid by XWiki
SAS to develop the XWiki software. Today that's
-- 12.5 committers (developers)
-- 1 open source product manager (see http://markmail.org/thread/ggaaw4u6yyci4oan
for its definition)
-- 1 designer
-- 1 tester/technical writer
- XWiki SAS sells services around the open source software, see http://www.xwiki.com/xwiki/bin/view/Services/
- XWiki SAS truly believes and understands open source, see http://www.xwiki.com/xwiki/bin/view/About/Values
-- I also wrote a blog post on this some time back: http://massol.myxwiki.org/xwiki/bin/view/Blog/XWikiSASAndOpenSource
- XWiki SAS has promised "not to do evil" ;), see its manifesto at http://www.xwiki.com/xwiki/bin/view/About/Manifesto
- XWiki SAS is paying for the servers and maintenance of xwiki.org,
myxwiki.org, the maven repo, the svn repo, the hudson build serversn
the free JUG farm, and more
Issue at hand
===========
XWiki SAS would like to generate more revenue to be able to increase
the development pace of the XWiki software. We'd like to fund even
more the development of XWiki, so that it becomes an even better
product. We've asked you what you'd like to see in the future in XWiki
and you've answered on this survey result:
http://www.xwiki.org/xwiki/bin/view/Blog/Features+Survey+Results
We'd like to implement those features as fast as possible.
For this we need to ensure that users interested in commercial
services find easily the way to http://xwiki.com, even when they
arrive on xwiki.org.
This is true for XWiki SAS's services but also for any company willing
to offer services around the XWiki open source project. There's no
magic. Developers need to be paid when they work full time on some
project. We need a commercial ecosystem around XWiki for it to
progress as quickly as its competitors (the collaboration market). We
need to allow for commercial companies the ability to generate revenue
from their work on the XWiki open source project. However we also want
to continue ensuring that all the XWiki development is done in open
source, under a LGPL license.
Governance Proposal
=================
1) xwiki.org is controlled by the XWiki committers. This means that
important changes brought to it should be discussed/vote on the list,
using the same practices as for code commits
2) xwiki.org stays open in edit mode to all external contributors (and
XWiki committers continue to monitor it to remove spam, etc)
3) we agree to start with 3 zones where companies can advertise their
commercial offers on top of the XWiki open source product:
-- On the download page (for business packages, subscriptions, hosting)
-- On the support page (for services: support, consulting)
-- (still to be defined) Possibly on a "Products" tab in the new
horizontal navigation. The idea would be to do as jboss.org is doing.
Projects are open source and community and Products are commercial
4) the company offerings are listed by their amount of contributions
to the XWiki open source project. The company that contributes most
(XWiki SAS today) gets the best spots (top of the list, bigger space)
5) Companies who want to be listed should provide some proof of their
contributions to the XWiki open source project
6) XWiki SAS gets some acknowledgment for paying for the xwiki.org
server/maintenance of it. Probably somewhere in the footer of the site
or on side panel somewhere
7) xwiki.org should always remain a site for the xwiki open source
community
Conclusion
=========
We want to stress that this proposal is not about XWiki SAS making a
commercial takeover of the xwiki.org site.
It's about recognizing that if the XWiki open source software
progresses quickly today, it's thanks to contributors but also for a
very large proportion to companies paying developers to work on it,
either directly (like XWiki SAS or other companies that have
developers contributing) or indirectly (by paying for example XWiki
SAS or other companies to work on specific features).
It's also about recognizing that XWiki SAS is happy to see other
companies willing to contribute to the progress of the XWiki open
source project and thus to provide a place for these companies to be
visible too.
I hope that all our contributors but also users of the XWiki Open
Source software will find this proposal acceptable and I welcome any
feedback on it.
Thanks
-Vincent Massol
Hat 1: XWiki SAS CTO
Hat 2: XWiki committer
Hello
I've translated WYSIWYG editor's Strings.properties file into my language.
Then I've putted it into place ( .../wysiwyg/client/editor) with name
Strings_sk.properties but editor is still in English.
What I am doing wrong?
--
View this message in context: http://n2.nabble.com/WYSIWYG-editor-language-in-user-interface-tp4440246p44…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi,
I was wondering if it was possible to remove the comments, attachments, history and information tabs from certain pages. Perhaps just by inserting some css or javascript on the pages where I don't want these things to show.
Also, I was hoping to reduce the font size of the "Create New Post" text in the blog (I'm using the toucan skin if that helps). Which file would I look in do to this?
Any help here would be greatly appreciated.
Cheers,
Josh
_________________________________________________________________
Find out what’s new with your friends Download the new Windows Live Messenger
http://download.live.com/
Greetings Folks,
I have setup XEM with application etc to deploy multiple wiki's and it is working a treat. Only one problem though. Most of our wiki instances are for private access only.
So under RIGHTS I have checked "Prevent unregistered users from viewing pages, regardless of the page or space rights" which works exactly how I would expect it too except for one thing, the style does not cary from the wiki onto the login page.
I am only new to the xwiki world, if somebody could point me in the right direction (documentation etc) that would be great.
Thanks
Ben
Hello all,
I saw in the xwiki.org documentation that to have auto numbered sections, i have to modify xwikivars.vm.
Is there a way to do the same but from the browser by editing the skin for example ?
Else do i have to add this code in each document ?
#set ($context.tocNumbered = true)
#set ($context.tocData = $tdoc.getTOC(2, 6, true))
Regards,
Christophe Périnaud
Windows Server 2003 SP2 in a VMWare instance
Oracle 10g
Java 1.6.0_12
Xwiki 2.0.3 from the pack Jetty/HSQL
--------------------------------------------------------------------------------
This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies.
While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection.
KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1
For custom application I need to add more properties
for ../xwiki/bin/edit/XWiki/XWikiUsers?editor=class
Is it acceptable/recommended way or other (more complicated?) approach
would be better?
Do you have any experience?
Thanks in advance,
Valdis
I noticed that if I create a new blog entry with the same title as an
existing entry in that same category the old one will be wiped out. Is this
expected behavior or a bug? Using xwiki 2.04.
daniel
--
View this message in context: http://n2.nabble.com/New-blog-entry-overwrites-old-tp4475221p4475221.html
Sent from the XWiki- Users mailing list archive at Nabble.com.