HTMLArea does not work after upgrade to Drupal 4.6 - SOLVED

I have the same issue. I removed the DB table form the old installation and it still doesn’t work.

Can you please upload a static copy of the page so I can check the parameters so I can see what the problem is.

just letting you know that we´re having the same issues with 4.6 and htmlarea/xinha, it shows up in the admin and we´ve configured it so that part do work, but it just doesnt show up in any text fields whatsoever.

I have looked at it, and I have worked it out.

goto htmlarea plugin configuration page, and reset up the plugins. this will fix the problem.

Sorry about that everyone.

i had hoped someone else would still have issues with 4.6 and htmlarea/xinha because im afraid it´s still not working for us....

the htmlarea module worked just fine in 4.5.2 for us, and we´ve both tried an upgrade to 4.6 and once we had tried everything we wiped the install and did a clean install of d 4.6, but htmlarea/xinha still wont work, it´s working perfectly in the admin settings but it just wont show up in the text fields.

i´ve checked and the use rich text editor is checked so awell im out of ideas, guess we´ll have to try one of the other modules which i realy dont feel like htmlarea worked flawlessly otherwise and the 4.6 implementation looked even better.

Can you please upload the static html so that I can take a look at the js and make sure that there is not some setting that is stuffing things up.

yep i could do that but problem is that there´s not even a single trace of htmlarea in the source code so that wont help you either........ And yes the add revision to html page box is checked, lol beats me whats going on, everything else is working like it should but the rich text editor part obviously isnt.

Im going to check and see if we can get tiny up and running, if it does we´ll have to look into htmlarea a bit more, if it doesnt work then there´s something realy weird with our 4.6 upgrade/install.

Anyway, i´ll let you know what happens and sure you can have the html if you want it.

If there is no trace of it the it is most likely the "Textarea specific visibility settings" on the admin > settings > htmlarea page are not set right.

Make sure it is not set to "Show on only the listed pages." as then it will only show in the textareas of the admin/settings/htmlarea pages.

nah it´s set to show on every page except for the listed one, and i´ve even tried wiping that list completely clean.
Im tempted to do one more clean install of 4.6 in case something borked up with the installation just seems weird that htmlarea would act like this all of a sudden.

If you want I am in #drupal-support at the moment, if you want to talk over IRC and I can work with you to sort this out.

I just looked at the source, The big thing that just jumped out is. Htmlarea module no longer distributes htmlarea js or Xinha with it. You need to download this from xinha.python-hosting.com and unpack it into the htmlarea module directory.

cheers for the drupal support on irc, just noticed it so i guess im to late, since i´ve been busy giving a couple of clients support myself :)´

as for xinha i´ve downloaded and extracted that one aswell but thanks for keeping an eye out for possible reasons, but im at this point pretty sure it´s something with the 4.6 install that´s gone bad and not realy something with htmlarea thats wrong.

I´ll let you know how it turns out of course and thanks again.

Here are the reasons why htmlarea will not had the js into the page.

1. it's a bad browser (IE 5 or safari)
2. the user has the "Enable rich text editor while authoring" unchecked". if the user has not edited there settings then it will take the default from "Default for New Users"
3. The htmlarea js directory cannot be found.
4. lastly it doesn't pass the "Textarea specific visibility settings" check.

Because you said before that it is working in admin I think that it is that last check that is failing.

I have exactely the same problem with HtmlArea and Drupal 4.6.0. on all the pages. tried all the above tips but nothing helped so far.
the source of the pages are empty of any sign of HtmlArea code.

it looks to me its a problem with Drupal itself. maybe someone of the drupal main-engine-crew knows something about that issue?

hi gordon just for kicks, 1, 2 isnt the case here, it used to work prior to 4.6 and since im a web and media developer i´ve tried it with both ff,ie6(+ maxthon) and netscape and opera.

and 3 shoudnt be an issue either but just for kicks and to rule it out, where should the javascripts be placed in the 4.6 html area version (im fairly sure it´s the same as before but since 1 and 2 is out of the question i had to ask just so we can rule that one out)?

