Hi,
I'd like to modify the configuration module so that it can support
adding dynamic configuration data (located in XWikiPreferences,
WebPreferences or other).
I'd like to propose:
* We remove the notion of ConfigurationManager
* We make ConfigurationSource components
* We create a XWikiPropertiesConfigurationSource (hint =
"xwikiproperties")
* (future) We create XWikiPreferencesDocumentConfigurationSource,
SpacePreferencesDocumentConfigurationSource,
UserPreferencesDocumentConfigurationSource components
* Create a DefaultConfigurationSource component (hint = "default")
which has @Requirement("xwikiproperties") (and other sources later
on). It's a composite ConfigurationSource which calls the various
internal sources in the right order.
In term of usage here's what you'd write. For example for
DefaultRenderingConfiguration:
@Component
public class DefaultRendernigConfiguration implements
RenderingConfiguration
{
@Requirement
ConfigurationSource source;
private static final String PREFIX = "rendering.";
private static final String DEFAULT_LINK_LABEL_FORMAT = "%p";
public String getLinkLabelFormat()
{
return (String) this.source.getProperty(PREFIX +
"linkLabelFormat", DEFAULT_LINK_LABEL_FORMAT);
}
}
WDYT?
Thanks
-Vincent
Hello!
For the XOO project, I would need a conversion module which has two
components:
1. converter from the swriter html in pure html.
2. bidirectional converter wiki syntax - html.
Is this already done in the Office Importer project? If yes, I would be
grateful if you tell me where can I find this components.
Best regards,
Cristina Scheau
Does this mean our blog application doesn't work for non admins in XE
1.9?
If so it's a big problem that may require releasing 1.9.1 sooner than
we wanted IMO and do a 1.9.2.
WDYT?
Thanks
-Vincent
On Jun 17, 2009, at 3:20 PM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2009-06-17 15:20:27 +0200 (Wed, 17 Jun 2009)
> New Revision: 21328
>
> Modified:
> platform/xwiki-applications/trunk/blog/src/main/resources/Blog/
> Publisher.xml
> Log:
> XABLOG-49: Publishing blog posts does not work for non-admin users
> Fixed.
> Patch from Marta Girdea applied without changes.
>
> Modified: platform/xwiki-applications/trunk/blog/src/main/resources/
> Blog/Publisher.xml
> ===================================================================
> --- platform/xwiki-applications/trunk/blog/src/main/resources/Blog/
> Publisher.xml 2009-06-17 13:17:12 UTC (rev 21327)
> +++ platform/xwiki-applications/trunk/blog/src/main/resources/Blog/
> Publisher.xml 2009-06-17 13:20:27 UTC (rev 21328)
> @@ -30,7 +30,7 @@
> #end
> #set($entryName = "$!{request.entryName}")
> #if($entryName != '')
> - #if($xwiki.hasAccessLevel('edit', $context.user,
> $entryDoc.fullName))
> + #if($xwiki.hasAccessLevel('edit', $context.user, $entryName))
> #set($entryDoc = $xwiki.getDocument($entryName))
> #if ($entryDoc)
> #getEntryObject($entryDoc $entryObj)
Hello,
I tried using the URL path based wiki access as described in Manager Admin
Guide:
http://localhost:8080/xwiki/wiki/mydomain.com/view/Main/WebHome
It works perfectly but then I click on the "Edit" menu for any content from
such an URL.
Finally I try to click on a bottom button "Cancel", "Preview" etc...
It redirects me to :
http://127.0.0.1:8080/xwiki/bin/login/XWiki/XWikiLogin?srid=
So apparently with URL based notation, the form action is badly managed and
redirect to 127.0.0.1 and then to the login as I'm not logger on
127.0.0.1...
Do you know this issue?
Pascal
Hello GSoC students,
Time flies fast when you're having fun: only 3 weeks left until the
midterm evaluation. Don't forget that, by July 6th, you should all have
a project with at least 30% of the functionalities proposed in your
application, which will help us estimate whether you will be able to
finish your work according to the plan or not. Also, don't forget about
the (at least) weekly commits requirement, very important for getting
proper feedback, and about updating the wiki when you have news.
Note that we believe some of the projects are not really advancing as
expected, but it's probably not too late to catch up. Please communicate
with one of the mentors in case you get stuck.
Hoping to see some nice code committed this week,
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi,
I'd like to propose that we release a XE 1.9.1 on the 29th of June.
It'll contain bug fixes.
We currently have the following planned/done for core:
http://jira.xwiki.org/jira/browse/XWIKI/fixforversion/11150
Note that this is one week after the 2.0M1 planned release.
Here's my +1
Thanks
-Vincent
Hi Richard,
On Jun 16, 2009, at 9:31 AM, goldring, richard wrote:
> Hi,
>
> Maybe not in the next build, but:
>
> * more wysiwyg page layout tools (instead of hand coding css) would
> be good
> to enable users to rapidly and quickly knock up good looking pages,
I think this could be solved with the new 2.0 macros we're planning to
add:
- http://jira.xwiki.org/jira/browse/XWIKI-2965
- http://jira.xwiki.org/jira/browse/XWIKI-2963
- http://jira.xwiki.org/jira/browse/XWIKI-2966
- http://jira.xwiki.org/jira/browse/XWIKI-1689
WDYT?
> * also better table creating/editing (resizing, etc) and formatting
> (grid
> lines hidden/shown) would also be good.
ok
>
> * facility to email in content (text, images, rich text, word/open
> docs,
> etc) to automatically create wiki pages would be good (think can do in
> Confluence?)
Yes that would be handy. Actually I thought that we had done this at
some point but maybe it was only done on some specific instance and
not in the core.
> * some sort of automated work flow facility
This would need to be discussed more since this is too generic and the
needs might be various. Right now there are 2 solutions for simple
workflows:
- use spaces with permissions and some velocity to move pages from one
space to another
- add a Status object to pages and use HQL (or XWQL) to perform
queries based on the status
> * some sort of dashboard/home page mashups for users to provide user
> customised access to wiki content
You mean ability to insert widgets? Meaning that it's the user that
chooses the widgets he'd like to see.
Something like http://incubator.myxwiki.org/xwiki/bin/view/Gadgets/WebHome
maybe?
Now you mention "wiki content". Do you have ideas about content
widgets you'd like to see?
Thanks
-Vincent
> Regards,
>
> Richard
>
> -----Original Message-----
> From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org]On
> Behalf
> Of Guillaume Lerouge
> Sent: 15 June 2009 16:45
> To: XWiki Users; XWiki Developers
> Subject: [xwiki-users] [Proposal] XWiki Enterprise 2.0 Roadmap
>
>
> Hi XWiki Devs & Users,
> here's the current proposal for the XWiki Enterprise 2.0 roadmap.
> Please
> give us your feedback about it and tell us whether you think we missed
> anything important. Please note that this roadmap covers the next 3
> months
> of development work. Improvements not included here will be
> discussed at the
> beginning of the next roadmap (in September 2009).
>
> Shout if you think we forgot something ;-)
>
> The list of tasks is divided in 3 parts: tasks we have already
> planned to
> have people working on, tasks that we would like to complete during
> the
> course of the release but have nobody planning to work on yet and
> tasks that
> will have to be postponed until the next release cycle.
>
> *Tasks with people already planned to work on:*
>
> - Rendering (Thomas)
> - Fix bugs
> - Make sure the XWiki 2.0 syntax doesn't move any more once XE
> 2.0 is
> out
> - WYSIWYG editor (Marius, Anca)
> - Fix bugs
> - Implement search in the link insertion dialog box
> - Improve the macro insertion dialog box
> - CAPTCHA integration (Jérôme)
> - Clustering (Thomas)
> - Write a clustering component based on XWiki events
> - Activity Stream integration (JV)
> - Watchlist (JV)
> - Rewrite the watchlist feature based on the activity stream
> - Make the watchlist work in XEM
> - Macros (Asiri)
> - Write the velocity macro bridge
> - Write a number of velocity macros
> - UI Improvements (Caty)
> - Blog
> - User Profile
> - Architectural Improvements (Vincent)
>
> *Tasks with nobody planned to work on as of today:*
>
> - Migrate all XWiki Enterprise pages to use the XWiki 2.0 syntax
> (Collective effort?)
> - Rewrite XWiki's Lucene Search backend (Sergiu?)
> - Improve XWiki's default skin (Laurent?)
>
> *Tasks that will have to be postponed to the next release cycle:*
>
> - Application Manager
> - Document Type Manager
> - Invitation Manager
>
> The current roadmap dates are the following:
>
> - XE 2.0 M1: June 22
> - XE 2.0 M2: July 13
> - XE 2.0 M3: August 3
> - XE 2.0 RC: August 17
> - XE 2.0: August 31
>
> Thanks in advance for your feedback.
>
> Guillaume, on behalf of the XWiki Development Team
Hello,
I wonder whether this is a error in my servers configurations or this is a
bug...
I have an XWiki server running behind an Apache server and the link between
them is performed using the simple mod_proxy with some pass such as:
ProxyPass /xwiki/ http://localhost:8080/xwiki/
It works perfectly except when I logout...
I get redirected to an URL looking like:
http://localhost:8080/xwikihttp://mydomain/xwiki/bin/login/XWiki/XWikiLogin…
Do you have an idea of the reason of this behavior?
regards
Pascal
Hi,
Since I've now introduced events for XWiki App start/stop and since
listeners to those events can have the Container injected in them, do
we still need the notion of ApplicationContextInitializer?
Thanks
-Vincent