Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GF entry verification against existing Pods object #124

Open
2 tasks
Dianei opened this issue Oct 16, 2018 · 2 comments
Open
2 tasks

Add GF entry verification against existing Pods object #124

Dianei opened this issue Oct 16, 2018 · 2 comments

Comments

@Dianei
Copy link

Dianei commented Oct 16, 2018

Issue Overview

GF entry verification against existing Pods object.

Expected Behavior

Add an option to select entry verification

  • Verify whether a Gravity Form entry is duplicating an existing Pods entry, based on selectable criteria/fields. (Ex. if fields: "staff_name" and "date_of_birth" match)

  • If yes, provide a message to the user with a link to the potential match, asking if the user to would like to continue (Y/N option).
    If no, create the Pods object as usual

  • If the user chooses YES, provide a notification option to be able to flag this entry as a potential duplicate to admin.

Current Behavior

Currently if a user enters a new object that is the same as an existing object, the form processes and creates a new Pods object. The admin must then manually delete the newly created object.

Possible Solution

No idea, but wonder if there might be a nifty code someone may have used in the past as a work-around. I would want to make this available for several forms/Pods on my site.

Steps to Reproduce (for bugs)

Form Upload

``` Upload Gravity Form JSON or Copy and Paste it Here. ```

Pods Package Export

``` Copy and Paste the JSON Export from Pods Migrate: Packages, Export and Paste it Here ```

Related Issues and/or PRs

Todos

  • Tests
  • Documentation

WordPress Environment

``` Debug Information

WordPress Version: 4.9.8

PHP Version: 7.1.22

MySQL Version: 5.6.40

Server Software: Apache

Your User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0 Safari/605.1.15

Session Save Path: /tmp

Session Save Path Exists: Yes

Session Save Path Writeable: Yes

Session Max Lifetime: 1440

Opcode Cache:

Apc: No
Memcached: No
OPcache: Yes
Redis: No
Object Cache:

APC: No
APCu: No
Memcache: No
Memcached: Yes
Redis: No
WPDB Prefix: wp_

WP Multisite Mode: No

WP Memory Limit: 128M

Pods Network-Wide Activated: No

Pods Install Location: /home/adoptare/public_html/wp-content/plugins/pods/

Pods Tableless Mode Activated: No

Pods Light Mode Activated: No

Currently Active Theme: Twenty Eleven

Currently Active Plugins:

Akismet Anti-Spam: 4.0.8
bbPress: 2.5.14
BuddyPress: 3.2.0
Collapse-O-Matic: 1.7.9
GP Conditional Logic Dates: 1.0.5
Gravity Forms: 2.3.4
Gravity Forms + Custom Post Types: 3.1.13
Gravity Perks: 2.0.11
Jetpack by WordPress.com: 6.5
Pods - Custom Content Types and Fields: 2.7.9
Pods Gravity Forms Add-On: 1.4 Beta
SG Optimizer: 4.0.7
WP-Members: 3.2.4.2
WP DataTable: 0.2.5
WP GDPR Compliance: 1.4.2

</details>
@sc0ttkclark sc0ttkclark added this to the Future milestone Oct 16, 2018
@brunomac
Copy link

+1

@martinderm
Copy link

A special case of this feature request is when the feed is used to pre populate form-fields but the intention is not to create a now pod at all, but to have a smarter form.

This is currently not possible.

@sc0ttkclark sc0ttkclark modified the milestones: Future, 1.5 Oct 18, 2021
@sc0ttkclark sc0ttkclark modified the milestones: 1.5, 2.0 Nov 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants