I think we'll probably place the code above the recordsets so you won't run into this problem.... of course this will cause a problem if you try to use a recordset as the plugin trigger or value, but in that case we will at least be able to alert that you are using a recordset and need to manually move the code below the recordset you are using.Unfortunately Dreamweaver Server Behaviors use a weight system that doesn't allow you to move the insert position based on settings or page setup, so we have an issue either way, but this one seemed easier to alert and document than the one you ran into.
Ray,
I hadn't thought about the issue with recordsets. I think in that case, you would actually be better going below the recordsets and using a warning to alert users that if they are using a complex page with recordsets that occur in the body, they will need to possibly move them up.
Or better yet, is there a way to put dynamic plugins or any plug in that has a binding to go below the recordsets and then put any static plugins with no bindings above?
Overall, though, I would say most users rarely have recordsets within the body (at least much less of the time) so with that known, I would actually leave it just how it is. In fact, had I had this extension before I created the site I was testing on, I probably would have never had a recordset AT ALL in the body because I would have used the plugin architecture to achieve that purpose.
Best regards,
Brian
