Pods form not triggering notifications

jaycollier commented 5 years ago

Issue Overview

When posts are submitted via the front-end Pods form, notifications are not being triggered through either of these plugins:

https://wordpress.org/plugins/notification/
https://wordpress.org/plugins/bnfw/

Expected Behavior

We would expect all of these notifications to be triggered by Pods form submissions:

CPT Added
CPT Saved as Draft
CPT Published
CPT Updated

Current Behavior

Posts added via the Pods form are not triggering these notifications:

CPT Added
CPT Saved as Draft

Steps to Reproduce (for bugs)

Here’s our live example: https://www.mltn.org/jobs/submit/

This is the shortcode we used on that page:

[pods name="job" form="1" fields="post_title,job_org_name,job_post_date,job_expires_date,job_submittor_name,job_submittor_email,job_submittor_phone,job_apply_link,job_apply_email,job_description”]

We created a staging version and deactivated all plugins except for Pods, a notification plugin, and PostSMTP. We changed the theme to Twenty-Nineteen. The problem persisted

Possible Solution

In this thread — https://wordpress.org/support/topic/no-notification-for-custom-post-type-added/ — suggestions were made regarding triggers.

WordPress Environment

This is the Pods debug information from our staging site with only 3 active plugins.

WordPress Version: 5.2.1

PHP Version: 7.1.30

MySQL Version: 5.6.36

Server Software: Apache/2.4.39 (Unix) mod_hive/6.27 OpenSSL/1.0.1e-fips mod_fastcgi/2.4.6

Your User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36

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: (snip)_

WP Multisite Mode: No

WP Memory Limit: 40M

Current Memory Usage: 12.095M

Current Memory Usage (real): 14.000M

Pods Network-Wide Activated: No

Pods Install Location: /home/j(snip)/staging/5/wp-content/plugins/pods/

Pods Tableless Mode Activated: No

Pods Light Mode Activated: No

Currently Active Theme: Twenty Nineteen

Currently Active Plugins:

    • Notification: 6.0.4
    • Pods - Custom Content Types and Fields: 2.7.12
    • Post SMTP: 2.0.2

Pods Package Export (helpful!)

Workaround or Alternate Solution Until Bug is Addressed

No workaround found.

Related Issues and/or PRs

Conversation about this bug here: https://wordpress.org/support/topic/no-notification-for-custom-post-type-added/

Otherwise, no workaround found.

issue-label-bot[bot] commented 5 years ago

Issue-Label Bot is automatically applying the label Type: Bug to this issue, with a confidence of 0.93. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

sc0ttkclark commented 5 years ago

Initial review seems to indicate something is going wrong in regards to the Notifications / BNFW plugins in regards to Pods form submit handling in PodsAPI::process_form (and on down the chain to PodsAPI::save_post). Not sure yet where the exact problem lies between the plugins but it will require having those plugins activated to test.

jaycollier commented 5 years ago

While this is being resolved, we are temporarily using Formidable Forms, which natively supports custom post type creation, custom fields, and notifications. (Gravity Forms required an add-on.) Works great with Pods.

jimtrue commented 5 years ago

@jaycollier The add-on in question for Gravity Forms was WRITTEN by Pods, so I don't think that counts as a reason not to use it. Our add-on is the only one that supports editing existing posts and relationship fields. Gravity Forms supports notifications natively as well.

jaycollier commented 5 years ago

Thanks, Jim. We were already using Formidable Lite, so we upgraded to the basic paid version, which is similar in cost to Gravity Forms. We do look forward to moving back to the front-end Pods forms when the bug is fixed.

jaycollier commented 5 years ago

Disregard the following comment.

Notifications for Pod CPT drafts, publishes, and updates with the Better Notifications for WordPress plugin: https://wordpress.org/plugins/bnfw/. The comment was about the Notification – Custom Notifications and Alerts for WordPress plugin: https://wordpress.org/plugins/notification/. I will post this as a support request there.

_Hi. I have found another problem which may be related, but, if not, please recommend whether I should create a new bug report.

The original report was about receiving notifications from front-end Pods form submissions.

Now, I have set up Notification to send emails when a Pods custom post type is added, published, or updated from the editing interface. When setting up the Notification plugin, the CPT appears correctly in its dashboard, but no email is sent when any of those actions occur.

To troubleshoot, I made a duplicate staging copy and deactivated all plugins except Pods, Notification, and Post SMTP (so I could verify emails sent via its log).

Logins, logouts, and standard page and post notifications work. The triggers for the Pod CPT don't send e-mails.

Recommendations? Are others sending notifications when Pods posts are created or updated? If so, is there another method?

Thanks for your assistance. We have a growing team of editors and knowing when authors make updates to posts is critical.

-Jay_

jakubmikita commented 5 years ago

FYI regarding the Notification plugin - I'm the plugin author and we keep our eyes open for this issue. Now when we released the most important features we'll try to tackle this one.

pods-framework / pods