Closed (fixed)
Project:
RSVP
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
5 Nov 2008 at 02:07 UTC
Updated:
19 Dec 2008 at 07:22 UTC
Jump to comment: Most recent file
Hi Omar,
as promised, here a drupal 6.0 version based on head which I would like to see merged into head as a first step. Since I did a lot of changes I can not tell at the moment if the diff properly worked, and with that the merged result. After the merge I would update and start my final testing based on head
Changes that are included:
-Now supports Drupal 6 and Date or Event.
-Now View 2 complient files. (I Removed contributes directory).
-Cleanup: Removed also rsvp.mysql
I did not deal with version information in the cvs header and alse did not add any version information into the install files.
| Comment | File | Size | Author |
|---|---|---|---|
| #21 | rsvp_5.patch | 81.12 KB | ulf1 |
| #21 | pic.zip | 3 KB | ulf1 |
| #14 | rsvp_4.patch | 171.3 KB | ulf1 |
| #14 | rsvp_4.tar_.gz | 50.16 KB | ulf1 |
| #13 | rsvp_3.tar_.gz | 47.31 KB | ulf1 |
Comments
Comment #1
scottrigbyHi Omar,
Thanks for this - I'm testing out this patched version of RSVP on Drupal 6.
So far, I only have one issue (because it prevented me from going any farther), and one other observation.
Issue:
* I've added a CCK node type called 'event' just for fun
* I've added a date field (tried with both 'date' and 'datetime' - does it matter which? the README says datetime, but I usually prefer date because I sometimes allow only the year and month to be selected, and KarenS suggests date for this purpose - see this issue for ref #269813: Date vs. Datetime)
* I applied the proper permissions ('rsvp on events' to authenticated user, and all perms to site admin).
* I made an association based on date (also tried with datetime)
* The problem is, even though my event is in the future, I'm getting the following message:
* I can't test any further yet because this isue doesn't allow me to rsvp.
Another observation:
* After applying the patch, there are two instances of rsvp_views (one in the contrib folder and the other in the rsvp directory root) - and neither are compatible with D6 core. I assume this isn't waht was intended -- but I can't make out from the patch what was the intention exactly -- was it to delete the contrib folder and add the rsvp_views.info & rsvp_views.module files into the rsvp module root directory? If so, I can try to add the patched lines manually to those for testing. (but can't do much anyway until the issue above is fixed).
I'm ready to test the next patch whenever you've got one :)
Scott
Comment #2
mradcliffeJust stopping by and noticed this...
should be the following if you want views includes in the module's root directory. Otherwise throw them in /includes.
Comment #3
ulf1 commentedSorry, the latest version was not really that stable.
This one should be way better, it is based again on the current head since rsvp.patch has not been integrated into head yet. You basically can discard rsvp.patch.
scottrigby: The patch should remove the contrib folder all together (at least that was my intention). The view integration is now completely in the rsvp rootfolder (file rsvp.views.inc)
I tried also Date as type and it seems to work just fine. Even if the 'to date' part is disabled. only negative point is that the time is still shown in the rsvp as 00:00:00
mradcliffe: The views work for me without the path declaration. However I can add the path as it seems good practice anyway.
Cheers,
Ulf
Comment #4
scottrigbyhi Ulf,
I tried this patch, and it didn't delete the contrib folder - it still creates another instance of rsvp_views.info & rsvp_views.module in the module root. It sounds like you intended to get rid of entirely, so I removed the contrib folder and those two files from the root as well.
I uninstalled the RSVP date connector module, and tested again with the newly patched version. Then followed the same steps as above...
But I'm still not able RSVP (?). Same error as above
This event has expired....If it works for you, it seems possible the patch didn't work in other places as well? I'm attaching the module after trying to apply the patch (and after deleting the rsvp_views files mentioned above. Can you try this and see if you can reproduce my error?
If so, could you please attach a patched version since it would seem there are problems with the patch?
Thanks :) Scott
Comment #5
ulf1 commentedHi Scott,
Your patches code is the same like mine which means the patch process run through successfully.
rsvp_views.info & rsvp_views.module can also be removed. That is correct.
The module checks if the end date (to date) is earlier then the current date. If that is the case you see this "The event is expired" message. My guess is that your "to date" that you specified is older then the current date for what ever reason. Please copy the attached file into your rsvp folder, rename it into "rsvp.module" and try to create an rsvp. You should then see some variables at the top of the screen. Please post them or send them to me.
Thanks,
Ulf
Comment #6
scottrigbyAha... - Ulf, the problem was in my datefield... I had (to date) set to 'never' (rather than optional or required) - to allow only a single starting date and time.
So I now set it to optional (so I can choose to have only a start date if I want), and now I can RSVP! So I did not apply your test module, because it looks like we found the problem. Personally this is fine for me, because I will need a (to date) for my application anyway.
This issue may be a fringe case. however because 'never' is a (to date) configuration option for the date module, we might want to check whether the datefield has this option available before checking if the end date is earlier then the current date? Or maybe we just need to add this note to the README so people know to enable the end date.
I'll continue to test -- but this at least clears up this particular issue -- Thanks ;)
Comment #7
scottrigbyOops, I spoke too soon...
I created an RSVP using the above case - but then got these errors:
Then I went back to my event - and the (to date) was completed to match the start date & time.I thought - maybe datefield doesn't save this automatically, but only completes if you go back to edit the node. So I saved the node just for kicks... (so start & end date/times are exactly the same, rather than leaving end date empty).
It now looks like the RSVP is ok -- or at least I'm not getting errors anymore :)
we should check whether to date is an array, and if not, add the data from the from date?
Update:
This is happening even with an ending date.
Comment #8
ulf1 commentedThat still should work without having a "toDate". I found the problem and fixed it.
Please copy the attached connector into your existing installation after renaming it. That should allow you to work without to make an end date mandatory or optional.
Comment #9
scottrigbyHmm, I added attached test in #8 as the new rsvp_dateconnector.module (and renamed the existing one to 'rsvp_dateconnector.moduleOLD'). I also cleared the cache just for fun... (didnt' run updates, because seems this isn't necessary?).
Next I deleted the existing association, and created a new association just to be safe.
I then tried to create an RSVP with an event that does have a start & end date / time set.
However, I get the same error (see attached Picture 2). I can not add or manage attendees under this tab, just see the error there.
But if I follow the breadcrumb trail back, I do see that an RSVP has been created (see Picture 3).
Comment #10
ulf1 commentedThanks.
Fixed with the attached file. Problem was that you do not have simplenews installed which resulted in the error.
~
Ulf
Comment #11
zilla commentedjust staring to follow this now and have a couple of quick questions:
i'd love to help test this - will there be an experimental d6 dev release put up anytime soon for those of us clueless about patching?
the module page says event module is still required, but this d6 version appears to support datecck - what exactly are the requirements if using rsvp on d6 *without* event module? will i still need simplenews to process?
has anybody tested on d6 with date cck where the field is unlimited? meaning: event custom content type with date fields allows one event to be added on multiple times/days in one node - but with a signup reflecting 'each time/date' as an option?
Comment #12
ulf1 commentedI am waiting for Omar to do the integration and update the version information. The module page does not contain any information regarding the D6 version. I updated the README with the current information though.
Here the current development version as patch and as installer. The README has benn updated.
Additional to bugfixes it contains
- a new permission "maintain rsvp"
- a page for admins/maintainers to manage all RSVPs.
I am not quite sure what you mean with unlimited datefields, but you can set a repeated date and create a RSVP for each of those dates.
Comment #13
ulf1 commentedHere an updated patch based on HEAD. Also a version as tar file.
Please uninstall and reinstall because the db format and some cached information have changed compared with rsvp_2.
-some bugfixes (displayed timezone was wrong).
-Now supports "Invitation Links" in Nodes.
-New general RSVP setting to choose which email address to use.
-new specific RSVP option to show attendees or just a summary.
-new specific RSVP option to show responses only after reply.
-List of attendees now contains the comment field as output.
(Not nice but at least it works.)
Comment #14
ulf1 commentedHere an updated patch based on HEAD. Also a version as tar file.
-includes mainly cleanup and some minor bugfixes.
I would love to get more responses if anybody is using my changes seriously.
What needs still a lot of work is the reply and attendee section and I am willing to think about working on it, but for that I like to kow if it is worth my time or not.
Comment #15
Matt H commentedI've been using your patch with Drupal 6, and it's mostly fine.
I've come across one issue: If you only enable 'RSVP', and don't enable any of the other 'RSVP' modules, you get the following error on all non-admin pages:
Keep up the good work!
Comment #16
chasz commented+1
Comment #17
aniko-1 commentedHi, is there going to be a full release of RSVP for Drupal 6? This is a great module.
Thanks
Comment #18
owahab commentedGreat job ulf1 and sorry everyone for being away that long.
I have successfully patched HEAD with #14.
I will create a branch for D6 so we can all test the module.
Comment #19
owahab commentedD6 branch created and module page updated.
Please wait until d.o cron updates the list of available versions of the module.
Comment #20
owahab commentedComment #21
ulf1 commentedHi Omar,
here the newest patch based on the latest 6.0 dev. stream. Please migrate into cvs.
patch contains the following features:
- completed abstraction of response list output using theme hooks.
- Added icons.
- fixed several visibility/permission/access bugs.
- It is now possible to create multiple rsvp's for the same start date (on same node).
- Attendees added by other people then the owner are now marked as such in the response list.
- Added configurable response text per rsvp.
- Added field for number of guests to invitation reply.
Database update is required after patch installation.
The patch is also suppose to contain the icons in binary format but I am not sure if that worked. thats why I added the icons here in a file (pic.zip) as well.
The last remaining part that needs to be done is adding proper stylesheets for the response list. From a programming point I tried to create the output as close as possible to the response lists at www.evite.com, but it still requires a lot of design work to make it look perfect.
Who wants to do that? I am not that great in web design.
The current output can be found in rsvp.theme and rsvp.css
Thanks,
Ulf
Comment #22
ulf1 commented