Back and next arrows on sponsor_node page lead to unexpected behaviour

[hyanwong]

Clicking the arrow ringed in red here:

Should normally advance the in-page row to some new species. Now, instead, it leads to this page:

[hyanwong]

I assume we have lost some sort of styling here? This is new behaviour, so I don't know what has changed.

Having said which, it seems to be doing this on production too. Damn.

[lentinj]

I'd assume the link wasn't intended to be followed, instead the carousel contents should have been replaced.

Any javascript errors in the console?

[hyanwong]

For triage, this is the system we are using:

http://web2py.com/books/default/chapter/29/12/components-and-plugins#Trapped-Ajax-links-and-the-A-Helper

See e.g.

OZtree/views/default/sponsor_node_price.load

Line 32 in fb6a70a

<li>{{=A(XML('&gt;'),_href=URL(vars=vars),cid=request.cid)}}<li>

[hyanwong]

I'd assume the link wasn't intended to be followed, instead the carousel contents should have been replaced.

Any javascript errors in the console?

Yep:

I'm thinking we might need to update the stuff in static/js

[hyanwong]

OK, I've tracked this down. It's because of this line:

OZtree/views/uikit_layout.html

Line 34 in fb6a70a

<!-- include 'web2py_ajax.html' could be done here, but it performs more than we want so we disect it and keep only the bits we really need -->

There is some functionality in web2py_ajax.html that we do need and we are not importing.

Is it just the calendar stuff we are discarding? If so, maybe we should simply comment that out from the web2py_ajax.html file and then include it after all, rather than hand-coding? What do you think @lentinj ?

[hyanwong]

Also, there's no harm in updating the various web2py-specific things in static/js, I suppose?

[hyanwong]

Fixed by #806