It’s been a while since I wrote that code and I’ve been working hard on trying to get 1.6 to a more functional state (which I believe it’s mostly there now.) Of note, while you can tie into the common ajax code sitting within for setupTimeoutElement and submithandlerfunc, the common thing to be noted is that you can have your JS code do whatever you need. Those methods are available, but there’s no 100% dedication to using it. Use it where you can, but it’s not a requirement. The js code get’s loaded automagically in 1.5 via node and sub in the get request. So let’s say you wanted js code to alter the list page for some reason. Your plugin node code would be say exampleplugin. You would simply need a file named: fog.exampleplugin.list.js (file names are always: fog.<node>.<sub>.js) Hopefully this makes sense. So in keeping with that file scheme, common files I can think of for a plugin named exampleplugin would be: fog.exampleplugin.js //base js for all exampleplugin node items. fog.exampleplugin.list.js //exampleplugin's list page. fog.exampleplugin.add.js //exampleplugin's create/add item page. fog.exampleplugin.edit.js //exampleplugin's edit item page. While I’m sure this doesn’t answer any of your questions, it should help with getting something functional. You can use other plugin’s to help in the understanding of the js files too. A common one I like to use that interacts with both groups and hosts is the location plugin. This should give a pretty good understanding of what to do, and how to do it. If you still have questions please ask and try to be detailed in exactly what you’re looking for.