#236 new

Urgent: ajaxoptions hiding the inpace editor params

Reported by Krish | August 27th, 2009 @ 08:51 AM

According to the API you should be able to provide the normal AJAX options to the inplace editor. I need to pass the session ID in the AJAX request so I added it but it seems to hide the inplace editor parameters. See the difference between the output below.

  1. Without the AJAX options. the editor id and value are passed along.

var editor = new Ajax.InPlaceEditor(divId, textUpdateUrl, {



27-08-2009 16:28:05 DEBUG - [update.php:100 (Logger:debug)] Array [ value => asdfasdf, editorId => txt_1_inner ]

  1. They are missing here.

var editor = new Ajax.InPlaceEditor(divId, textUpdateUrl, {

ajaxOptions: {
    postBody: 'SESSION_ID=9e5b697cb9fe9d1e258fe95d94d1bb5d4a95cbd1'


27-08-2009 16:29:12 DEBUG - [update.php:100 (Logger:debug)] Array [ SESSION_ID => 9e5b697cb9fe9d1e258fe95d94d1bb5d4a95cbd1 ]

I really need to resolve this immediately. As a workaround, is there a way to put the editor params in the ajaxOptions?

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket