Features integration from work we've done using RSVP module

muhleder - September 8, 2009 - 09:50
Project:RSVP
Version:6.x-2.x-dev
Component:Miscellaneous
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active
Description

Hi Ulf,

we've used this module on a site that launched yesterday, and wanted to share back some of the additions we've made, if there's any interest on bringing the work into the module.

I'll use this issue to give a general overview of the changes we've made, and will hopefully get some time from the agency to separate everything out into individual patches with their own issues if you're interested. Would be good to hear what your plans are for the module rewrite you mentioned, and see if there's any way we can integrate our work with yours.

The work we've done covers a few main areas;

Extra views integration.

Timestamp for invitee response and invitation sent. (Issue 547990)

Move email templates into theme overideable files, and put settings into admin section, so they can be edited without touching code if wanted.

Moved lots of the code that is contained in the theme files into blocks, so it's possible to move the pages into different page regions.

Few relatively minor bugfixes for edge cases.

Added a progress bar to the event creation process, with back/forward buttons at the bottom of each pages. This is probably the most valuable of the additions we made, but also the least complete. If you wanted to include this it would probably best be done as part of the module rewrite.

The main issues with the work we've done which still need some work imo are
1. Knowing which section of the process the user is on, this is currently done by url inspection, but my feeling is that there is a better way of doing it.
2. Block display, we have used the Drupal blocks page to display the blocks on the appropriate pages, again, I think this is better done in code, with the option to override.
3. Views for lists of invitees. This is working quite nicely, we'd like to put the views we are using into a set of default views which the user can override if they want. The views are displayed as blocks, which has the same issues as point 2 above.

The site we built launched yesterdy if you want to take a look at it, it's an public event management site for Breast Cancer Care UK, so you can sign up and try out the event creation process.

pinkfridays.org.uk

Thanks,

Mark

#1

ulf1 - September 8, 2009 - 15:38

Hi Mark,

great interface. Looks already really good.
You are very welcome to send your patches and changes. The 2.0 version is very much stable and after releasing the final version, I then have time looking into how to integrate your changes into the code stream.

Extra views integration.
View improvements are always welcome.

Move email templates into theme overideable files, and put settings into admin section, so they can be edited without touching code if wanted.
Sounds interesting.

Moved lots of the code that is contained in the theme files into blocks, so it's possible to move the pages into different page regions.
I guess it was a lot of work to make it work, but I am very interested in that.

Few relatively minor bugfixes for edge cases.
Yes, I like bugfixes.

Added a progress bar to the event creation process, with back/forward buttons at the bottom of each pages. This is probably the most valuable of the additions we made, but also the least complete. If you wanted to include this it would probably best be done as part of the module rewrite.
I am not sure how the integration with the event/date module can be accomplished, but it is certainly worth the efforts because it looks very good.

The main issues with the work we've done which still need some work imo are
1. Knowing which section of the process the user is on, this is currently done by url inspection, but my feeling is that there is a better way of doing it.
Storing the state in the session information is the way to go.

~
Ulf

 
 

Drupal is a registered trademark of Dries Buytaert.