When "Enable WISIWIG" is off, we can Preview and Submit the form.

When "Enable WISIWIG" is on, showing the button bar, we can not Preview and Submit the form.

Tested on Drupal 5.1 beta.

Comments

Gurpartap Singh’s picture

Priority: Critical » Normal

Please be more specific about your browser & version, operating system, or any other configuration. If there's another javascript being included(other than Drupal 5.x core), chances can be for any kind of code conflict. Also on comment form or content?

xmacinfo’s picture

Followed your advice.

Tested on Mac OS X 10.4.8 and Windows XP SP2. Drupal 5.0 beta 1 (core only) with widgEditor as the only extra.

  • Mac Firefox 2.0 - Cannot submit or preview
  • Mac Safari 2.0 - Working nicely
  • Mac Safari Nightly webkit - Working nicely
  • Windows Firefox 2.0 - Cannot submit or preview
  • Windows Internet Explorer 6 - Norking nicely

All tests done with the creation of a new Blog entry.

If you cannot duplicate this bug with Firefox 2.0, I'll look in the extensions installed and the preferences.

Gurpartap Singh’s picture

Cannot duplicate this for Firefox 2.0 in Windows XP or OSX. Some unrelated problems with Safari though.

xmacinfo’s picture

I will try this on a new Windows XP box Monday.

As for my versions of Firefox 2 on OS X and XP, I will try to enable/disable some JavaScript preferences and do the same with Firefox extentions.

Gurpartap Singh’s picture

Status: Active » Postponed (maintainer needs more info)

Any followup?

LaurenH’s picture

I too have this problem. I am using the WebKit (Safari) nightly build in OS X. With widgEditor active, I create a blog node, type some content, and hit preview, only to find the body field no longer has any of the content I typed into it. However, if I submit the page, the content does get submitted, If I switch to the code view before submitting, I can see the HTML code for the content, so it's still there, just not being loaded into the preview's body field.

Gurpartap Singh’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

The original issue might be related to some javascript error on that page that broke the setup. Since it's been long time since this issue was reported, I'm closing it. In case such a problem persists for anyone, please report.