I get this error:
Fatal error: Call to undefined function get_option() in /testserver/wordpress/wp-content/plugins/event-registration/event_registration_export.php on line 24
The reason you are getting that error is that wordpress is not installed in the root directory of your website. The plugin was written assuming it would be in the root installation. In the plugin folder there is a file called event_registration export.php you will need to change line 3.
Current:
3. define( ‘ABSPATH’, $_SERVER['DOCUMENT_ROOT'] . ‘/’ );
Modified:
3. define( ‘ABSPATH’, $_SERVER['DOCUMENT_ROOT'] . ‘/your_subdirectory_name
Sign Up for Authorize.net Account
Muzza,
Please provide me a little more detail into what you would like. It is not complicated to integrate your users (for example if they are logged in, to auto fill in their data).
I was getting the export problem, did the suggested hack to no avail, then looked more closely to find that it was YOUR bogus use of the /mission/ subdirectory in the corresponding event_registration_export_csv.php was causing the biggest problem.
Couldn’t this have been done more sensibly by using an abspath inherited from the general setting of the blog address URL rather than what would appear to be one’s domain name, after all there are a large number of blogs out there not in the root directory.
My other gripes
(1) the filename generated (export attendee list to csv) is just the first word of the event name (shouldn’t it be the full name with spaces or hacked to _ (underscore) as in slugs.) Or if you need a shortname the Event ID for paypal (if defined) could be better than the first word of an event name
(2) the events dont appear to list in either date or ID order. My events were defined in date order.
(3) there seems to be no processing in the interface to set the start or end time of an event. Yet the associated strings are documented on avdude.com which I found via http://wordpress.org/extend/plugins/event-registration/
(4) no links to avdude.com or the http://wordpress.org/extend/plugins/event-registration/ web pages from edetechweb.com which give the crititcal setup information for the use of the plugin.
(5) One concept that seems to have been omitted is that of the registration closing time, which one may want to be earlier in the day of the event or many hours or even days before the event.
(6) on the configure organisation page the string “Do You Want To Send Confirmation Emails? (This option must be enable to send custom mails in events” should be “Do You Want To Send Confirmation Emails? (This option must be enabled to send custom mails in events” – sorry only a minor typo
(7) on the event setup page “DO YOU WANT TO SEND A CUSTOM CONFIRMATION EMAIL?” always defaults to yes – Its annoying to have to change it to no every time when I want to use the settings I have modified on the configure organisation page 19 out of 20 times.
(8) On the regform setup page the field for the event name is not expanding as on the event registration page so the full event name is not displayed. I have dates near the end of my event names that are only partially visible.
(9) How do you configure it to say “Postcode” rather than “ZIP code” ? without hacking it too much so that I don’t have to re-hack the plugin files every time there is an update. Some of my users may not be that computer literate to realise that Postcode and Zipcode are the UK and US versions of the same thing.
Sorry if this list is long. its a very useful plugin. In the winter I could have it in use for 2 “active” events at the same time. (Fishing matches – on a River or a Canal) or it may even be possible to have a Lake event as well)
DavyB,
Thank you for your comments. I am working vigorously to resolve many of them. Please download the latest version from the wordpress website and provide me your feedback.
thanks
John,
Can you give me admin access to your wordpress so I can look at the issue?
Only just noticed your reply 27-July-2009 09:15 GMT+1 (you dont have a subscribe to comments) some of the above issues may have been resolved by the update to 4.0 the repository says you plugin is 47 days old ie 10 June or thereabouts 31-may would be a 3.x release which has since been updated about 11 June – will recheck issues and get back to you