• Hello and thank you for your plug in, documentation and blog.
    Q: Any updates on either of these two teasers?
    “There are a few more convenient methods you can use, which I will demonstrate in the next tutorial on using the PDb_Template utility class.”
    “In the coming months, I will be posting some auxiliary plugins that will give you an easy starting point for creating your own.”
    Thank you!

    Background/Skill Level:
    We’re a homeowners association trying to use your plugin to manage contact info for residents as well as some other descriptive details. We haven’t yet settled on the right structure for how best to implement – one record per house or one per resident or one per family or other? I’ve played w/ PDB custom templates including some using PDB_Template class and gotten some nice results w/ that. Also played w/ your advice about how to mimic multiple databases w/ some success as well. My skill level is generously described as intermediate. I code in php by looking at working code that is similar and then making changes until I get the results I want. I’m fine w/ html, xml, css and such tools as Firefox inspector, ftp access, phpMyAdmin. But once we get this all set up, we need for all updating of records to be manageable w/ no more skill than your typical facebook user has.
    My current challenge is trying to create a Copy Record capability so that when a house changes hands an unskilled administrator can archive the record for the selling (leaving) owner and update only those fields that are changing for the buying (new) owner. I can do this now w/ a flag field and operating directly on the database, but want to create a menu driven capability. Seems like I should create an auxiliary plugin, but I need to look at an example.
    Any advise? help? example code? Thanks!

    https://wordpress.org/plugins/participants-database/

Viewing 1 replies (of 1 total)
  • Plugin Author xnau webdesign

    (@xnau)

    I still intend to write that tutorial, but haven’t quite found the time yet. Part of the problem is I am still developing the API and I didn’t want to put out a tutorial that might have someone develop a plugin that would break later.

    The reason I mention that is that the API for the backend is not very far along in it’s development. So even though building an auxiliary plugin is not too difficult, and the API is in place for that, the specific hooks you would need to implement the backend user interface are likely not in place yet.

    If course, it wouldn’t be too hard to do what you propose outside of the plugin API, especially of you’re familiar with the process of writing a WP plugin that adds features to the backend. Your most difficult challenge will be writing the UI.

    If you’ve got specific questions, and I offer this only becuause you’re a coder, you can email me at support@xnau.com

Viewing 1 replies (of 1 total)

The topic ‘auxiliary plugins and the Pdb_Template Class’ is closed to new replies.