xwiki-devs

xwiki-devs@xwiki.org

9399 discussions

by Guillaume Fenollar

Hello there, I just merged branch 4.0 of admin tools application here : https://github.com/xwiki-contrib/application-admintools Now that I built the new xar package, I would like to release it in maven to update the Extension Page<http://extensions.xwiki.org/xwiki/bin/view/Extension/Admin+Tools+Application>, so I need a Nexus account. Can anybody help me with this? For those interested, 4.0 is a complete rewrite of Admin Tools, to match version 2.0 or 2.1 of wiki syntax. See release notes just here: * All scripts have been rewriten using xwiki 2.1 (mostly) or 2.0 syntax. > * SQLTools developed by Guillaume Delhumeau has been implemented to > standardize SQL queries inside Admin Tools. With it, we now can Run Query, > Show Large History, Show Spammed Pages... We plan to include PostgreSQL > scripts very soon. > * Used Space page has been rewritten completely. It summarizes now disk > space used by all subwikis of the farm, and show attachments related > database if filesystem storage mode is not used. > * Configuration Check page has been rewritten, with some recommendations > at the bottom depending on the configuration. At the moment, we put > recommendations about memory, cache, encoding and cookies encryption keys. > * User Rights Check has been replaced by Show Rights, which simply shows > every right set on wiki / spaces / pages. It may be useful when we put > temporary rights to pages (which can lead to security leaks) > * Show Logs script have been included with a UI which permits to choose > number of loglines to output, directly in the wiki page. > * Database Encoding Check nows works with subwikis. Indexes Check has > still to be implemented with full list of Indexes. > * Export Tools now have Large Export/Import scripts > * DatabaseToFilesystem porter script has been added (it seems not > compatible with 5.x at the moment though). > * Requests Status page has been dropped And about the code or the commits, please be kind, I'm not a developer at all ;-) Thanks, Guillaume Fenollar

12 years, 1 month

[xwiki-devs] [QA] Feedback for 5.2M1

by Manuel Smeria

Hello devs, XWiki 5.2M1 is scheduled to be released the next Monday. I'll go through the list of bugs fixed for it and also take a look at the new features. Besides these, do you want something else tested as well ? Thank you, Manuel

12 years, 1 month

[xwiki-devs] Retrieving xwikilistitems

by Stephen Martin

I want to modify the GlobalBlogRss feed to add a couple of different filters and have been able to do so successfully up to the final point. I can't seem to get the syntax correct for limiting the results to a specific xwikilistitem. The query string is passed to xwiki.feed.getBlogFeedOutput. The query string that I am using is: , DBStringListProperty as categories join categories.list as category, BaseObject obj, IntegerProperty isPublished, IntegerProperty hidden, DateProperty publishDate where doc.fullName <> 'Blog.BlogPostTemplate' and obj.name = doc.fullName and obj.className = 'Blog.BlogPostClass' and publishDate.id.id = obj.id and publishDate.id.name = 'publishDate' and isPublished.id.id = obj.id and isPublished.id.name = 'published' and hidden.id.id = obj.id and hidden.id.name = 'hidden' and (doc.creator = 'XWiki.stevem' or (isPublished.value = 1 and hidden.value = 0)) and obj.id = categories.id.id and categories.id.name='category' I would like to add the statement [xwikilistitem].value='Blog.Production' but unclear of proper way to do so. Is another JOIN required? Any pointers to reference material would be welcome as well. Thanks, Steve Martin IT Support Jones Metal (740) 623-5102

12 years, 1 month

Re: [xwiki-devs] [xwiki-notifications] Problems with XWiki 3.1

by Denis Gervalle

Hi Federico, Release 4.1.1 is not a really good choice for migrating. There are still a couple of migration issues in that release. I advise you to migrate to 4.5.4 to be really safe with migration. If you continue to have migration issue with that version, please provide the container logs to diagnose the issue. Be careful to properly merge your xwiki.cfg file with the distributed one, and to let migrations run on all databases. Regards, On Tue, Aug 6, 2013 at 3:23 PM, Federico Moglia < federico.moglia(a)workingteams.com> wrote: > Hi! > I'm Federico and I'm working with XWiki Enterprise 3.1. I have some > problems in the app, for example, when I tried to assign rights to any > user. Attach screen of error and a txt file with the stack trace of > exception. > > For try to solve this, I've imported the xwiki database to the version > 4.1.1. The restore in PostgreSQL didn't give any errors. But when I tried > to access, the application shows me this exception in the browser: > Exception while switching to database xwiki Wrapped Exception: Database > xwiki needs migration(s), it could not be safely used! (Attach file with > the full stack trace) I am using PostgreSQL 9.1. In the file xwiki.cfg, I > have configured the migration with the next line: xwiki.store.migration=1. > So, I don't understand why fails. Maybe my database is corrupted and this > is the cause of the problem. But I don't know how I solve this. > > When I tried to import the xwiki in .xar format, the log in catalina.out > shows this: > 2013-07-26 16:17:43,752 > http://localhost:9001/xwiki/bin/get/XWiki/XWikiPreferences?xpage=packageinf… WARN > c.x.x.p.p.Package - Failed to parse document [Disney/GlosarioTecnico.xml] > from XML during import, thus it will not be installed. The error was: Error > number 2002 in 2: Error parsing xml > Wrapped Exception: Truncated ZIP file Nested exception: Truncated ZIP file > > The information that I've found in Internet was not very useful to resolve > the problem, for this reason, I decided to write you. I hope that you can > help me with this. > > Thanks! > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications > > -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

12 years, 1 month

Re: [xwiki-devs] [xwiki-notifications] Problems with XWiki 3.1

by Sergiu Dumitriu

Hi Federico, The root of the problem seems to be a corrupted database. Changing rights fails to commit the changes to the database. Trying to upgrade fails to execute some migrations, mandatory database changes needed for the new version. You should look at the logs that occur while starting the new version, it will say what migration failed to execute and why. On 08/06/2013 09:23 AM, Federico Moglia wrote: > Hi! > I'm Federico and I'm working with XWiki Enterprise 3.1. I have some > problems in the app, for example, when I tried to assign rights to any > user. Attach screen of error and a txt file with the stack trace of > exception. > > For try to solve this, I've imported the xwiki database to the version > 4.1.1. The restore in PostgreSQL didn't give any errors. But when I > tried to access, the application shows me this exception in the browser: > Exception while switching to database xwiki Wrapped Exception: Database > xwiki needs migration(s), it could not be safely used! (Attach file with > the full stack trace) I am using PostgreSQL 9.1. In the file xwiki.cfg, > I have configured the migration with the next > line: xwiki.store.migration=1. So, I don't understand why fails. Maybe > my database is corrupted and this is the cause of the problem. But I > don't know how I solve this. > > When I tried to import the xwiki in .xar format, the log in catalina.out > shows this: > 2013-07-26 > 16:17:43,752 http://localhost:9001/xwiki/bin/get/XWiki/XWikiPreferences?xpage=packageinf… WARN > c.x.x.p.p.Package - Failed to parse document > [Disney/GlosarioTecnico.xml] from XML during import, thus it will not be > installed. The error was: Error number 2002 in 2: Error parsing xml > Wrapped Exception: Truncated ZIP file Nested exception: Truncated ZIP file > > The information that I've found in Internet was not very useful to > resolve the problem, for this reason, I decided to write you. I hope > that you can help me with this. > > Thanks! -- Sergiu Dumitriu http://purl.org/net/sergiu

12 years, 1 month

[xwiki-devs] Considerations on application development in multi-wiki mode

by Jeremie BOUSQUET

