By shane on

I've got a 4.3.2 stock system with the book.module and htmlarea.module. I've noticed that when using htmlArea to edit text blocks in the book module, there are severe problems. Primarily, if you edit text in the WYSIWYG mode, then submit, all of the content is LOST. However, if you toggle to HTML Source mode, then submit, the content is submitted and saved properly.

This just caused me over 2 hours of lost content editing time - as I failed to "view" the content after submitting it.

However, other modules do not seem to exhibit this behavior. I've got the contact.module, and the submission of content using htmlArea section for the block text areas works just fine in WYSIWYG mode.

The event.module seems to work jine with htmlArea - so the problem appears to be confined to the book.module (of the modules I've tried to date).

Anyone run into this one yet?

Comments

gordon’s picture

gordon commented

Make sure that you use the cvs version of htmlarea as the book module has 2 textareas on it and the beta version of htmlarea only supports one.

--
Gordon Heydon

shane’s picture

shane commented

Gordon - thanks for the reply. I did try the CVS version and received the following error: 

warning: call_user_func_array() expects first argument,
 'page', to be a valid callback in 
/<b>...somepath...</b>/includes/theme.inc on line 219.

So I moved back to the 4.3.0 released htmlarea.module version. I'm running a fairly stock 4.3.2 system. I just tried the most recent CVS version this morning (Feb 09, 2004) and get the same error. Not sure what to do about it, as I'm not to familiar with callback routines, etc. so not sure how to troubleshoot this.

Any ideas from there? Thanks for your input and any other help in advance.