The code for the view that has the problem is:
<index-page>
<content-body:>
<div part="cities">
<table-plus with="&@cities" push-state update="cities" fields="this,
sometext, adate">
<this-view:><a push-state update="suburb-part"/></this-view:>
<adate-view:><click-editor/></adate-view:>
</table-plus>
</div>
</content-body:>
<after-content-body:>
<div part="suburb-part">
</div>
</after-content-body:>
</index-page>
On Friday, September 20, 2013 2:24:01 PM UTC+10, Cameron Taylor wrote:
>
> The problem seems to be that on the index page I have an <a
> update="somepart"/> where the link goes to a show page. The show page
> creates editors but it starts it's editor-dom-id count from 1. Since there
> are already editors on the index page they end up with the same dom-ids.
>
> It seems like I will either need to change the index page to include all
> the relevant data from the show page or somehow override the editor dom
> id's. Is there a simple way to either change the counter used by the editor
> tag or to make the editor tag generate ids with a different suffix?
>
>
>
> On Thursday, September 19, 2013 6:37:14 PM UTC+10, Imanol Alvarez Perez
> wrote:
>>
>> Hello Cameron,
>>
>> i have tryed reproduce the problem but I have been unable. Can you
>> explain a more bit the problem and how reproduce it?
>>
>> Regards,
>> Imanol
>>
>> El miércoles, 18 de septiembre de 2013 06:44:54 UTC+2, Cameron Taylor
>> escribió:
>>>
>>> I have an application that includes two <table-plus/>, each of which
>>> provides in place editing. The second <table-plus/> is loaded via an ajax
>>> push-state link. The problem occurs when editing the first row of the
>>> second <table-plus/>. The edit is sent to the database correctly but the
>>> ajax response actually updates the editors on the first <table-plus/>.
>>> Inspecting the code confirms that the divs are using the same ID sequence
>>> so colliding and the first instance is selected. The app is running at:
>>> http://173.212.223.148:3000/.
>>>
>>> I assume this problem is occurring because I am loading the second table
>>> via an ajaxified link to the show page, which I then show on the index
>>> page. I take it this isn't the right way to go about it? What would be the
>>> hobo convention for this sort of thing. Basically I want a way to click on
>>> a row in my first table and have it load up a child table via ajax. Then I
>>> want to be able to edit both tables. Any suggestions?
>>>
>>
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/groups/opt_out.
