badabingbreda

In case anyone else would ever need it, I guess there’s no harm in sharing the code used by WP All Export (set it to use ID as the value and ‘export the value returned by a php function’, then point to following functionname):

function return_abh_gravatarurl($value) {
        // get the obh_options from wp_options table
	$abh = json_decode(get_option( 'abh_options' ));
        // reset the $value so we get the abh_author{value} property
	$value = 'abh_author' . $value;
	if (property_exists($abh , $value)) {
		if (property_exists($abh->{$value}, 'abh_gravatar')) { 
			return _ABH_GRAVATAR_URL_ . $abh->{$value}->abh_gravatar;
	} 

	}
		return null;
}

• This reply was modified 4 years, 1 month ago by badabingbreda.

Hi Calin, thanks for that. There must be some reason for why it’s stored in wp_options table but I wouldn’t really have thought to look there, mainly because all users seem to have custom fields connected as well.

I’ll be able to add an export callback to my WP All Exports plugin that tries to match the userid to a corresponding named array value to fetch me the image name. So thanks for your swift help.

Hi @olbweb , I’ve been trying to figure out why this could be happening and I can’t really think why it does. The technique I use to fetch the plugin is also used a in bigger commercial plugin I developed and is used across a few hundred different sites. ACF has changed it’s way to fetch the used field groups and field names a few times so maybe you can share with me the ACF version you’re using on that version and I’ll try to find a solution.

Hi Honza, I can’t really tell from an image. I tried to replicate your result, but I got exactly the same, as expected. I also don’t quite get why there is a image_size attribute in the shortcode when you select a textarea.

Can you provide me with an url where it is live?

Hi, let me assure you that the confusion was not intentional. I was looking for a short, to the point name for my plugin and I was adding more tools and things to it along the way the name seemed fitting.
I hadn’t even made the connection to Tool*set* until I had released the first version. If you’ve ever tried releasing something, then you know that changing names at the very last minute or even after that is not a pleasant thought.

If that’s any consolation, I have planned a name change in the not so distant future that should probably take away some of that confusion.

Thanks Michael, I did as you did, created the same things but this time on a vanilla install. It worked! as expected and per my settings. But, when going forward and trying to build up to the actual dev-settings it broke again. I think I found what is going wrong:

I didn’t think it was of significance but I also have a CPT called Label; I manually put in the Labels as posts, then the releases that belong to that recordlabel are being queried on Spotify and inserted into the database as seperate CPT’s Release with a taxonomy label which gets the same slug as the calling Label.

So, I was able to simply migrate the taxonomy ‘label’ to ‘recordlabel’ and now it works as it should.

Thanks for your quick reply!