I figured to use javascript to read the id from the url.

Hey Ed,

It is of course accessible from the $vars['entity']->guid variable, which I have done for forms_data listings. But I would also like to bind other standard elgg entity fields to form fields - e.g. most form entries have a 'title' field, which I would like to bind to the $vars['entity']->title field. This makes form listing and river entries a lot more informative than they are currently.

Newbrie

Just to note that the latest version of the form plugins now supports a {$_guid} template field.

Hi Ed,

This is an event calendar, rather than an appointment calendar. So I think that some of the features you mentioned might not get added, at least not for a while.

I'm currently working on an unrelated plugin for a client which should allow moderating all group content (basically the access control dropdown is removed for non-admins, all content is set to private and admins can change that to make it visible to everyone else).

Just as a further comment - the range of requested features for this plugin is vast, and I need to be careful to avoid making it so complex that it becomes too hard to use.

If you look at the plugin settings for the event calendar, I think that you will see that it is already bumping against this limit.

Hi Kevin,

Yeah, I think moderation should be a standard group feature. Looking forward to that plug-in of yours! (",)

With regards to the appointment, I think it's just a matter of application. Sometimes, just by modifying the language to reflect a different field name or system message can create a different experience for the user. Just my 2 cents worth. (",)