After installing the
WysiwygPlugin, I get HTTP headers in the page's sourcecode:
Expires: 0
Cache-control: max-age=0, must-revalidate
<?xml version="1.0"?>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:i18n="http://xml.zope.org/namespaces/i18n" i18n:domain="kupu">
This screws the rendering of the page completely
In what page? Where do you see the headers? What were you doing? Can you reproduce this error on this site?
CC
Unless someone can show me how to reproduce this before next wednesday (21st), I'm going to close it.
CC
I am also getting this behaviour, but only when mod_perl is enabled. The Expires & Cache-control lines appear at the top of the kupu editing area, so when the topic is saved they are added to the "body" (in a similar way to Item1547). If I browse to the URL that
TWiki:Plugins.WysiwygPlugin pulls back the content from (ie: .../view/.../?skin=kupu&wysiwyg_edit=1) the Expires and Cache-control lines appear in my browser. My config is: Cairo, Apache 2.0.54, mod_perl 1.99, perl 5.8.5.
Wasn't sure whether to re-open this one or start a new bug - hope this way is ok.
MLR
I had this happen when adding functionalities to the Wysiwyg Plugin: this is the symptom you get is the perl of the
plugin triggers a perl error...
CN
Mmm, got also this error when installing on a mod_perl site, with
Cairo. Seems that commenting out the code
# DEPRECATED in Dakar (modifyHeaderHandler does the job better)
#$TWikiCompatibility{writeHeaderHandler} = 1.1;
#sub writeHeaderHandler {
# my $query = shift;
# if( $query->param( 'wysiwyg_edit' )) {
# return "Expires: 0\nCache-control: max-age=0, must-revalidate";
# }
# return '';
#}
in
lib/TWiki/Plugins/WysiwygPlugin.pm
fixes it
CN
Aha! OK, then it's Cairo that has the problem. OK, we can simply comment out that function, as you suggest. Though I have absolutely no idea why this is happening; must be some unfortunate relationship to mod_perl that doesn't happen in Dakar (which is a lot more mod_perl safe).
SVN 8867
CC