Hello, This is no particular issue I'm addressing here, just wanted to get possibly some feedbacks on the app I'm developing, considering virtual mode. Also not from a technical point of view (though it's impacting of course), more on best way to make use of XWiki. It's for the Mail Archive :) Currently I provide components and 1 UI, to administrate, operate (email loading) and navigate (livetables, stats) a Mail Archive. Focusing on UI, the whole app is inside xwiki-contrib-mailarchive-ui. The use-case I would like to allow/improve, is of someone wanting to create "isolate" different mail archives / mailing-lists in different subwikis. The first thing I did (and that works), is duplicate the whole app in each sub-wiki (after fixing some issues caused by being in a sub-wiki). My next move would be to separate the administration: xwiki-contrib-mailarchive-admin-ui xwiki-contrib-mailarchive-ui The idea would be to install admin/operate part once for all, and install the "navigation" app in each needed sub-wiki. To allow that, "navigation" xar cannot depend on "admin" (or it would install "admin" everywhere), and "admin" could depend on "navigation", for the unique wiki use-case. Means that it's the admin that should be installed in mono-wiki mode, and this is a bit weird I think for users. Or I could say that both should be installed, up to you to decide where you install what (but logically you install "admin" in main wiki and "navigation" in main or sub- wiki(s)). Of course the concept is that the "administration" UI takes into account the possibility of wanting to use multiple sub-wikis, and allows the user defining what is the destination of created mails pages for each mailing-list (ie, the main wiki, or a specific sub-wiki). Then there's the case of all the XClass pages. Because they are needed for the "navigation" (along with Sheets and so on), but to restrict number of pages created, it would seem good to create those once for all in the main wiki, and just "use" them from the sub-wikis mail archive pages (home, topic, mail, ...). Doing that, the "navigation" app would be very minimal (not much more than a home page in fact). To simplify I could add them to the "admin" app, but what I do not like is that logically they are not part of the admin. In fact they could be seen as a third UI, a technical one, dedicated to "wiki-storage-mapping" (sorry for that name, hope you get the point, if you're still reading this). Logically both "admin" and "navigation" should have a dependency on "storage", but to follow primary optimization purpose only "admin" should mark this dependency. So: "admin" --> "navigation" "admin" --> "storage" WDYT ? (apart from, "this mail is way too long"). I'm asking, because I'm not sure I'm taking it the right way. I'm also not sure, if following this I'm not going to create some coding hell :) (another topic for me would be to plug my admin part into the xwiki admin UI, but I'm also afraid of the amount of work...) Thanks, Jeremie

12 years, 1 month

[xwiki-devs] [VOTE] Remove PR check for query languages other than XWQL and HQL

by Eduard Moraru

Hi devs, It seems that our SecureQueryManager [1] is preventing the execution of queries other than XWQL and HQL in the absence of PR. However, this is not at all a friendly policy when it comes to extensions. An example of where this is causing problems is Solr queries, where only users (well, document authors) with PR can execute them. As the subject says, I suggest removing this restriction and leaving rights check to be performed in each QueryExecutor's execute() method. The associated Jira issue is XWIKI-9386 [2] Here's my +1. Thanks, Eduard ---------- [1] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi… [2] http://jira.xwiki.org/browse/XWIKI-9386

12 years, 1 month

[xwiki-devs] Bug with global user profile in sub wiki and support for empty servlet path

by Christian Meunier

Hi All, I sent 2 emails to the users list without much success and I am hoping that I might find a more suitable audience for my somewhat technical issues with the devs. 1) Global users in sub wiki. In the system I am trying to setup, all the users are created using a custom auth module in the main wiki (Global users), so there will be no local users. The issue is that on a sub wiki, when you click on a user to bring up its profile, you end up on a document not found. From the auth module, the principal returned is prefixed with the 'XWiki.' so the system should be able to differentiate between local and global users and act accordingly. I checked that I could reproduce the issue even if i am not using any custom authentication. Should i log this as a bug in Jira ? 2) Empty servlet path support The second thing I am struggling with is shortening the urls. I am following this guide: > http://platform.xwiki.org/xwiki/bin/view/Main/ShortURLs But no matter what I try, I cannot make it work without the '/bin/ prefix. Please note that the xwiki is running under Jetty as the main context (mapped as '/') so the url I have is: server.com/WebHome which according to the short urls document should work. it appears that the issue comes from StandardXWikiURLFactory: -------------------- String type = extendedURL.getSegments().get(0); if (type.equals("bin") || type.equals(this.configuration.getWikiPathPrefix())) { xwikiURL = this.entityURLFactory.createURL(extendedURL, parameters); } else { throw new UnsupportedURLException(String.format("URL type [%s] are not yet supported!", type)); } ---------------- So basically for server.com/WebHome, what is happening is that type above equals to "WebHome" and so the condition obviously fails and throws the UnsupportedURLException. Given the above code, I am either forgetting something in the xwiki.cfg or it simply cannot work out of the box... If i were to provide my own custom XWikiUrlFactory, would it solve entirely the issue or some other parts of the system will nevertheless fails because they have the same assumption regarding the presence of the bin or the PathPrefix in the url ? Thanks in advance for your help ! -- Chris

12 years, 1 month

[xwiki-devs] [Reminder] BFD#30

