Can not use HTMLarea...Why?

Hi,

How come that i can not use HTMLarea. I can see it on the screen but not get an active marker in it and can not type anything in the text area. Have this problem in both IE and FF.

Peter

Silly question -- but --

Have you selected it in Admin -
Configuration/MyStore/HTMLARREA/ and turned it on?

Laura

DesignbyDemeter:

Silly question -- but --

Have you selected it in Admin -
Configuration/MyStore/HTMLARREA/ and turned it on?

Laura

Yes for sure, otherwise i would not see the HTMLarea active in the Products Description Box.....

If you're referring to attempting to edit in the define-pages-editor area, then you're likely dealing with read-only files, as per the alert on-screen. Make the files writable, and then the editor window will unlock from read-only as well.

I‘m not sure here... I thought the product description was stored in the database and not in a file... but maybe I’m wrong…. If it is as DrByte suggests stored in a file?? Which file then???

Now I’m confused....:no: :no: :no:

I just can't type anything in the HTMLarea..... see the picture

Peter

I 'replaced' htmleditor with Xinha - - htmleditor has a reputation for being buggy I think (for me it comes and goes) - when using Xinha - you right click over the editing box and the editor pops up - works nice

http://xinha.python-hosting.com/

That was a BIG different :thumbsup:
I love Xinha already :D

I don't know if i installed it right but i just renamed the folder to htmlarea and deleted the old one... I seems to work anyway :yes:

Thanks Wasana :thumbsup:

If your are using Firefxo, look at this Xinha Here!

• Xinha Here! is a Firefox extension wrapper for the Xinha HTML editor. It enables WYSIWYG editing in any textarea and text box on any website.

.

Nooooooooo

Ok, i could edit my files with Xinha.... However, ALL my text in every page has disappeared :cry:

What is this?????

Xinha even destroyed all my newsletters. Now, i can not even edit them without Xinha :shocking: :shocking: :shocking:

what a nightmare - when I installed Xinha I didn't touch any ZenCart files - it works with Firefox, not ZC... this has to be caused by what you did with the htmlarea editor files.... if possible I'd take a backstep and re-create the htmleditor files from the original installation files. then use Xinha without extra tweaking. Hopefully - it will restore access to the text... good luck...

No the files are completely empty... nada...zero... maybe it's better to run Xinha localy instead :huh:

PeterBKK:

Now I’m confused....:no: :no: :no:

I just can't type anything in the HTMLarea..... see the picture

Peter

I have the exact problem as Peter. Anyone know how to solve this problem ?
The same problem at Tools -> Define Page Editor, HTMLarea is shown but it's not possible to edit anything in the HTMLarea box...
/Typhoon

Typhoon - This is how i solved it.

Deselect HTMLarea in admin.
Use Firefox as your web reader.
Download the firefox plugin "Xinha Here 0,9"
Thats all

Now you are able to use the WYSIWYG-tool in every field on internet.
Mark the field and right klick and choose "Open Xinha Here" - woula :thumbsup:

Peter

Typhoon:

I have the exact problem as Peter. Anyone know how to solve this problem ?
The same problem at Tools -> Define Page Editor, HTMLarea is shown but it's not possible to edit anything in the HTMLarea box...
/Typhoon

You have to change file /admin/includes/htmlarea.php
Change line 21:

  echo '	_editor_lang = "'.strtolower(DEFAULT_LANGUAGE).'";' .BR;

to:

  echo '	_editor_lang = "en";' .BR;

Bartek

Hello

I have the same problem, but i found the solution.

If u go to admin/includes then u open the file htmlarea.php, then on line 21 u put 2 // then save

looks like this

before changing
echo ' _editor_lang = "'.strtolower(DEFAULT_LANGUAGE).'";' .BR;

after changing
// echo ' _editor_lang = "'.strtolower(DEFAULT_LANGUAGE).'";' .BR;

This work for me, i dont know if this is the good way to make it work or bad way.

Try it and u will see.

From the above two posts, both changed the code related to BR.

I think You don't need to change the code.

There are several points should be noted.

1. the only and most updated language of HtmlArea is the english language.
   It loacaled at:
   htmlarea/lang/en.js

And most of the others are not updated!
Please copy the en.js to you language file or translate it for yourself.
if you are using another language,
e.g.
I use Chinese,
then I will copy en.js to another file as b5.js and I translate it to Chinese.
(And in the admin I use b5 as my language code!)

2. the name of the lanage file of HtmlArea is related to the setup of language code in Zen Cart.
   e.g.
   As pointed out in Note #1 in above,
   HtmlArea default language file is english and the file name is en.js
   And the language code used in default install of Zen Cart is en.

And they works without problem.

Therefore:
A. If you use another language other than the default englihs language in Zen Cart, check that the language file in htmlarea directory is updated. If you don't find the file for you language, just copy the en.js to your own.

B. Even you use the default english language in Zen Cart, check that the language code en had not been changed!
e.g.
If you use english but in admin
the language code changed to br,
then copy the en.js to a file as br.js.

Then it may works although without code change.

These last notes should be resolved in v1.3.5 ...

cableguy:

Hello

I have the same problem, but i found the solution.

If u go to admin/includes then u open the file htmlarea.php, then on line 21 u put 2 // then save

looks like this

before changing
echo ' _editor_lang = "'.strtolower(DEFAULT_LANGUAGE).'";' .BR;

after changing
// echo ' _editor_lang = "'.strtolower(DEFAULT_LANGUAGE).'";' .BR;

This work for me, i dont know if this is the good way to make it work or bad way.

Try it and u will see.

This worked for me, however I can't see why it works. I am using English as the default languare and Spanish as the second language

Commenting out the line for tool tips indeed works (so does forcing lang=en).

However, the cause for the issue, as noted below) seems to be that HTML area does not like incomplete language files. Copying en.js to xx.js (xx being your language code) and changing the code in the file itself does work.

Lets try to post updated versions for future inclusions.