David Baumwald

@brianbrown Sorry to hear that it’s not working for you. I am supporting this though. If you’d like to submit a support request with the exact issue you’re having, I’d be happy to take a look.

@bvhprods It’s not a bug, and this was done for accessibility in WP Core. See Track ticket 50105 for context.

@rodgersnigel Good point. I like to encourage more recent versions, but there’s no technical requirement here to diverge from what WP Core itself supports. I’ve lowered the PHP requirement to 7.0.

@alanfuller Thanks! This was originally set to land in 5.7, but was reverted. It did finally land in 5.8. I’ve updated the plugin to reflect that.

Hello @adrianspk! What I think would be best is to directly filter the field output after the generic output is compiled. The “User” field type has three output value types: array, object, or ID. Looks like you’re using the default of array. Using apply_filters( 'de/acfpoftao/format_post_title', $title, $post, $field, $post_id ) will work like this…

function de_filter_post_object_add_on_output( $title, $post ) {
		$append_field = get_option( 'de_acfpoftao_append_field' );
		$user         = get_field( $append_field, absint( $post->ID ) );	

		if ( ! $user || empty( $append_field_value ) ) {
			return $title;
		}

		$append_field_value = $user['display_name'];
		
		$format = apply_filters( 'de/acfpoftao/append_field_data_format', get_option( 'de_acfpoftao_append_field_format' ) );

		switch ( true ) {
			case preg_match( "/^separator::(.*)/", $format, $matches ):
				$title .= ' &' . $matches[1] . '; ' . $append_field_value;
				break;
			case preg_match( "/^wrap::(.*)/", $format, $matches ):
				$title .= ' &l' . $matches[1] . ';' . $append_field_value . '&r' . $matches[1] . ';';
				break;
			default:
				$title .= ' (' . $append_field_value .  ')';
				break;
		}

		return $title;
	}

	add_filter( 'de/acfpoftao/format_post_title', 'de_filter_post_object_add_on_output', 10, 2 );

Note: I’ve not tested this code, but in theory it should work.

• This reply was modified 3 years, 9 months ago by David Baumwald.
• This reply was modified 3 years, 9 months ago by David Baumwald.

Thanks for the ticket! The plugin has ben rewritten, and this error was resolved along the way. Please open another ticket if you have any other issues after updating to the latest version.

Looks like this is an error related to your theme “luzuk”. If you find an issue directly related to this plugin, feel free to open another ticket. =)

Looks like this was actually an issue with WooCommerce. If you find an issue that directly relates to this plugin, feel free to open another ticket.

@cyberchicken Is correct. There’s currently no settings available in the plugin.

Sorry for the issue you’re having, but this is completely unrelated to this plugin. The error states that there’s no more space left on the drive to write session data. You’ll have to consult with you host or a developer.

Excellent suggestions! I’ll definitely update the regex to reference the end of the filename to prevent more false positives.

I’ll also look at using the $_wp_additional_image_sizes global to filter only known-WordPress generated thumbs.

@dmje

Yes, this works on any post type. In general, it works on any screen you’re using a “Post Object” ACF.

@nathaningram Sorry about that and the delay. I’ve resolved the error. Please let me know if you have any other trouble.

It can be used as a mu plugin, but I wouldn’t recommend that. The plugin hooks into Updraft, so it wouldn’t function properly due to loading order.

If you want to ensure users don’t see or deactivate it, just try hiding the plugin from the list of plugins.

• This reply was modified 6 years, 10 months ago by David Baumwald.