1.4.2 to 1.5
1.4.2 to 1.5
I was trialling 1.4.2 and was about to go live..and today my trial expired and i have bought a license.. i downloaded 1.5 and it breaks..
specificaly..i am using the ajax method to send data to server and handling it there..
i observed that:
in 1.4.2, for a single bubble edit, entire row is sent
in 1.5, for single bubble edit, only that cell is sent
but the docs say in 1.5 only multi row protocol changed, but i am seeing it different...
can you please confirm this?. I have tried legacyAjax also, still it sends single cell edits, not entire row.
and i cant seem to find the 1.4.2 licensed version to download
This question has accepted answers - jump to:
Answers
Hi,
Sorry to hear you have encountered problems with the upgrade.
What is happening is that when you edit a single field in bubble mode it will submit only the value of the field edited. While this was an intended feature, based on feedback, I think this qualifies as a bug now. I'm planning on releasing 1.5.1 next week to address it.
In the mean time:
There isn't a download facility for old versions just yet (something I'm going to add soon). Can I use the e-mail address you used to register for the site to e-mail a copy of 1.4.2 through to you?
Allan
allan,
Thanks. I think the single field feature is good, and it was a feature i was looking for as wel. Its just that i had my backend done to work with 1.4.2 fullrow protocol, and need to go live.. i will update my backend to 1.5 protocol later..
in the meantime, yes please email to that address the 1.4.2
regards,
allan,
What should be the returned json upon a successful edit action?
in 1.4.2... it was entire row as {column1: value1, column2: value 2}
as of 1.5.. whats the expected json return?
The client / server protocol is documented in the manual.
You can also use the
legacyAjax
option to have Editor use the legacy format if needed.Allan
allan,
So for single column update also do I have to send back the entire row again?
I have tried legacyAjax, but it is still sending single column update.
That is correct yes. The reason being is that that single update might have effected other fields. I am thinking about relaxing that constraint and having it merge the new data with the old.
Yes, Editor 1.5.0 will only send the field that has been edited when using inline or bubble editing. In retrospect that change was a mistake and 1.5.1 will enable an option to allow it to submit the whole row. 1.5.1 should be available at the end of next week all being well.
Allan