good day dear Apachefriends,
I have been working on a custom feature for WP Job Manager
aimed: adding extra featurs and options to modify via filters, the content that is displayed.
story: I've read many of the tutorials on http://www.wpjobmanager.com/documentation.
I'm trying to recreate a extra feature from the Resumes add-on (demo here) where you can add additional education or experience fields. I am trying to recreate that feature in the main WP Job Manager plugin to populate an optional subfield for addresses. I added some extra- fields and subfields to the form (there is a separate template file that renders the form).
some musings bout the db-structure of the wp-job-manager:
i have learned that every job, resume, alert, or other special WP Job Manager Feature is just a Custom Post Type (CPT). They are stored inside the wp_posts table of the database. the question is: how is a single job listing for example stored: Is there only one line per one table or how is this going to happen? this makes me wonder: The core data and the core data - fields for each listing, resume, alert, or other WP Job Manager feature is stored as a single row in the wp_posts table. So we can say that each piece of meta-data (e.g. Company Name) is being stored as its own row in the so called wp_postmeta - db-field;
The so called terms/taxonomies are a bit more complicated — if one really want to dig in, this page might be helpful:
https://codex.wordpress.org/Database_Description :: It may not explicitly mention custom post types, but they’re just posts, with the post_type set to something other than post.
so far so good - at the moment i am trying to find a path through the whole structue of the data-handling of wp - job - manager
for me the question is: how to create and add extra featurs and options to modify the content of wp-job manager