Hi devs,
I'd like to propose 2 small changes that should make a huge difference for our users.
1) Introduce the notion of technical spaces
The idea is that in WebPreferences for a space we should have a boolean property mentioning if the space is a technical space or not.
This will allow to:
* Remove the blacklistedspaces variable
* List only non technical spaces for simple users
2) Introduce the notion of Application spaces
The idea is that in WebPreferences for a space we should have a boolean property mentioning if the space is an application space or not.
This will allow to:
* Replace the Quick Links Panel with an Applications Panel listing all spaces that are application spaces
* Only list Content spaces in the Spaces Gadget in the Dashboard
* Add the ability for extensions to declare new applications that automatically appear in the Applications Panel
I'd also like to suggest adding a global admin preferences to quickly select all spaces that are application and/or technical spaces (imagine a list of all spaces with 2 checkboxes for each space listed). This makes it very easy for the admin to reconfigure what are application spaces (thus showing in the app panel) and what spaces should be hidden for simple users. Of course modifying these would modify the WebPreferences of the said spaces.
In addition to make this autodiscoverable I'd suggest that for admins the Application Panel should have a link to this admin feature. Something like "Configure Applications...".
WDYT?
Thanks
-Vincent
PS: I'm very excited about these 2 ideas since they're simple and IMO will make XE much easier to use and understand for people starting to use it.
Hi,
Since xwiki isn't handling json POST request I've modified all my
source code to work with xml using simple-xml library(Andriod friendly
library).
Earlier I used json deserilizer as gson. I've created separate module
for gson as the xwiki data model. Now I've created another module for
simple-xml.
Should I remove gson module and replace it with simple-xml module? or
keep both modules. (gson module is no longer used for my project).
*New xwiki-android-component was developed for adding and viewing comments.
sources aren't pushed to repo yet since above module decision.
This week plan
Following  components will be developed this week.
* View/Upload page attachments. - Viewing is limited to Android native
viewers(Image Viewer, Video Player, Web Browser for text etc.). Native
file selectors are used for selecting files to upload.
* Add search component
Best Regards,
Chamika Weerasinghe
Hi devs,
I'd like to propose to create a twitter account for xwiki.org. The idea at first is to use it to announce new releases as part of the release process.
More specifically to tweet a link to the blog post we write on xwiki.org at each release.
Here's my +1 (I'll do it if we agree)
Thanks
-Vincent
Een groot Europees bedrijf is op zoek naar de kandidaten voor
beschikbare vacatures.
U zult zonder geldinvesteringen en met minimaal tijdsverlies het geld
kunnen verdienen.
Wij zullen een opleiding voor u geven; zelfs tijdens de
opleidingsperiode zult u al beginnen het geld te verdienen.
Deelname aan de opleiding zal niet voor je hoofdactiviteiten lastig
vallen.
Wanneer U gennteresseerd bent - stuur uw resum op ons e-mail:
job(a)sprytex-it.org
The XWiki development team is proud to announce the release of XWiki
Enterprise 3.0.1.
This is the first (and probably last) bugfix release for the 3.0 series,
with 37 issues closed on top of 3.0.
Backported from the 3.1 branch, two new features found their way into
this release: the possibility to export a wiki document into an office
format using a running OpenOffice/LibreOffice installation, and the new
UI for customizing the PDF export. More details in the full release
notes, at
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris…
Since this is a bugfix release on an older branch, the Download page
doesn't list the new binaries, but you can download them directly from
the OW2 Forge download page:
http://forge.ow2.org/project/showfiles.php?group_id=170
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi All,
I have an issue with login, creating user, creating space and adding user
to group in xwiki.
We are using our own sso and implemented in xwiki. its working fine.
Now i want to create user and add the user to group through xml rpc client.
i m using a sample code.. before that i want to login as admin. when i try
to login as admin in my remote machine it throws this exception. I
implemented this xwiki in jboss 4.2.2GA server. The main thing i noticed is
the exception coming in this line mainly * "rpc.login(user, pass);"*
import java.net.MalformedURLException;
import org.apache.xmlrpc.XmlRpcException;
import org.xwiki.xmlrpc.XWikiXmlRpcClient;
public class XmlRpcLogin {
public static void main(String[] args) throws MalformedURLException{
//URL of the xwiki instance
String url="http://testisp.css.com:8081/xwiki/xmlrpc/confluence";
//Replace user & pass with desired xwiki username & password
String user="Admin";
String pass="admin";
//Perform Login & Authentication using above url address
try{
XWikiXmlRpcClient rpc = new XWikiXmlRpcClient(url);
rpc.login(user, pass);
}
catch(XmlRpcException e){
System.out.println("invalid username/password was specified or
communication problem");
}
}
}
Exception :
17:55:28,313 ERROR [STDERR] org.apache.xmlrpc.client.XmlRpcClientException:
Fail
ed to parse servers response: Expected methodResponse element, got
{http://www.w
3.org/1999/xhtml}html
I really not aware why this happening. i hv all jars and things properly
placed n same code worked well before 1 year. now its causing this problem.
Any help greatly appreciated.
Thanks in advance.
Regards,
Nithya.
--
View this message in context: http://xwiki.475771.n2.nabble.com/Exception-while-login-creating-user-addin…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
I see you have left comments here and in jira and neither of them seem to be there anymore.
My reason for placing it in oldcore is the same as my reason for not using ConfigurationSource.
The main store is chosen from a key in the xwiki.cfg file, if there's a ConfigurationSource for xwiki.cfg then I would like to know about it.
I could have proposed moving the main store key to xwiki.properties but I made a guess that a proposal like that wouldn't fly.
If a user ever does switch to a different store, telling him that he needs to change two configuration keys in two different files so that developers don't go in debt would not make sense to him.
Caleb
On 07/31/2011 02:45 AM, vmassol wrote:
> I don't like the way you've fixed it too much (you've introduced some hacks) since using Initializable is the standard way of initializing components. The problem here can be fixed easily by not using the XWikiContext which in any case shouldn't be used. Instead configuration should come from a Configuration Source.
>
> Also you seem to be injecting the query executor but in init() you're looking it up again.
>
> Could you explain the need for this class and why it's located in the oldcore rather than being in the query manager's module?
>
> Thanks!
>
Just fyi we received several emails about build failing for rendering.
There were 2 issues:
1) the jenkins agent jar on the machines was not in sync with the jenkins version
2) Sergiu made a mistake during the release. He changed the java version to 1.5 (was 1.6). This makes the build fail since we require 1.6....
I personally don't like that we're doing releases from the agent machines, especially using the same user.... We should improve this.
Thanks
-Vincent
Hi Team,
I am not able to create virtual xwiki through the XwikiManagerPluginAPI. I
have developed just sample restful web service. Below is the code which I am
using to create virtual xwiki :-
@Component("org.sisgma.xwiki.rest.HelloWorldResource")
@Path("/hello/")
public class HelloWorldResource extends XWikiResource {
public HelloWorldResource(){
}
@GET
public String get(@DefaultValue("world") String myresourcename) throws
XWikiException, QueryException {
XWikiContext ctx = Utils.getXWikiContext(componentManager);
try {
WikiManagerPluginApi aoi =
(WikiManagerPluginApi)ctx.getWiki().getPluginApi(WikiManagerPlugin.PLUGIN_NAME,
ctx);
ctx.setDoc(new XWikiDocument(new DocumentReference("jaspreet", "space",
"page")));
System.out.println("_____________********* deleting xwiki");
aoi.deleteWiki("neenu", true);
aoi.deleteWiki("neenu1", true);
aoi.deleteWiki("karam", true);
System.out.println("_____________********* deleted xwikies");
System.out.println("_____________********* Creating new xwiki");
aoi.createNewWiki("jaspreet", "templatexe", null,aoi.createWikiDocument(),
true);
} catch (XWikiException e) {
e.printStackTrace();
}
System.out.println("_____________********* " +ctx);
System.out.println("_____________"+ctx);
return "Hello " + myresourcename;
}
}
Above code is not working. Virtual xwiki is not being created using the
API.
It is very urgent. Please help.
Thanks
Karamjit.