as for 4. well im inclined to believe the same thing as you, but if so what can i do about it?

im glad(Sad) to see that we do have one more user with the same issues, so yes im leaning more towards it being a drupal 4.6 issue but anyway lets look @ 3 and 4.

If you guys can contact me via my contact page I will send you a versiopn of htmlarea with a little debugging in it so I can determine exactly what is stopping Xinha from working.

done, looking forward to giving the debug a go

i´ll be online wednesday 10.00 to 18.00 gmt+1

hi All,
i'm in the same boat. I'm getting a Javascript error via the Firefox console:
Error: start_editor is not defined. No HTMLArea controls at all; just a text area.

i'll be following along this thread. if you want to send me a debug version, i'll be glad to bang on it.

e-mail to : misc at tinorb dot com

Thanks,
m

Basically what come back from the debug version of htmlarea that I sent out was that they did not have the version of xinha installed in the correct place.

Xinha needs to be unpacked into.

modules/htmlarea/xinha(-latest)

I am thinking of commiting the debug version with an option to turn on and off the debug mode which puts comments in the html about why the xinha did not load.

problem for us is that xinha is installed in /modules/htmlarea/xinha (and we´ve tried modules/htmlarea/xinha-latest)
so that information didnt solve it for us but we´re continuing to look into it together with gordon.

If I'm looking at the directory structure,

[root@snoop html]# ls -la modules/htmlarea/
total 280
drwxr-xr-x 5 root apache 4096 Apr 23 18:03 .
drwxr-xr-x 7 root apache 4096 Apr 23 17:39 ..
drwxr-xr-x 3 root apache 4096 Apr 16 04:01 docs
-rwxr-xr-x 1 root apache 36117 Apr 15 09:52 htmlarea.module
drwxr-xr-x 4 root apache 4096 Apr 23 18:03 plugins
-rwxr-xr-x 1 root apache 778 Mar 10 13:57 start_drupal.inc
drwxr-xr-x 8 root apache 4096 Feb 11 14:34 xinha
-rwxr-xr-x 1 root apache 217864 Mar 25 15:45 xinha-latest.tar.bz2

and

[root@snoop html]# ls -la modules/htmlarea/xinha
total 292
drwxr-xr-x 8 root apache 4096 Feb 11 14:34 .
drwxr-xr-x 5 root apache 4096 Apr 23 18:03 ..
-rwxr-xr-x 1 root apache 2373 Feb 11 13:14 dialog.js
drwxr-xr-x 2 root apache 4096 Feb 11 14:34 examples
-rwxr-xr-x 1 root apache 525 Feb 11 13:14 gogodist.sh
-rwxr-xr-x 1 root apache 5199 Feb 11 13:14 htmlarea.css
-rwxr-xr-x 1 root apache 14135 Feb 11 13:14 htmlarea_css.js
-rwxr-xr-x 1 root apache 130995 Feb 11 13:14 htmlarea.js
drwxr-xr-x 3 root apache 4096 Feb 11 14:34 images
-rwxr-xr-x 1 root apache 8251 Feb 11 13:14 index.html
-rwxr-xr-x 1 root apache 7512 Feb 11 13:14 inline-dialog.js
drwxr-xr-x 2 root apache 4096 Feb 11 14:34 lang
-rwxr-xr-x 1 root apache 1628 Feb 11 13:14 license.txt
-rwxr-xr-x 1 root apache 547 Feb 11 13:14 makefile.xml
-rwxr-xr-x 1 root apache 56 Feb 11 13:14 make-patch
-rwxr-xr-x 1 root apache 7161 Feb 11 13:14 make-release.pl
drwxr-xr-x 16 root apache 4096 Feb 11 14:34 plugins
-rwxr-xr-x 1 root apache 9662 Feb 11 13:14 popupdiv.js
drwxr-xr-x 2 root apache 4096 Feb 11 14:34 popups
-rwxr-xr-x 1 root apache 3819 Feb 11 13:14 popupwin.js
-rwxr-xr-x 1 root apache 101 Feb 11 13:14 project-config.xml
-rwxr-xr-x 1 root apache 26366 Feb 11 13:14 reference.html
-rwxr-xr-x 1 root apache 7141 Feb 11 13:14 release-notes.html
drwxr-xr-x 2 root apache 4096 Feb 11 14:34 tests