by Marius Dumitru Florea

Hi everyone, Today is BFD 30. Our goal is still to have more bugs closed than created for the past 1300 days! http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 As of now we're 16 bugs behind! Let's close the gap! Here's the BFD#30 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=11609 Thanks Marius

12 years, 1 month

[xwiki-devs] [Proposal] Workspace as a Flavor

by Ecaterina Moraru (Valica)

Hi devs, So this is a proposal to have Workspaces as a Flavor and NOT integrated by default. IMO Workspace is a real nice use case and we should definitely promote it. This is how I envision the main homepage (Home) http://incubator.myxwiki.org/xwiki/bin/download/Improvements/WorkspaceHomep… and this is how the homepage of a workspace would look like http://incubator.myxwiki.org/xwiki/bin/download/Improvements/WorkspaceHomep… For more mockups please check the full proposal: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/WorkspaceHomepage The problem is that Workspace Flavor is a use case on it's own and IMO in this particular use case you will not want to have isolated wikis, and plus you will don't want to have lots of the features that are currently by default, so it's really obvious that the Workspace flavor is a specialization of XWiki and will not be anyone's cup of tee. For example, the other Flavors proposed are: - Public Website: you definitely don't need workspaces here - Documentation: same, no need - Application Development: this is intended for development, no need for workspaces See Flavors proposal http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Flavours So Workspaces Flavors is exactly the Groupware Flavor (just I proposed it with another name) http://incubator.myxwiki.org/xwiki/bin/view/Improvements/GroupwareFlavor What I think we should do in 5.2 is indeed have by default the ability to create multiple wikis (so XEM integration, bu without Workspaces). So: - Have 'Add - Wiki' only shown to admins (until we decide otherwise) http://incubator.myxwiki.org/xwiki/bin/download/Improvements/CreateWikiImpr… - Have main wiki homepage defined as 'Home' (using the icon and with a customizable title) - Have a consistent create step for wikis, spaces and pages (in just one step, since Members has sense only for Workspaces) http://incubator.myxwiki.org/xwiki/bin/download/Improvements/CreateWikiImpr… - Integrate Wiki Manager inside Administration (since it's information related to administrator and should not be public as it is now) We could improve the UI by using a livetable http://incubator.myxwiki.org/xwiki/bin/download/Improvements/CreateWikiImpr… All stated above is default functionality that doesn't break backwards compatibility and that is shared between all Flavors. Some base concepts related to Flavors: - Let's consider that what we currently have is a 'Default Flavor' (XE) - We could have a 'Base Flavor' in the future that will consist of 'Default Flavor' minus all the extensions that are not share between all flavors. It will contain just base features and the common denominator for all Flavors. Every time you want to create a new Flavor you could start from this Flavor. - Extra: for test purposes we could also have a 'Full Flavor' containing all the extensions supported by XWiki Development Team. This would be helpful to run the integration tests on it and see if there are possible problems when installing combinations of extensions. Also could serve as a demo flavor of what is possible in XWiki. - There will also be the 'Standard Flavors': Workspaces, Public Website, etc. (proposed and supported by XWiki Development Team) Having this is mind: - Flavors should have the ability to "remove" or alter some pages from the 'Base Flavor' (currently our 'Default Flavor'). For example the Workspace Flavor needs its custom main homepage that list the existing workspace (this doesn't make any sense to any other Flavor). Another example is removing 'Wiki Manager' from 'Default Flavor' and replace it with 'Workspaces Index' that is visible for all users. - Flavors could have their own skin (might need some changed .vm) + preferences (different layout, etc.). In the Workspace Flavor we will want to promote the creation of Workspaces and not Wikis (that is found in the Base Flavor). - Flavors need to integrate other Flavors. For example: 'Workspace Flavor' = 'Base Flavor' + extensions. Also we could have a 'Product Management Flavor' = 'Workspace Flavor' + custom applications installed like: Projects, Deliverables, Meetings, etc. So what we could also do in 5.2 (or 5.3) is: * Flavor definition (from a technical perspective), extensions collections, ability to integrate also pages in the list, etc. * Work separately on the 'Workspace Flavor' which could be our first proposed Flavor (besides the current 'Default Flavor' which is a version of Knowledge Base). This means improving the current 'Workspace Application' with the above proposed Homepages improvements. Let me know what you think, Caty

12 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs