Hello friends,
Beside yesterday's addition, these have also been addressed. I apologize if
you checked yesterday and the addition was not on github/live instance, I
uploaded the unchanged folder.
- Lots of sections in Administration are missing the styles + some portion
> of settings are displayed after the administration menu ends (Chrome) (you
> need to scroll in order to see all the options, see Administration ->
> Applications -> WYSIWYG Editor settings )
- .xform style for .xHint are gone (you can observe this when creating
> pages/spaces)
I just uploaded some stylings that makes this more eye pleasing and
responsive.
- The page -> Share by email feature is style-less.
Styled this as well
Thank you,
Jonathan Solichin
Hi Developers,
With the help of Andrei (from the XWiki SAS support team), we have
worked on a prototype to provide a reference documentation for XWiki
scripting development.
We have found that new XWiki developers have difficulties getting
around everything that's available in XWiki and struggle a bit to find
the appropriate documentation.
Providing a reference documentation would go a long way to help the
developers getting up to speed faster. This is the objective of this
prototype.
You'll find the design page here:
http://dev.xwiki.org/xwiki/bin/view/Design/DeveloperReferenceDocumentation
A first prototype is available here:
http://incubator.myxwiki.org/xwiki/bin/view/ScriptingReferenceDocumentation…
At this point it only provides documentation for the latest version
(4.1.x), but it's already quite good as we have nothing really good
currently.
The first step would be to find a home on xwiki.org for this documentation.
It could be:
http://dev.xwiki.org/xwiki/bin/view/ScriptingReferenceDocumentation/
We also need a space to store all the builds of the full javadoc of
the XWiki platform for each version (I don't think using ZipExplorer
is a good idea given the size of the zip of the javadoc).
I suggest making them available through Apache at:
http://dev.xwiki.org/docs/${version}
If that's ok I can proceed to publish the prototype on dev.xwiki.org
and continue on the plan listed on the design wiki.
Any comments and ideas are of course welcome.
Ludovic
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
How can you use the standard XWikiXMLRPCClient to add pages or spaces to a particular wiki, when you are running the XWiki Enterprise Manager application?
I have installed everything, and I've made 2 new wikis.
When I log in as localhost:8080/xwiki/xmlrpc/confluence, I can add a space or page, but I can't specify which wiki to use!
The url localhost:8080/xwiki/wiki/NEW_WIKI/xmlrpc/confluence doesn't hit the xml rpc servlet filter. It initializes my context to the XWiki that is the main one, not a sub-wiki.
String url = "http://localhost:8080/xwiki/xmlrpc/confluence";
XWikiXmlRpcClient rpc = new XWikiXmlRpcClient( url);
rpc.login( user, pass);
rpc.storePage(someNewPage);
Thanks!
Dan
________________________________
This communication (including all attachments) is intended solely for
the use of the person(s) to whom it is addressed and should be treated
as a confidential AAA communication. If you are not the intended
recipient, any use, distribution, printing, or copying of this email is
strictly prohibited. If you received this email in error, please
immediately delete it from your system and notify the originator. Your
cooperation is appreciated.
Dear XWiki Community,
I have implemented the Advanced Search Features and Admin Module
for Solr Search Component.
The features include:
*Querying over:*
1. Plain strings ( can filtered based on space and language )
2. Objects [ object:XWiki.XWikiUsers ]
3. Properties [ XWiki.XWikiUsers.first_name : Sa* ]
4. Attachments [ filename:gsoc.pdf ]
5. Facets [ Space, Creator, Author, Creation Date, Modification Date,
Language ...]
6. Advanced search using document fields like title, name, comments,
space, language etc..
7. Multilingual Support
*Admin Gui:*
1. Index based on the wiki and the available spaces.
2. All the statistics
- Indexing stats
- Solr details, versions
- Solr configuration files and their sizes.
- Component details.
3. Indexing page.
- Details of indexing process in progress.
For more detailed information for Advanced search refer to the link below:
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Solr+Feature+Page
The detailed information about the admin module, Progress of the project,
API and the recent code is given in the progress page:
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SOLRsearchcomponent
Running instance of the amazon ec2 server:
http://ec2-50-19-181-163.compute-1.amazonaws.com:8080/xwiki/bin/admin/XWiki…http://ec2-50-19-181-163.compute-1.amazonaws.com:8080/xwiki/bin/view/Search…
--
Thanks,
Savitha
Hi devs,
Following upon an issue with migration encountered by Jeremie Bousquet, I
felt on an unexpected issue that I do not really know how to fix.
When you made a copy of a document containing a custom mapped class, a new
custom mapped class is created by the exact copy of the original document
class definition, but the custom mapping for this copied class is probably
incorrect or not available.
For exemple, if you made a copy of XWiki.XWikiPreferences, you get a new
class that has an internal mapping, but since the .xbm is unchanged, there
is probably no chance that the newly defined class has a mapped entity in
the hibernate mapping. This is precisely the cause of the issue I have
encounter with Jeremie, since the migration tried to migrate IDs of that
new class, which was unusable. Initially, I had an NPE that I have
transformed into an exception now, since I see this as a corruption
somewhere in the store.
The issue with a dynamically custom mapped class could even be worse, since
both class will have the same mapping.
So my question is more generally about how we handle copy of custom mapped
classes ? now and in the future ?
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
Hi,
In the development of Cassandra attachments, I found I want to load an attachment one chunk at a time and
write that chunk to a provided OutputStream, this is how I envision next generation Hibernate attachments working too.
I would like to add to XWikiAttachmentContent:
public OutputStream addContent();
which returns an OutputStream that allows writing the attachment content and upon close,
sets the attachment content as dirty and resets the size field.
WDYT?
Caleb
xwiki activity stream is very very slow
My 4.1.3 instance performance is not acceptable.
It takes me more than 10 seconds to display the activity stream.
Is there a simple workaround to remove 'activity stream' from user profile view?
I have already remove 'activity stream' from WebHome.
✉ Kirby Zhou
Hello devs,
I want to cast a vote regarding the following proposal:
Remove the section about manual testing and the link to the MTR's from
M1, M2 and RC1 Release Notes, since we test against MTR only after we
release RC1.
This means that we will have a MTR only for final releases, which will
be linked from the RN page of the final version.
After releasing each M1, M2 and RC1, only the newly added features are tested.
The rationale behind this is that ATM we point a link to a MTR (for
every minor release) but the MTR will be empty ("Not Tested"), so this
renders it useless for minor releases.
Waiting for your votes/opinions
Regards,
Sorin B.
Hi devs,
One of the main goals of 4.2 release was to be able to upgrade an
XWiki farm in a few minutes. Thomas has started working on this and I
need to improve the UI which is currently very minimal. We are pretty
late overall and one way to still have this in 4.2 is to postpone the
final release by adding a third milestone.
The current planning is:
* 4.2M2: 6 Aug 2012 (Today!)
* 4.2RC1: 20 Aug 2012
* 4.2Final: 27 Aug 2012
With a third milestone we could have this:
* 4.2M2: 6 Aug 2012 (Today!)
* 4.2M3: 27 Aug 2012
* 4.2RC1: 10 Sep 2012
* 4.2Final: 17 Sep 2012
However, doing this means we're going to miss the unofficial "1 cycle
per year rule" (we were already over 1 year at the current rate but
it's going to be worse with this) which means we would need from now
on to have shorter release cycle for the 4.x cycle:
* 4.3: October (2 months)
* 4.4: December (1 month)
* 4.5: January (1 month)
In any case the 4.4 and 4.5 release are supposed to be cycle
stabilization releases so it's not a bad thing.
We just need to agree we're not going to put any more big stuff in the
4.x cycle. One thing we would still need to put in is a new skin which
must go in 4.3 (would be too late afterwards).
I'm +1.
Thanks,
Marius
P.S.: This is actually Vincent's proposal, but I'm sending the vote
myself because he's on holiday.