Hi (Sergiu),
I see you've committed Caty's pull requests. Thanks for that it's very nice! :)
One little detail: the name of the color theme that was bundled in XE 3.3
Right now it's "XE33Default". I think this is not correct since the colortheme application is not supposed to be linked to XE. We're actually moving it to platform.
So I'd rather call it something like "XWiki33Default" with a title of "XWiki 3.3 Default" instead.
WDYT?
Thanks
-Vincent
Hi All,
I created one page named as Release4 and when i try to search Release4 does
not show any results for this page but if i create another page with name
ReleaseFour and now search ReleaseFour , it shows the results. *Is it an
issue or i am missing some thing here?*
Hi All,
i have created a space on xwiki with the name MySpace. Now i want to create
one sub space under MySpace with name Releases. When i go MySpace and do
add space and give the name of my new sub space i.e Releases . It does
not add that space under MySpace but it adds as seperate space together.
Is it possible to create sub-space ?
Hi All,
I do the login with admin credentials in one internet explorer window. Now
i open one more seperate IE window and give my xwiki home url i.e
http://localhost:8888/myxwiki/ . I see in this second i am directly getting
logged in with admin credentials which is not correct. I should see login
screen on this second window here.
Then i did debugging and found out with both IE windows
xwikicontext.getRequest().getSession() returning the same session(
basically both sessions are having same session id). As per my
understanding session is specific to browser window . so both windows(or
request from diffent IE windows) should have different session attached to
them.
Not getting how come both request are having same session id.
Thanks
Hi devs and everyone,
Here's a proposal for the XE 3.4 roadmap.
The idea is to have a short release focused on stabilization and polishing exclusively. This is meant to be the first of 2 stabilization releases (with XE 3.5). Reminder: XE 3.5 is the last release of the 3.x cycle and after it's released we'll start the 4.x cycle.
Dates:
=====
3.4M1: 19 December
3.4RC1: 26 December
3.4Final: 5 January (not putting 2 january since it's just after new eve and people might be a bit tired and not in the mood of releasing ;))
Plan for 3.5:
3.5RC1: 23 January
3.5Final: 30 January
Must have:
=========
* Finish UI for extension manager - Sergiu
- more polishing (js, etc)
- support for XAR merges and conflicts
- whatever is missing (I'm not sure about its exact status - Sergiu, could you give us a precise status of what's missing?)
* Fix bugs and continue improving Extension Manager backend and the XWiki Repository application (XR) - Thomas
- Thomas, can you list important stuff to do here?
* Finish App with Minutes - Marius
- Polishing
- New auto title/page name feature
- Maris, can you list other things that we need to finish in 3.4?
* LDAP Admin UI - Jerome
Nice to have:
===========
Backend:
* LDAP group sync need to test group membership before adding user to group XWIKI-7063 Unassigned
* Page creation date should be the date of the installation XWIKI-7058 Unassigned
* Accessing a store that is not migrated to the lastest data version should not be allowed XWIKI-7006 Denis Gervalle
* Reduce the likelihood of having same (hibernate) document id for different documents XWIKI-6990 Denis Gervalle
* When using filesystem attachments with attachment versioning disabled, deleted attachments are duplicated on the hard disk. XWIKI-6951 CalebJamesDeLisle
* Deleted attachments duplication in recycle bin while File Storage is on XWIKI-6917 CalebJamesDeLisle
* Renaming a page should also rename the title of it XWIKI-6743 Unassigned
* Be able to rename a space from the UI XWIKI-6722 Unassigned
* Be able to delete a space from the UI XWIKI-6687 Marius Dumitru Florea
* Use a predefined Space Template like Dashboard, Livetable when creating a new space XWIKI-6684 Unassigned
* Problems displaying the correct attachment version when using a proxy XWIKI-6569 Unassigned
* Performance of blog category panel is still not enough XWIKI-6363 Unassigned
* Change stylesheet and javascript extension filename when a modification is done on those XWIKI-6073 Unassigned
* Auto-create Space.WebHome when creating a page in an underfined space XWIKI-5399 Unassigned
Front end:
* Add more/all configuration parameters in the wiki administration XWIKI-7066 Unassigned
* Unable to add users to a group on IE9 XWIKI-7061 Unassigned
* When editing a User Profile category, after saving the changes, preserve the category tab XWIKI-7059 Unassigned
* Strange behaviour when pressing back and forward on a page that has 2 WYSIWYG editors displayed XWIKI-7028 Marius Dumitru Florea
* Log-in automatically on registration XWIKI-6892 Unassigned
* Tree from document index does not expand on IE9 XWIKI-6752 Marius Dumitru Florea
* Have an auto-complete for the User and Group visibility inputs for the Message Stream XWIKI-6728 Unassigned
* Limit dragable width of textareas in FF4 and Chrome XWIKI-6304 Unassigned
* WebSearch should only display spaces with view right XWIKI-6227 Unassigned
* Auto-suggest doesn't work for global users XWIKI-6207 Unassigned
* New floating action menu hides titles in the content of the page when jumping to an anchor XWIKI-6018 Unassigned
* Activity Stream doesn't show Image Profile change XWIKI-5930 Unassigned
* Cannot filter using "/" on a Date column in the livetable XWIKI-5889 Unassigned
* Better placement of the documentation link XE-1031 Unassigned
* Cannot access the object editor for documents with XWikiRights objects on wikis with many users XE-1015 Unassigned
* New XWiki Syntax Guide XE-880 Unassigned
* Occasionally the livetable fails to load on index pages XE-844 Unassigned
* Add option to 'show more entries' on displaying the Activity Stream XE-748 Unassigned
Please review the items where your name is indicated to make sure you're planning to implement them!
Of course if there are some other items that you're planning to do, make sure to add them to the list.
WDYT?
Thanks
-Vincent
Hi devs,
As we have moved to GitHub, I've started coding an equivalent of the SVNApp
(http://extensions.xwiki.org/xwiki/bin/view/Extension/SVN+Application) for
GitHub, which should ease up commiting pages from XWiki to GitHub, and
because the GitHub SVN bridge is unfortunately not compatible with SVNKit.
The bad news is that it's not a GitApp which seems very difficult to do as
it relies on a local clone of the repository which is quite overkill when
in an XWiki.
The good news is that thanks to the GitHub API and a java wrapper from
Eclipse, it seems fully possible to have the same functionnality as the
SVNApp.
I've made some good progress, as I've been able to check a repository
against the Wiki AND I've been able to commit non existant files in an
existing repository.
The life proof is the commit of the GitHubApp itself which was done with
GitHubApp:
https://github.com/ldubost/application-githubapp/tree/master/src/main/resou…
It's still a prototype as there is a lot of work left. For now every file
is commited separately and I've not yet tested updating and other
complexities, especially as the GitHub api is not that easy to work with
(many times I had no errors but my updates were not showing up.
Ludovic
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi devs,
I'd like to move Selenium2 PO classes for platform in xwiki-platform. The rationale is that:
1) it belongs to platform
2) it allows us to write functional tests in platform
More precisely here's what I propose:
* Move current unit test fwk currently in xwiki-platform-test to xwiki-platform-test-unit
* Add a new xwiki-platform-test-functional module and move the PO objects + functional test classes in it FTM (in some future we'll move POs for a given module in that module but we're not quite there yet)
I'm starting to work on this in few minutes so please let me know ASAP what you think.
Thanks
-Vincent
Hi devs,
The default implementation of
DocumentAccessBridge#getDocument(DocumentReference) has been modified
a few months ago [1] to return the translated document. As a
consequence, currently there's no way to access the default
translation of a document from a component without depending on the
old core (i.e. without using XWiki.getDocument()). Thus I'm proposing
to add:
/**
* Retrieves the default translation of a document specified by its reference.
*
* @param documentReference a document reference
* @return the default translation of the specified document
* @throws Exception when the storage cannot be accessed
* @since 3.4M1
*/
DocumentModelBridge getDefaultDocument(DocumentReference
documentReference) throws Exception;
to DocumentAccessBridge. The default implementation will do exactly
what DocumentAccessBridge#getDocument(DocumentReference) was doing
before [1].
Note that the default translation of a document is important because
it is the only one that provides the document objects. So if you want
to access the objects of a document you have to do it through the
default translation.
Thanks,
Marius
[1] https://github.com/xwiki/xwiki-platform/commit/f1188a7be56600aa975d7ccc747a…
Hi devs,
I'd like to propose to write a Distribution Maven Plugin that would have the following features:
* Ability to generate XWiki config files.
* Ability to generate a full expanded XWiki Distribution. Here are the steps it will do (since I have a first working version I'm pasting what it currently does):
** Step 1: Expand Jetty resources into the package output directory.
** Step 2: Get the WAR dependencies and expand them in the package output directory.
** Step 3: Copy all JARs dependencies to the expanded WAR directory in WEB-INF/lib
** Step 4: Copy compiled classes in the WEB-INF/Classes directory. This allows the tests to provide custom code, for example to override existing components for the test purpose. As an example the link checker might want to override the HTTP Checker component so that checks are not done over the internet since the tests need to execute in a stable environment to prevent false positives.
** Step 5: Generate and copy config files.
** Step 6: Copy HSQLDB JDBC Driver
** Step 7: Unzip the Colibri Skin
** Step 8: Import specified XAR files into the database
* Ability to generate a full zipped XWiki Distribution
* Ability to import XARs
Use cases:
* Simplify the current build (XE, XEM, etc) by using this plugin
* Use it to generate custom packaging to write functional tests for platform modules
* Allow xwiki developers to easily generate custom distributions by handpicking platform modules + their own modules
As mentioned above I've worked on this and I'm going to commit a first working version real soon. My current goal is to write some functional tests for the linkchecker-ui module.
ATM I have added a new "package" mojo as part of the packager plugin but I'd like to create a new xwiki-platform-tool-distribution-plugin in the future and deprecate the current packager plugin.
Thanks
-Vincent