On Jun 14, 2008, at 3:10 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-06-14 03:10:55 +0200 (Sat, 14 Jun 2008)
> New Revision: 10325
>
> Modified:
> xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/web.xml
> Log:
> XWIKI-2117: encoding problems with AJAX adminstration utility
> Fixed by not ignoring the specified character encoding sent by the
> client.
>
>
> Modified: xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/
> web.xml
> ===================================================================
> --- xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/
> web.xml 2008-06-14 00:31:23 UTC (rev 10324)
> +++ xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/
> web.xml 2008-06-14 01:10:55 UTC (rev 10325)
> @@ -16,6 +16,10 @@
> <param-name>encoding</param-name>
> <param-value>ISO-8859-1</param-value>
> </init-param>
> + <init-param>
> + <param-name>ignore</param-name>
> + <param-value>false</param-value>
> + </init-param>
Some comments on this init-param would be good I think, especially
since the "ignore" name is pretty cryptic.
Thanks
-Vincent
Hello,
I just completed the modifications I mentioned in "Mail Problems"
earlier. Seems to work just fine.
XWiki.sendMessage redirecting to MailSenderPlugin, mail authorization (
= works with any smtp server, local or not), and means to provide
additional Java Mail properties in Admin Prefs.
I just need to test it a bit more and make patches and demo package.
Should be ready in about 12-18 hours tops.
Three things though:
1) I still have no idea what about the subject - it just defaults to
"XWiki Message" in this version.
2) It needed mailsender plugin moved from plugins module to core module
to avoid circulars and other nasties.
3) It still needs some sensible defaults and/or documenation for
validation / confirmation content.
Greetings, Lilianne E. Blaze
On Jun 12, 2008, at 1:50 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-06-12 01:50:00 +0200 (Thu, 12 Jun 2008)
> New Revision: 10268
>
> Modified:
> xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium-
> tests/src/test/it/com/xpn/xwiki/it/selenium/WikiEditorTest.java
> Log:
> XWIKI-1007: Removing all content in page has no effect & the content
> of a wiki page is not allowed to be completely empty
> Added integration test
>
>
> Modified: xwiki-products/xwiki-enterprise/trunk/distribution-test/
> selenium-tests/src/test/it/com/xpn/xwiki/it/selenium/
> WikiEditorTest.java
> ===================================================================
> --- xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium-
> tests/src/test/it/com/xpn/xwiki/it/selenium/WikiEditorTest.java
> 2008-06-11 23:49:28 UTC (rev 10267)
> +++ xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium-
> tests/src/test/it/com/xpn/xwiki/it/selenium/WikiEditorTest.java
> 2008-06-11 23:50:00 UTC (rev 10268)
> @@ -158,4 +158,20 @@
> getFieldValue("content"));
> // TODO: We need to find out how to make a text selection in
> Selenium
> }
> +
> + public void testEmptyContent()
I'd suggest: testEmptyDocumentContentIsAllowed
>
> + {
> + open("/xwiki/bin/edit/Test/EmptyWikiContent?editor=wiki");
> + setFieldValue("content", "this is some content");
> + clickEditSaveAndView();
> + assertFalse(getSelenium().isAlertPresent());
Why do we test for not having a dialog box present? There's content so
why should that happen? If it's required the test should have some
comments to explain it.
>
> + assertEquals(-1, getSelenium().getLocation().indexOf("/
> edit/"));
I don't understand this either since we have clicked on save, we're no
longer in edit and the url has view. Why verify this in this test
which is about verifying that empty content is allowed.
>
> + assertTextPresent("this is some content");
Again why test this. The ability to enter content is already tested in
other tests AFAIK.
>
> + open("/xwiki/bin/edit/Test/EmptyWikiContent?editor=wiki");
> + setFieldValue("content", "");
> + clickEditSaveAndView();
> + assertFalse(getSelenium().isAlertPresent());
> + assertEquals(-1, getSelenium().getLocation().indexOf("/
> edit/"));
> + assertTextNotPresent("this is some content");
Is there a need to do the 3 tests which seem to be about the same
verification?
Thanks
-Vincent
Good day, community
Yet one question: I want to retrieve xwiki page without header and footes via
javascript, to save in dom-node.
Now I search a principal way how to do this. I see two possible ways:
A -- write special 'zero' skin
// unfortunelly, I see that documentation on skins is outdated: in
installation of svn version I see that velocity templates are situated outside
skin.
B -- try to use xwiki XML/RPC interface. (or may be add JSON-ORB as servlet)
So, questions:
- what approach (from this two) is prefferrable ?
- where is documentation on xwiki XML/RPC interface ? Or some example of
usage ? Are anybody tried to use XML/RPC interface from javascript. ?
- may be still possible to reload (returning to first approach) view.vm
template in skin. If yes - how ?
P.S. (More detailed explanation what I want on code level:
i. e. I want to write in xwiki page something like:
<script>
function update()
{
new Ajax.Reaqest('/xwiki.home/bin/view/My.Page', 'post'
parameters {
A: $('form.A').value,
B: $('form.B').value,
skin: 'zero'
}
onSuccess: function(transport) {
$('result').innerHTML=transport.response;
}
);
}
</script>
<form>
<input name='A' id='form.A' >
<input name='B' id='form.B' >
<button name='DO' onClick="update();" >
</form>
<div id="result"> </div>
--
Ruslan Shevchenko
GradSoft. http://www.gradsoft.ua
Hello,
Is there any particular reason why /templates are not in /WEB-INF?
I don't like the idea of having part of the source code accessible by
everyone.
Greetings, Lilianne E. Blaze
Hello devs,
I'm currently trying to find the best approach to automatically upgrade an
XWS instance workspaces when upgrading the XWS version. By that, I mean
adding new pages to existing workspaces for example.
I see at least two possible approaches :
* On display of the workspace, we check that the considered pages are
present, and if not either we automatically create them, either we offer a
big button to "upgrade" the workspace. (the test could be done in a skin
template, so that any page would trigger the upgrade)
* On plugin init, we search for all workspaces and upgrade the ones in
need. And we could have a marker once the upgrade is done, not to execute
the query at each init.
WDYT ? Are there other approaches I'm missing ?
Regards,
Jerome.
Hi devs,
While working on the new GWT-based WYSIWYG editor, I find out that the
default DialogBox from GWT moves very slow when dragged if it contains
many HTML elements (like a table with 10 rows and 20 columns). In the
current WYSIWYG editor dialog boxes are used for color picker, custom
character, insert image / attachment / macro / table. Before I start
porting these dialogs to GWT I'd like to ask you:
Do you agree with using dialog boxes for these features?
* if so, do you think it's ok to optimize the way they are moved by
showing only their border while dragging (win95-like)?
* if not, how can we replace them?
Thanks,
Marius
Just to let you know (and especially Marius) that I've discovered that
wikimodel has a XHTML parser already which seems to be doing quite a
lot of things.
I'll be trying it next week and integrate it into the new rendering
module so that the new WYSIWYG module can use it.
Thanks
-Vincent
Hi XWiki users and developers !
It's voting time again.. You have helped me get through to the semi
final a few month ago, and this week is the voting period for the
semi-final. What's less fun is that this time we cannot not the current
voting result in real time so we have to push as much as we can.
You can vote here (in french too but that should not be too difficult ! Make
sure you select the second person at the top !):
http://www.radiobfm.com/bfm_academie/index.php
This can give a nice additional boost to XWiki !
Thanks to all of you for you continuous support of XWiki and
participation to the lists.
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs