Just wondering if anyone else is expereinceing this before I log it in the tracker.
The HTML editor is not working for me. It appears, but cannot have any text put in it. This only occurs in IE6.
JR
Is it the same issue as this: http://moodle.org/mod/forum/discuss.php?d=73636 ?
Julian,
I think this is a css issue. Try to copy following tags from standard theme styles_ie6.css to the beginning of you theme's (funky etc) styles_ie6.css:
/*
* These styles are ONLY included for IE 6 (via meta.php)
*/
.tabtree {
height: 100%;
}
.tabrow0 {
padding-top: 10px;
}
.tabrow0 li {
margin-left: 0;
}
.tabrow0 li.first {
margin-left: -4px;
margin-right: -4px;
}
.tabrow0 li.last a {
margin-right: 0;
}
.tabrow0 li.onerow {
margin-right: 0;
}
.tabrow0 a {
padding: 0 0 0 13px;
}
.tabrow0 a span {
padding: 12px 1em 4px 0;
}
.tabrow0 div,
.tabrow0 ul {
top: 2.7em;
padding: 0.2em 0;
}
form.mform input {
margin-left: expression((this.type=="text"||this.type=="file"||this.type=="password")?'-10px':'0');
}
form.mform textarea {
margin-left: -10px;
}
.que .info {
margin-left: 0.6em;
}
Editor should work again (this is the same problem we had with Funky in theme forum - when standard meta tags are not included we need to add them if needed)
A good Moodler has already reported it to the tracker 
Thanks for the roses 
- and for the voting 
- and for the voting
I still suggest checking if theme standardsheets is true or false and standard metatags include true or false (from theme config.php)
I just tested it with IE6 in latest moodle 1.8.3 and it works here with moodle 1.9 (i am using now IE6 to test this). Can someone confirm that editor of moodle 1.9 or moodle 1.8 would not work with standard theme and IE6 on some environment ? Bente???
I tested with the standard theme yesterday and with some other themes too, it do not matter to me which theme you choose, there are problems with all I tried, standard, formal white, cameleon.
About config.php, is this what you mean:
About config.php, is this what you mean:
$THEME->standardsheets = true;
/// This variable can be set to an array containing
/// filenames from the *STANDARD* theme. If the
/// array exists, it will be used to choose the
/// files to include in the standard style sheet.
/// When false, then no files are used.
/// When true or NON-EXISTENT, then ALL standard files are used.
/// This parameter can be used, for example, to prevent
/// having to override too many classes.
/// Note that the trailing .css should not be included
/// eg $THEME->standardsheets = array('styles_layout','styles_fonts','styles_color');
////////////////////////////////////////////////////////////////////////////////
/// This variable can be set to an array containing
/// filenames from the *STANDARD* theme. If the
/// array exists, it will be used to choose the
/// files to include in the standard style sheet.
/// When false, then no files are used.
/// When true or NON-EXISTENT, then ALL standard files are used.
/// This parameter can be used, for example, to prevent
/// having to override too many classes.
/// Note that the trailing .css should not be included
/// eg $THEME->standardsheets = array('styles_layout','styles_fonts','styles_color');
////////////////////////////////////////////////////////////////////////////////
$THEME->metainclude = false;
/// When this is enabled (or not set!) then Moodle will try
/// to include a file meta.php from this theme into the
/// <head></head> part of the page.
/// When this is enabled (or not set!) then Moodle will try
/// to include a file meta.php from this theme into the
/// <head></head> part of the page.
It looks ok - I would check next all activities and javascrits from custom blocks etc (as Tim suggests) that could have conflicts with IE6 or htmlarea = debugging to ALL, does firefox error console show any errors or faulty tags and so on...
Ok, that will be to technical for me.
Not at all. Just start from administration menu
Administration-> Server-> Debugging
Debug messages: ALL Show all reasonable PHP debug messages
Now I have changed to Administration-> Server-> Debugging
Debug messages: ALL Show all reasonable PHP debug messages
Result in IE
Adding a new post in forum gives an errormessage in top of the side:
Notice: Undefined property: stdClass::$en in /home/danskonl/public_html/intra/lib/moodlelib.php(4505) : eval()'d code on line 1,
nothing happen in enlarged editor, it just fails as 'normal'
In FF
No errors are shown
Anyway, it does not make any sense to me. Is this what you think I should do?
Debug messages: ALL Show all reasonable PHP debug messages
Result in IE
Adding a new post in forum gives an errormessage in top of the side:
Notice: Undefined property: stdClass::$en in /home/danskonl/public_html/intra/lib/moodlelib.php(4505) : eval()'d code on line 1,
nothing happen in enlarged editor, it just fails as 'normal'
In FF
No errors are shown
Anyway, it does not make any sense to me. Is this what you think I should do?
Thanks for the response.
this is happening in the standard theme (going back to basics testing this one).
While I do get some errors from custom blocks...this is I believe irrelevant as none of these blocks are showing when I am trying to use the editor.
With debug on I am getting no errors on the screens where I am trying to use the HTML editor.
this is happening in the standard theme (going back to basics testing this one).
While I do get some errors from custom blocks...this is I believe irrelevant as none of these blocks are showing when I am trying to use the editor.
With debug on I am getting no errors on the screens where I am trying to use the HTML editor.
If you have time to test try to install a clean test moodle without any custom blocks to you environment. What version of php your server is running, Julian? For example http://playpen.riverview.nsw.edu.au/course/view.php?id=24?&theme=standard gives lots of css errors like
margin-left::auto;
.#hidden {
visibility: hidden;
}
mod stampcoll 3 css errors
# Stylesheet for block MyNotes v1.0
document.getElementById("dual_clock_l") has no properties
http://playpen.riverview.nsw.edu.au/course/view.php?id=24?&theme=standard
Row: 220
They may be irrelevant or may be relevant - all I know is that IE6 has not got this kind of problems on my server - neither with moodle 1.9 nor moodle 1.8 latest versions so the problem must be either in content or in different environment (php5.2.x ?)
Hi Mauno
I have copied the ie6-styles to fw_layout.css in the Formal White theme (it has no styles_ie6.css). It fixes the problem in IE6 but unfortunately this affects the tabs in Firefox as shown in the attachment.
Then I tried only with the last 3 properties and both IE6 and Firefox is ok. But in both cases I got the problem with the enlarged editor in IE7.
Any other suggestions?
I have copied the ie6-styles to fw_layout.css in the Formal White theme (it has no styles_ie6.css). It fixes the problem in IE6 but unfortunately this affects the tabs in Firefox as shown in the attachment.
Then I tried only with the last 3 properties and both IE6 and Firefox is ok. But in both cases I got the problem with the enlarged editor in IE7.
Any other suggestions?
Difficult to say what is really causing this but I have a couple of suggestions:
1) If address of your server is https://... http://tracker.moodle.org/browse/MDL-10794
The problem is/was in the file /lib/editor/htmlarea/popups/fullscreen.php in line 32 (Andy Tagliani).
This line is back again:
if (/^https?:/i.test(script.src)) {
and for Andy this worked:
if (/^http:/i.test(script.src)) {
2) Also this fix http://tracker.moodle.org/browse/MDL-11242
temporary broke full screen (Martin L fixed it back pretty soon)
Upgrading to the latest version or just copying folder lib/editor/htmlarea over the previous one could help.
3) Theme formal_white has no meta.php so it should take meta tags from (the latest) standard theme (styles_ie6.css and styles_ie7.css). When you said that pasting those tags to fw_layout.css helped for ie6 it makes me wonder if your themes (including standard theme) are from some previous package...
Hope this helps.
Mauno
Thank you very much! I think I solved the problem with Andy's hack. We use https for login.
Bente
Bente