Support

Account

Forum Replies Created

  • Hi All, thanks for the great info.

    I’m making a real estate website, where each property has a price that needs to be entered in the back end by the client.

    I’ve fixed the comma (thousands separator) issue on the front end display with the above snippet.

    But when using a number field (as discussed here) the client cannot use any commas when they are entering the property price, which goes against how we’ve been taught to write numbers — 1,345,000 must be entered into the ACF number field as 1345000 which doesn’t make sense to the average person.

    I know that I could create a text field instead, where a client could use commas (thousands separator), but then I’m having trouble sorting by price when that field is not a number.

    Wondering why the number field doesn’t allow for comma (or other thousands separator)?

  • Solution:

    Note that there’s an IF and an ENDIF which need to be wrapped around the ACF fields.

    Also note that the default WP the_content() code must remain in place — even if you’re not using it for content in your template.

    
    <div class="entry-content clearfix">
    
    <!-- HIDES ACF FIELDS for use with WP password protect feature -->
    <?php if( !post_password_required( $post )): ?>
    
    	<h2><?php the_field( 'business_name' ); ?></h2>
    
    	<p><?php the_field( 'client_name' ); ?></p>
    
    	<p><small><?php the_field( 'date' ); ?></small></p>
    
    	<h1><?php the_field( 'introduction_title' ); ?></h1>
    
    	<p><?php the_field( 'introduction_text' ); ?></p>
    
    <!-- ENDS HIDE ACF FIELDS with WP Password Protect -->
    <?php endif; ?>
    
    <?php the_content(); ?>
    
    </div><!-- .entry-content -->
    
    
Viewing 2 posts - 1 through 2 (of 2 total)