LindsayMac

Updating this issue:
I have found the cause of this error.

If you have a class that extends the WP_REST_Post_Controller for your custom endpoints, you may have redefined the __construct method without calling the parent::__construct, that will replace the construction of the class with your new controller, but the instantiation of the WP_REST_Post_Meta_Fields controller happens within the construct of the parent WP_REST_Post_Controller and is never set.

To fix this problem:

call on the parent::__construct($post_type) from within your custom class’ __construct method

–OR–

do not override the constructor at all.

I have also encountered this same error upon updating a heavily customized WP install. It seems, actually, that endpoints that set the post_type as anything other than ‘post’ work fine, but if you hit an endpoint where the post_type is set to ‘post’ it throws this error.

**this is also on a Multisite Install

I am using a custom endpoint that looks like this:
?site=subsitename&post_type=post&posts_per_page=10&paged=0&return_args=limit

Attribution would be appreciated ?? If you get the git situation sorted I can just fork and do a pull request

NEVERMIND I decided I was being stupid and i should just test the “delete” button and it works just fine!!! Completely forgot the reason why I made dev copies of sites is so i can potentially break them testing.

@nhanco – go to WordPress Social Login USERS tab and when you hover over the user name you are given an option to DELETE. That will remove the user from the “social networks” list but not delete the user overall.

I am not certain if you can only do this for the user overall or if you can do it per-connected account (meaning if they link FB and Twitter and you only wanted to delete twitter)

+1 for this! No idea how to achieve this but I need to unlink my social profile without deleting the user. I see that there is a WPSL DELETE button but worried about clicking it and deleting my user. Its not very clear

Its just simply a matter of taking the code I wrote and tweaking the query for the category terms to include empty categories AND second level categories

It was not coded to include sub categories (mostly because from a visual UI standpoint, it could get messy looking)

I’m sorry I am confused. I clicked your link and see tabs with categories working just fine.

I submitted a pull request that includes categories. You can take the code here

It has yet to be rolled into the plugin’s core, so be aware that updating will overwrite those changes.

Caleb – believe I forked your repo and submitted a pull request on git. If i didn’t remidn me

So i MIGHT be able to work this out if I had more brain power on this Friday night, but I dont… So i’m going to post it here

Basically we need to run a foreach on $group (i think) on the $result variable.. So foreach group, run the createCampaign function.. That is my guess. I havent gotten into testing and coding yet though

// Set the content variables
	$content[$htmlContentTag] = $postContent;

	// Segmentation, if any (Interest groups)
	$segment_opts = NULL;
	if ( 0 != strcmp( $interestGroupName, WP88_ANY ) )
	{
		$group = $api->listInterestGroupings( $listID );
		if ( NULL != $group )
		{
			$interestID = $group[0]['id'];
			$conditions = array();
			$conditions[] = array('field'=>"interests-$interestID", 'op'=>'all', 'value'=>$interestGroupName);
			$segment_opts = array('match'=>'all', 'conditions'=>$conditions);
		}
	}

	// More info here:  https://apidocs.mailchimp.com/api/1.3/campaigncreate.func.php
	$result = $api->campaignCreate( 'regular', $options, $content, $segment_opts );

I have noticed the same thing as well…

I have a few groups based on my WP Categories and then I have one group called “ALL CATEGORIES” so basically a post will always be in TWO different MailChimp segments / groups… therefore the “all” segment is not ever getting any emails.

OOPS NEVERMIND!! I had some code in my functions.php file that was conflicting with it and thus breaking anything prestashop related.

So no worries. it now works! YAY!

Thanks Aytechnet. It’s not a major conflict because I was able to update it myself without a problem

I do, however, have another issue that has cropped up. I have the shopping cart in my header and it seems that the cookie is not passing when I go to the wordpress side of my site, so my cart shows empty while I am browsing there, but not while I am in the store.

Babbsela, please look at the screen shot. This is an issue with the ADMIN SCREEN and how they are displaying in the META BOX. the theme has no bearing on this issue.