I already have a membership plugin, but can see using ParticipantDB as a transaction DB.
To do this, I could reconfigure the tables to permit a registered user to access a page which has text-entry fields and check boxes, etc. I would use the existing loginID as a foreign key and a timestamp for uniqueness in creating new records.
In “PDb_Init.class.php,” I see the create statements, table structure and arrays for values. I am thinking that all of the customization I need to do for creation will be done here. Am I right? Are there other files which need to be aware of changes?
After I get this working, I will want short_codes. Will new templates suffice?
I will also need to instantiate new transaction records with read-only values (userID and TS) acquired in-session. Is this a short_code issue?
- The topic ‘Using plugin as a transactional DB’ is closed to new replies.