Hello Devs,
Is it possible to render one page with two different class sheets.
For example, in a 3 page navigation,
-> We create an object of a class on the first page and add it to the second
page.
-> But, we do not display the Object properties on the second page, instead,
we add some more properties to that object on that page
->on the third page we want to display the object properties.
So, my question is can I just use the same page for the second and third
page (described above). That one page has the object added to it but will
display two different things based on the style sheet.
I tried doing this, but it did not replace the class sheet applied the first
time with the second one.
-> From Page 1 to Page 2, I used
$response.sendRedirect($newdoc.getURL("save",
"template=${etemplate}&parent=${eparent}&title=$etitle"))
where etemplate = Template 1
This adds
#includeForm("XWiki.ClassSheet1")
-> From Page 2 - Page2 (with a different template), I used,
$response.sendRedirect($newdoc.getURL("propupdate",
"template=${etemplate}&parent=${eparent}&title=$etitle"))
where etemplate = template 2
This does not replace #includeForm("XWiki.ClassSheet1") , but just adds //
to the wiki editor and the editor contents look like this:
//
#includeForm("XWiki.ClassSheet1")
I was expecting it to just overwrite it with
#includeForm("XWiki.ClassSheet2")
Q) Is there any way to remove the template and add a new one....any other
better way of achieving this.
Thanks a lot for all help
Hi,
I am working on an application that relies heavily on custom search to get
the data to client.
I have looked at the xwiki api and it seems that seerch method needs
programming rights.
Now every user would not have programming rights.
So could you please let me know how can I execute such search methods from
within my velocity code.
One way would be to use my custom search plugin to bypass the xwiki
programming rights.
I have also see the xwiki reference page for search queries and there are
some where no result is displayed, and this is probably because when we
access the page there is no access for guest user or logged in user to
execute those queries.
http://platform.xwiki.org/xwiki/bin/view/DevGuide/velocityHqlExamplesMacro
So again can't the search apis move out of programming rights?
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Using-search-apis-tp17315167p17315167.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
When I run jettyrun from platform web, I don't get the skins loaded.
What I see in the run is that it points to the sources of platform web
for it's web resources.
With this patch:
Index: pom.xml
===================================================================
--- pom.xml (revision 9842)
+++ pom.xml (working copy)
@@ -170,6 +170,7 @@
<configuration>
<contextPath>/xwiki</contextPath>
<classesDirectory>${project.build.directory}/${project.build.finalName}/WEB-INF</classesDirectory>
+
<webAppSourceDirectory>${project.build.directory}/${project.build.finalName}/</webAppSourceDirectory>
<scanIntervalSeconds>10</scanIntervalSeconds>
<connectors>
<connector
implementation="org.mortbay.jetty.nio.SelectChannelConnector">
It points to the result of the build in target, where the skins have
been unzipped.
I would commit this, but I'm wondering why this was not reported
already and if everybody has this problem ?
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hello all,
I have to migrate from xWiki Enterprise 1.2.1 to something newer because
of a known bug of my current release.
My idea is to switch to the 1.4.. can anyone tell me if i must install
the 1.3 before the switch to the 1.4?
Is there a "migration checklist" somewhere?
Thanks.
--
By MCM.
Hi,
Some comments I've discussed with JV about implementing
http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministration
I believe we should design it in the following manner:
* The Admin page is a generic empty shell
* An XWiki instance is made of applications (admin pages like users/
groups/configs are part of the admin application too). Examples: Blog,
Calendar, Panels, etc
* Each application should be able to contribute admin pages to
configure/administrate itself. These pages should automatically appear
in the left menu on the new admin page. Note that this will require
interface extensions so right now we would hardcode them in the menu.
* What it means is that the admin page should link to the admin pages
located in the applications providing them.
I know we're missing the interface extensions to make this work but
I'd like that our design for the new admin page works towards this
goal in mind.
WDYT?
Note: This email was prompted by Evelina asking if it was ok to attach
XARs to be imported in the XWiki.XWikiPeferences page. IMO it's not a
good thing to do. The XARs should be attached in the ImportExport
application pages (as it's done now). Now I have no idea how easy or
hard this is to implement since I haven't dived in the implementation.
Thanks
-Vincent
Just checked out and ran a `mvn install` got the following ...
<code>
[INFO] Compiling 22 source files to
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/target/classes
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[41,46]
type com.xpn.xwiki.plugin.PluginApi does not take parameters
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePlugin.java:[544,15]
incompatible types
found : com.xpn.xwiki.plugin.lucene.LucenePluginApi
required: com.xpn.xwiki.api.Api
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[68,12]
cannot find symbol
symbol : method hasAdminRights()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[69,53]
cannot find symbol
symbol : variable context
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[69,19]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[85,19]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[106,27]
cannot find symbol
symbol : variable context
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[105,19]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[167,31]
cannot find symbol
symbol : variable context
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[166,16]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[183,15]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[191,15]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[199,15]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[216,27]
cannot find symbol
symbol : variable context
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[215,19]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[263,16]
cannot find symbol
symbol : variable context
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[262,19]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[286,16]
cannot find symbol
symbol : variable context
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[285,19]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[345,31]
cannot find symbol
symbol : variable context
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[344,16]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[407,31]
cannot find symbol
symbol : variable context
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
/home/asiri/projects/xwiki/xwiki-dev/trunks/xwiki-platform-plugins/lucene/src/main/java/com/xpn/xwiki/plugin/lucene/LucenePluginApi.java:[406,16]
cannot find symbol
symbol : method getProtectedPlugin()
location: class com.xpn.xwiki.plugin.lucene.LucenePluginApi
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2 minutes 25 seconds
[INFO] Finished at: Sun May 18 08:50:39 LKT 2008
[INFO] Final Memory: 45M/142M
[INFO]
------------------------------------------------------------------------
</code>
Hello devs,
I'm trying to figure out a "clean" way of storing third-party applications
credentials in a XWiki user profile.
My use case is the following (and I believe such use cases will continue
to occur as we offer more web-services integration). We want XWiki
Workspaces users to be able to update their twitter status too when
posting an update on a workspace "workstream", just checking a box.
First time they would be asked for their twitter credentials, but for the
following ones, it be nice not to ask.
A possible way I want to propose is to encrypt the username/password
couple (for example, represented under their base-64 form since twitter
API requires basic authentication) through a cipher, using a secret key
based on a combination of the user XWiki password hash and a secret
parameter located in xwiki.cfg. This way, programming rights or physical
access to xwiki.cfg would be required to decrypt the login/passwd.
If the user changes his XWiki password, thus the hash, or if the secret
parameter value is changed, the user would be asked to enter is
credentials again (In fact, as soon as the service authentication fails).
WDYT ? Are there cleaner/more secured ways of doing this ?
Thanks for your inputs,
Jerome.
Hi developers,
I am a new comer to java and xwiki. I am trying to to download the xwiki
1.4 source
code and setup the xwiki build environment in Eclipse. Is there any
tutorial for that
or can any one help me with that? Any help will be highly appreciated.
Regards,
Viv