seems to be OK, isn't it?

It works perfectly on Firefox, but not on IE 6.

i'm having a similar issue with htmlarea/xinha in 4.6, and i think it may be related to the phptemplate theme engine. earlier today i switched the site i'm working on back to stock 4.6 code, installing *only* the htmlarea module, and everything worked fine- until i setup phptemplate and switched to our custom theme. then i switched to a stock phptemplate theme (box_cleanslate), and htmlarea still didn't work. when i switch back to the standard xtemplate-based theme, htmlarea works again!

are others using phptemplate-based themes? can they verify that switching to a non-phptemplate theme fixes htmlarea? does gordon have any insight into why this might be happening? we're currently investigating what's going on here, as we really want htmlarea to work, but would love any feedback or ideas from others here :)

i think there must be two different issues going on here, then- i tried resetting the plugins to defaults, as described earlier in this thread, and it has no effect on my installation. is anyone else still having this issue?

Can you please upload the static html from the page in question. This will help me determine if it is the htmlarea module of the Xinha javascript and can either fix the problem or send it to the xinha authors.

ok we've found and fixed the problem, which was indeed in our theme. apparently the "stock" phptemplate theme i switched too had also been tweaked (and so was therefore not "stock" anymore) so that both neglected the very important piece of code:

print theme("onload_attribute");

in the <body> tag, which also contains some other custom elements. adding this element back into the body tag made htmlarea work nicely again :)

gordon: i won't bother posting the static html, since we've corrected the issue now, but i thought i'd mention that careful scrutiny of our static html output (and how it got there) was ultimately the way we located the problem here. thanks for a great module, and your help in identifying this bug!

Wait, wait!

I just did an installation (upgrade from 4.5.2 to 4.6.0) and I am experiencing something very weird.

In Firefox, HTMLArea (with last nights release) works awesome.

In IE 6, the HTMArea interface loads and then, just as someone would start to type in anything, the interface grays out. And IE users can't enter anything in.

I didn't see anything mentioned like this, but would appreciate some help on it or someone to point me to the correct post.

S

I have also tested this in several different themes and it displays the same behavior for each. It just loads up and grays out. IE 6 users can't post anything, it seems.

this sounds like a problem with Xinha and not the htmlarea extension. raise this issue with xinha.python-hosting.com

Hi,

I just installed Drupal 5.3 via Fantastico De Lux, and then htmlarea and xinha.

I've done it on two separate addon domains. It works perfect on one, but I get the _editor_url error on the other. I did the exact same thing on both.

On the one not working, I reset the module, set permissions, etc. And I'm using the default template on both. Someone please help.

Thanks!

Oh, and I haven't messed with the online_attribute issue because I don't know how but I suspect that isn't an issue since its all default and works one one but not the other.

EDIT SOLVED: I went in and deleted my cookies and now it works!

amazing, unpacking into it's own directory was the elusive solution that's been killing me for a month. Wish that was in the instructions...
i'm definitely glad i upgraded tho, this looks beautiful and the tidy html is awesome!

(also running Drupal 4.6 (.11) and htmlarea module wouldn't actually create formatting bars)

DJOH- Can you elaborate on what you mean by 'unpacking into it's own directory'? I am running drupal 5.5 and I am having some issues. I am able to administer but i can't see the toolbar. Any suggestions?

I meant that previously, I'd unzipped Xinha directly into the htmlarea folder (so Xinha files were all over the htmlarea folder). This didn't work at all.
What fixed it was to extract Xinha into it's own directory, into modules/htmlarea/xinha/