traveler

This adjustment seems to have fixed the above errros:

<?php
// ADDS META BOX TO 'CLOSET' SCREEN SHOWING OUTFITS CREATED FOR THIS CLIENT

// ADDS FONT AWESOME TO 'CLOSET' ADMIN SCREEN
function queue_scripts_to_closet() {
   wp_enqueue_style( 'le-font-awesome-css', 'https://pro.fontawesome.com/releases/v5.10.0/css/all.css' );
}
add_action('admin_enqueue_scripts', 'queue_scripts_to_closet');

// CREATE THE META BOX
function le_outfit_loop_meta_box() {
    $screens = ['closet'];
    foreach ($screens as $screen) {
        add_meta_box(
            'outfit-loop-meta-wrapper',      // Unique ID
            'Outfit History',                // Box title
            'le_outfit_loop_html',           // Content callback function, must be of type callable
            $screen,
            'side'
        );
    }
}
add_action('add_meta_boxes_closet', 'le_outfit_loop_meta_box');

// HTML TO RENDER THE META BOX
function le_outfit_loop_html($post) {
   
   global $post;
   $tempPostVar = $post;
   $editScreenId = $post->ID;
   $clientTaxTerm = $post->post_title;
   echo "<h4>" . $clientTaxTerm . "'s Outfits:</h4>";
   ?>
   
   <div class="admin-button-wrapper">
      <a href="/wp-admin/post-new.php?post_type=outfit" 
         id="js-create-outfit-btn" 
         class="btn">
         <i class="fas fa-plus-circle">&nbsp;</i>
         Create New Outfit
      </a>
   </div>

   <?php
   $outfitLoopArgs = array( 
      'post_type' => 'outfit',
      'tax_query' => array(
         array(
            'taxonomy'  => 'client',
            'field'     => 'slug',
            'terms'     => $clientTaxTerm, // should equal the closet post title
         ),
      ),
   ); 

   $outfits = get_posts( $outfitLoopArgs ); 
	if ($outfits) : ?>
      <ol>
      <?php
      foreach ($outfits as $outfit): setup_postdata( $outfit );
         ?>
         <li>
            <a target="_blank" href="<?php echo get_edit_post_link($outfit->ID); ?>"><?php echo $outfit->post_title; ?></a>
         </li>
         <?php
      endforeach;
      // wp_reset_postdata();
      $post = $tempPostVar;
      ?>
      </ol>
      <?php
   endif;
}

Thanks.

Update, I changed a lot around, now I have it working almost. The only issue is the fields that have spaces are being sent as strings but returned as arrays so only the first word of that string shows without adjusting for the return array value in the page template. I imagine this has to do with me not using register_rest_route()?

Here is my jquery:

updateProfile() {

        this.title = this.firstName.val() + ' ' + this.lastName.val();
        this.slug = this.firstName.val() + ' - ' + this.lastName.val();
        this.firstName = this.firstName.val();
        this.lastName = this.lastName.val();
        this.email = this.email.val();
        this.cellPhone = this.cellPhone.val();
        this.homePhone = this.homePhone.val();
        this.officePhone = this.officePhone.val();
        this.homeAddress = this.homeAddress.val();
        this.city = this.city.val();
        this.state = this.state.val();
        this.zipCode = this.zipCode.val();
        this.gender = this.gender.val();
        this.dateOfBirth = this.dateOfBirth.val();
        this.rolodexId = this.rolodexId.val();
        this.staffId = this.staffId.val();
        this.department = this.department.val();
        this.jobTitle = this.jobTitle.val();
        this.supervisorsFirstName = this.supervisorsFirstName.val();
        this.supervisorsLastName = this.supervisorsLastName.val();
        this.userProfileIntro = this.userProfileIntro.val();

        $.ajax({
            beforeSend: (xhr) => {
                xhr.setRequestHeader('X-WP-Nonce', leadershipData.nonce);
            },
            url: leadershipData.root_url + '/wp-json/wp/v2/profiles/' + this.profileWrapper.data('id'),
            type: 'PUT',
            data: {
                title: this.title,
                slug: this.slug,
                meta: {
                    first_name: this.firstName,
                    last_name: this.lastName,
                    email_address: this.email,
                    cell_phone: this.cellPhone,
                    home_phone: this.homePhone,
                    office_phone: this.officePhone,
                    home_address: this.homeAddress,
                    city: this.city,
                    state: this.state,
                    zip_code: this.zipCode,
                    gender: this.gender,
                    date_of_birth: this.dateOfBirth,
                    rolodex_id: this.rolodexId,
                    staff_id: this.staffId,
                    department: this.department,
                    job_title: this.jobTitle,
                    supervisors_first_name: this.supervisorsFirstName,
                    supervisors_last_name: this.supervisorsLastName,
                    user_profile_page_intro: this.userProfileIntro
                }
                
            },
            success: (response) => {
                this.makeProfileReadOnly(this.inputFields);
                console.log('Congrats a success!');
                console.log(response);
            },
            error: (response) => {
                console.log('No Sorry');
                console.log(response); 
            }
        });
    }

I have my PHP custom fields registered in this format:

register_meta('post', 'first_name', [
		'object_subtype'	=> 'profile',
        'show_in_rest'		=> true,
        'type'              => 'string',
	]);
	register_meta('post', 'last_name', [
		'object_subtype'	=> 'profile',
        'show_in_rest'		=> true,
        'type'              => 'string'
	]);
	register_meta('post', 'email_address', [
		'object_subtype'	=> 'profile',
        'show_in_rest'		=> true,
        'type'              => 'string'
	]);

Using 'type' => 'string' did not function as I thought, which was that it would force that value to be a string.

What is the next step to look into so that my input fields and text fields with multiple words within them aren’t converted to arrays before being sent back to the page?

Ok, I was under the impression these routes were automatically generated when you “show in rest” for the CPT. Here’s how I’ve created these:

<?php

// second param is function name creating the routes
add_action('rest_api_init', 'eventRestRoute');

function eventRestRoute() {

    // first two args can be whatever
    register_rest_route('seiu-events/v1', 'seiuEventsRest', array(
        'methods'   =>  'POST',
        'callback'  =>  'createEvent'
    ));
    register_rest_route('seiu-events/v1', 'seiuEventsRest', array(
        'methods'   =>  'DELETE',
        'callback'  =>  'deleteEvent'
    ));
    register_rest_route('seiu-events/v1', 'seiuEventsRest', array(
        'methods'   =>  'PUT',
        'callback'  =>  'editEvent'
    ));
}

// create new event post
function createEvent() {

    // create the event post
    wp_insert_post(array(
        'post_type'     =>  'events',
        'post_status'   =>  'publish',
        'post_title'    =>  'Rest Post',
        'post_content'  =>  'This is an amazing post.'
    ));
}

At this point I’m not attempting to capture any of the json data sent but just create a new Events post titled “Rest Post” to make sure I’m going in the correct direction.

When I use Postman to make a POST request to example.com/wp-json/wp/v2/events, I get this error:

{
    "code": "rest_cannot_create",
    "message": "Sorry, you are not allowed to create posts as this user.",
    "data": {
        "status": 401
    }
}

Reading up on the REST API documentation I see that the cookie authentication that uses nonce only works for using the REST API from within wordpress. My calls are coming from outside of WordPress. What is the workaround for this, assuming my code above should allow a simple post to be created just by sending data to my custom route?

Last, am I wrong to assume I do not need to be using Ajax for this, since the request is not originating in a browser but instead from an outside system?

So I’ve been reading as much as possible on this, going over tuts, but most all that I’ve seen talks about using the rest api to query it’s own database, meaning in my theme I query my site’s database to fetch data and create posts from it. In all these, there is a javascript trigger that starts it.

I’m now confused now though, about what triggers making/creating a post when JSON data is sent to an endpoint?

I’ve created and deleted cpt’s using wp_insert_post() that creates a post with a title that matches an ID number attached to the end of a URL. In this case, if that ID exists, then I use ajax to send that ID to PHP and call a PHP function that then uses wp_insert_post() to create the post. To delete it, I use the same ID as a meta_value to query the correct post and then use wp_delete_post() to delete it. This is a very simple tracking mechanism to see who goes to a signup form and then doesn’t complete it.

So what am I missing here, I have a small JSON object that will be sent to my route,
example.info/wp-json/wp/v2/events
and my JSON that will be sent is:

{
    "eventID": 16924,
    "regions": "R1, R2, R3",
    "type": "Rally",
    "eventName": "Test Event Name",
    "eventLocation": "Test Location",
    "eventStartDate": "2/29/2020",
    "eventStartTime": "12:00",
    "eventStartAMPM": "pm",
    "eventEndTime": "2:00",
    "eventEndAMPM": "pm",
    "staffResponsible": "Staffname1",
    "notes": "",
    "counties": "Los Angeles, San Bernardino",
    "dept": "Information Technology"
}

So what will trigger my function to create a post from this?