Hi,
Im trying to fix http://jira.xwiki.org/jira/browse/XWIKI-4274
Basically if you do $xwiki.getDocument("someDoc").getRenderedContent()
it'll get executed in the context of the current doc which I believe
is wrong especially since other signatures of getRenderedContent()
execute in the target document's context.
I have fixed this locally but found that admin.vm for example is
assuming that getRenderedContent() will get executed in the context of
the calling doc (i.e. XWiki.Import when doing an import for example).
FYI the chain flow is admin.vm -- getRenderedContent() -->
XWiki.AdminSheet --> XWiki.AdminImportSheet --> importinline.vm, which
requires the current doc to be XWiki.Import (to get/put attachments
from/to it).
I can fix this easily using a new getRenderedContent signature I've
introduced.
However I'm wondering if we have other places that incorrectly use
getRenderedContent() and assume it won't be rendered in the context of
the target document.
Is this change too dangerous to make? If not know, we'll need to it
quickly (2.1M1?) since it's an important bug IMO.
WDYT?
Thanks
-Vincent
Could be useful:
http://ocpsoft.com/prettytime/
Idea of usage: For ex we could use that to show the last modified
document dates for dates in the past week (for ex):
"Document created 2 days ago"
It's in the maven central repo and it's under LGPL
-Vincent
Hi Everyone!
I have read this document "Writing GWT applications in XWiki" (
http://dev.xwiki.org/xwiki/bin/view/Drafts/WritingGWTApplicationsInXWiki)
And I know how to develop GWT module for xwiki now. I also have read the
document "WYSIWYG Editor Module" (
http://code.xwiki.org/xwiki/bin/view/Modules/WysiwygEditorModule). I
followed the instruction which tried to integrate the WYSIWYG editor(GWT
application) in wiki pages, and I put the following code in my wiki editor:
"{{html}}
<script type="text/javascript" src="XWikiWysiwyg.js"> alert('WYSIWYG code is
loaded!'); </script> <textarea id="demo"></textarea> <script
type="text/javascript"> Wysiwyg.onModuleLoad(function() { new
WysiwygEditor({hookId:'demo'}); alert('WYSIWYG code is loaded!'); });
Wysiwyg.onModuleLoad(function() { editor = new WysiwygEditor({hookId:
'demo'}); }); }); </script> {{/html}}"
After saved, it only display a blank text area without any sign of WYSIWYG
editor, also there is no alart 'WYSIWYG code is loaded!' popup. Can you help
me figure it out what is wrong with it?
I am planing to develop a tree view using GWT to display Design Rationale
Element. Could you give me some ideas of after my development, how can I
embeded the GWT application into Xwiki pages and interact with the GWT
application?
Thank you very much!
Leon
Hi devs,
We've been working on improving the editors (content, class, object),
and now I have some pretty important UI changes to commit, but not
everybody seems to agree with them, so I bring up a vote.
The whole improvements can be seen on
http://incubator.myxwiki.org/xwiki/bin/Improvements/ImprovedEdit
Here are the individual voted points:
0 Remove all panels in edit mode
1a Parent and title above the content in wiki/wysiwyg mode
1b The same style in edit mode as in view mode for the parent/title fields
1c AJAX Suggest for the parent field
2a New label for the content textarea ("Content")
2b List of included documents after the Content label
3a Syntax switcher in the top right corner of the content
3b Syntax help in the top right corner of the content
3c Syntax help and switcher only in the wiki editor
4 Better label for the version comment
5a Right float the Minor edit field
5b Put the Minor edit label after the checkbox
6 Move autosave in line with the submit buttons
7 Introduce new AJAX-powered Add Object
i) above the objects
ii) bellow the objects
8 Introduce new AJAX-powered Add Object from this class
i) at the top of the list of existing objects
ii) at the end of the list
9 Move the class switcher in the top right corner
9b Remove the class switcher
10 Introduce new AJAX-powered Add Property
i) at the top of the list of properties
ii) at the end of the list
I vote +1 for all of the above, except 9b (-0), and with options 7i),
8ii), and 10ii)
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi,
Our goal is to develop a wysisyg macro allowing to :
- Insert an Image stored on Alfresco
- Insert a link to a document stored on Alfresco
To do this; we have develop a small browser on Alfresco in order to choose
the image to insert (img src) or the file to link (a href).
After selecting the Alfresco file; we need to generate a macro like :
[[Lien vers le doc
toto>>http://alfresco.airfrance.fr/alfresco/.../toto.doc||rel="__blank"
title="Ouvrir le doc toto..."]]
or
[[image:http://alfresco.airfrance.fr/alfresco/..../image.jpg]]
Using the wiki editor and the old Wysiwyg editor; we had no problem to do
this. (Openning popup and populate les link field with alfresco file path.)
With the new editor; I can't find the way to do this.
In fact my problem could be resume to add a picto in the 'link' and 'image'
macro GUI allowing to open my alfresco browser in order to populate the path
!
Any idea to do this ?
Thanks,
Julien
--
View this message in context: http://xwiki.475771.n2.nabble.com/Wysiwyg-editor-and-macro-accessing-to-Alf…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi... Good to know there are people with common interest in embedding xwiki
to existing project.
Here is my confusion. Please comment if you have idea on this.
I have my J2EE project. It uses JSF, Spring and Hibernate. So I have my own
hibernate.cfg.xml and web.xml and other config files.
Now, I'm trying to add xwiki as a module to my project. Since Xwiki uses
Struts and Hibernate, it also has its own hibernate.cfg.xml and web.xml
files.
How do I integrate these two now?
Can I have both of these in my project and move on?
If I am able to work it out, I think I can move forward. I just learnt the
way how we can delegate the struts action management to the spring
framework.
Regards,
Manish
--
View this message in context: http://xwiki.475771.n2.nabble.com/Embed-xwiki-to-existing-project-tp5070278…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
Please provide feedback for the Selective Export UI:
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MultiExportProposal
PS. The HTML+CSS is not final and it's tested only in Firefox. It will be
improved if it gets positive feedback.
If it doesn't display correctly, please use the IMG to visualize.
Thanks,
Caty
Hi,
I would like to add support for secret token verification to prevent
CSRF attacks (see http://jira.xwiki.org/jira/browse/XWIKI-4873).
The main idea is to add a random token as a parameter to each request
that requires edit/comment/admin rights and check that this token is
present on the server side. Since there are many ways one can modify
documents, it would require many changes all over the place, in particular:
* add a public method to XWikiContext:
String getSecretToken()
that generates a random token and caches it in the session
* add a public method to XWikiRightService*:
boolean isRequestLegitimate(String action, XWikiContext context)
to check if the given action is allowed to be executed
* add the following API methods to Context:
String getSecretToken()
boolean checkSecretToken()
for including the secret token into forms/AJAX requests and checking
that the current request is legitimate
* add a new configuration parameter core.useSecretTokenValidation for
disabling this functionality, and the corresponding method
useSecretTokenValidation() to CoreConfiguration and
DefaultCoreConfiguration
* use the secret token (hidden input for forms or parameter of GET
requests) in all templates (*.vm files in web/standard and skins,
velocity macros in applications/**/resources/*.xml)
* check the secret token in Save/Delete/Upload/etc.-Actions and throw
an exception to deny the access if the check fails
* check the secret token in all templates that directly modify data
(e.g. web/standard/src/main/webapp/templates/admin.vm)
* fix all selenium tests that directly modify pages using the
open(...) method
* make sure nothing else is broken
WDYT?
Thanks,
Alex
Hi devs,
It's time for roadmap again in order to define what we want to work on for XE 2.4 (as usual this list doesn't include bugs that we have to fix).
Here's a proposal that takes into account past stuff that we had planned for XE 2.3 and that haven't been done:
* Work on improving performances in general (could be a cache macro, object handling improvements, etc). Any taker?
* Finish xwiki-localization. Suggestion: Sergiu + Thomas
* Lucene as main search engine in XE: Thomas
* Fix some security issues. Sergiu + others?
* Edit Mode UI Changes: JV/Sergiu/Marta
* Continue the Model Reference refactoring - Vincent
* Office preview - Asiri
* Invitation Manager - Caleb
* Rights UI improvement to make rights easy to use at last - Suggestion: Caty + Sergiu
* Support for component versioning and claddloader isolation (prereq for the extension manager) - Vincent
* Integration of xwiki-portlet in sandbox into the platform - Marius
Nice to have:
* Livetable macro - Asiri
* Selective Export UI - Any taker ?
* Continue work on Model. Suggestion: Vincent
* Office Export - Asiri
Proposed dates:
* XE 2.4M1: 24 May 2010
* XE 2.4M2: 14 June 2010
* XE 2.4RC1: 28 June 2010
* XE 2.4 RC2 (if needed): 5 July 2010
* XE 2.4 Final: 12 July 2010
WDYT?
Please everyone confirm if what is put next to your name is ok with you or if you have other ideas or wish to work on something else. I'll then update
http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap
Thanks a lot
-Vincent