doublesharp

Hi, in the current version you have to select “Validated Field” as the type in the Field Group Editor, and then you can select your actual field type within the Validated Field settings. All the other settings are found under it. This isn’t ideal for a couple of reasons – copying the properties around is tricky, converting to a validated field means you have to recreate the field, etc – so in the new version the plan is to just add the controls on to the settings for other field types. I’ve had the code 80% done for 6 months and just haven’t had time to wrap it up, but hopefully soon!

Hi Uffe,

Apologies, I ended up being really busy with work and haven’t had a chance to look at this yet. My project ended last Friday though so once I catch up on random chores I’ll have more time to spend here.

Thanks for your patience,

J

You just want the pattern, without the delimiters. Are you entering the regex as \A[1-9]\d{3} ?[a-zA-Z]{2}\z? Alternatively you can use the PHP validation and do a preg_match().

I’m also using a cache, which I just cleared. It doesn’t always flush things as well as one might hope if that could be related.

Not immediately, but the upgrade was processed… fwiw I am using nginx, php-fpm, php7, and mariadb so kind of but not really standard.

This is being caused by the call to return apply_filters( 'popmake_popup_is_loadable', $loadable, $popup_id ); in includes/pum-deprecated.php. The filter function in includes/integrations/class-popmake-woocommerce-integration.php takes 4 arguments and has no defaults.

Either need to change includes/pum-deprecated.php to:

// or whatever the appropriate default values are for args 3 and 4
return apply_filters( 'popmake_popup_is_loadable', $loadable, $popup_id, array(), false );

Or change includes/integrations/class-popmake-woocommerce-integration.php to:

// or whatever the appropriate default values are for args 3 and 4
public function popup_is_loadable( $is_loadable, $popup_id, $conditions=array(), $sitewide=false ) {

This former seems like it would best make it backwards compatible.

@bdbrown, @denzel_chia This is unchanged in both the 3.0.0 and 3.0.1 zips. It’s pretty straightforward so hopefully it can make it into the next release.

Thanks!

@nikeo, I posted this in it’s own thread but to be PHP7 compatible the constructors for alx-posts.php, alx-tabs.php, and alx-video.php in the functions/widgets/ need to be rewritten from the class name to __construct(). Looks like they are still using the class name in 3.0.1.

Thanks!

Oops, misunderstood the UI here. I thought clicking the title would lead to the edit screen for the recipe, not a preview using my latest post.

This was caused by PHP-FPM not being able to write to the session directory. I am not using the default “apache” user and needed to change the ownership of the PHP session folder.

Sorry for the false alarm!

Justin

It does seem to be serving ads, but can’t find the channel(s) for reporting

I’m finally getting back to working on the new version of Validated Field, so the current production one probably won’t be changed. I will take your suggestions into consideration for version 2 though.

The code you see on the front end is show if front end validation is enabled to provide the post_ID to the validation. It is included using a hook on wp_head:

add_action( 'wp_head', array( $this, 'set_post_id_to_acf_form' ) );

You should be able to use the global $acf_vf; object to remove the action after the plugins have loaded, but before wp_head is called. If you are using it on the front end you probably want to replace this by adding it to the wp_footer hook.

Thanks!

I’ve been out of the country but getting back next week and will have a chance to look into this issue then. There is a new version that is nearing completion that should solve this problem and offer a bunch of new features. Thanks for your patience!

@kalagan – can you let me know the versions of WP, ACF, and VF you are using? I am wrapping up a new version of the plugin that is working, it’s possible that the current version broke with one of the recent updates.

Thanks!

HI @sunpublicity,

With the current version of the plugin this isn’t possible, but I have been working on a completely revamped version 2.0 that will include this as a premium add-on. As it is currently implemented you can make a field hidden or read-only based on the user’s profile. Let me know if you think there is value in making this extend to a per user model.

I’ve had some other projects take up most of my time lately but hope to have the new version out sometime in January.

Thanks!

Justin