TOPIC: Pre-sale questions

I appreciate your patience. Here are the last questions I have:

1. Can I add my php code/callback my code after an user register for an event and have access to that registration record? (so I can add an JEvent automatically with his registration id and save the JEvent id into his registration record)

2. Can I add my php code/callback after an user unregister for an event and have access to that registration record/ (so I can delete the JEvent associated with that registration)

3. Can I unregister an user for an event from my php code? (so I can unregister it if an user remove a JEvent associated with a DT event)

4. Can I use a php script to create a DT event without using your entry form?

I am not expecting these features to be available, but I need to know if it's possible to go behind the scene and do this stuff by myself.

Thanks again

Of course this type of thing is possible if you write the code to do it. All records are stored in the database. Each event has an ID, which is connected to each record. You can trace everything through to update / delete whatever you need to.

I am shocked by the way you answer the PRE-sales questions. My questions were very specific and at the point. I was expecting your answers to be the same. I didn't ask what a php script can do, I asked what the extension you sell does and how it's possible to extend it to cover very common (for me) cases. My goal was ti buy your product and since you advertise integration with others and since there is no way I can test this integration without buying it, I don't get your attitude.

Maybe you need to re-read the rest of this thread. I've answered your questions with much detail in regards to existing functionality of our product and am happy to do so. I've also not answered with any attitude at all.

In my last response, I was simply stating that what you want to do is possible, but none of that functionality presently exists. DT Register does allow users to cancel their registrations. The whole connection of showing your history in a separate calendar to view yourself is the functionality we already discussed that you would be adding. So your last post about specific functions to process along with that would all be apart of your new customization.

If you choose (in 2.7) to integrate an event with JEvents, it syncs ONE event where it will display in both DT Register and in JEvents as an event that displays for people to register for. That is the extent of the syncronization. The event ID from JEvents will sync in the database with the eventID in DT Register to connect them. Your customization would have to check all connecting IDs, along with userIDs and whatever else you need to put together your custom features.

Outside of providing actual code and instructions, I'm not sure what else you are wanting here in this forum. Obviously code and instructions are not going to be given here. Thanks.

Let me ask you a specific question from a user perspective: you have a website with 1000 users, 100 of them are "teachers" and the rest "students". The teachers can add "classed"/events in the calendar. The students can see those 200 events and can sign up for them. After more than 50 events added in the calendar, how would you expect a student to keep track of the events he signed up for and the events he didn't by looking in his calendar? If he'll look at the "public" events, probably there might the 200 events per day. The user would need a way to see the events he added (as JEvents) AND the DT events he signed up for, this is his OWN calendar.

I think you are wanting to make things more complicated that it needs to be... creating duplicate copies of events in a separate calendar for each user. Your going to end up with tons of records and probably a big mess. Here's my suggestion which makes much more sense I believe...

Just using the DT Register calendar, add an option where the user can filter the calendar view to show only events that they have registered for. Then create navigation so the user can click to see their registration in the calendar view... list view... whatever they want.

This way, there is only one calendar to deal with... no duplicate copies of events... just displaying data as needed in various ways. That would be a lot less customization too. No need to create extra data, or try and keep two different calendars in sync. Hope that helps the thought process as you sort out what you need to do.