Error Message "Fatal error: Cannot access empty property"
soccernyc - December 28, 2008 - 22:31
| Project: | RSVP |
| Version: | 6.x-1.0-rc1 |
| Component: | Integration |
| Category: | support request |
| Priority: | normal |
| Assigned: | soccernyc |
| Status: | closed |
Jump to:
Description
Here is an error message I receive when trying to use the invite link after creating an event.
Fatal error: Cannot access empty property in /home/soccerny/public_html/drup/modules/rsvp/rsvp_dateconnector.module on line 20
Any help given, is very appreciate - thanks so much for developing this module!

#1
Hi,
Which "invite" link exactly did you click on? How does the url of the link look like that causes the error?
What rsvp permissions does the user has if he is a registered user?
Thanks,
Ulf
#2
Is it possible to have access to your site? If yes, could you create an account and a new role for me and give the role rsvp admin privileges.
That is probably the fastest way to find out for me what is wrong.
Thanks,
Ulf
#3
Hi soccernyc,
After looking into your configuration, I found that you use the event module to manage your events, but you enabled both "rsvp event connector" and "rsvp date connector" for date.
At the moment the rsvp module works only with one or the other enabled, but not both at the same time.
To get the configuration right,
-disable "rsvp event connector" module.
-disable "rsvp date connector" module.
-uninstall "rsvp event connector" module.
-uninstall "rsvp date connector" module.
-enable "rsvp event connector" module.
It is possible that you get some warnings while disabling/uninstalling because you do it for both connectors at the same time bot it should be fine.
I have to do some testing and add some checks to avoid this situation.
Thanks,
Ulf
#4
Your Config worked!
Wow! It's such an awesome tool! I love it! So happy to finally be able to see/use it now.
Thanks so much for your help, you went above and beyond.
#5
Please install the newest development version that will be available soon. I fixed some important issues today.
~
Ulf
#6
Automatically closed -- issue fixed for two weeks with no activity.