rgreenstreet

Yep, looks like the API is back. I’m inclined to believe the issue was with PDF.Ninja rather than this plugin. Marking as resolved for at least my thread.

I have tried uploading a completely different PDF to the form, duplicating the CF7 form, and even re-creating the CF7 form from scratch to try to remedy this.

Your PDF form does not have any form fields entered into it.

You can use a site like pdfescape.com to add fields to the PDF file

Thanks for the input! I understand what you mean about it being an edge case. You da bomb, man.

Thanks for your input! I’ll try that and mark this as resolved for the time being.

Update:

Tentative fix:

On a whim I decided to go over to the page that the CF7 form is on and re-save it (even though all changes were made on the form, not the page), and it seems to be working now.

Dunno if this is a permanent fix and I just have to do this step moving forward, or if there’s something I can change to not have to perform this step.

Any insight, Jules?

Additional information:

It’s the group tag as well as the content that is showing in the email, not just the content

So we’re getting the full [group1] this is the content [/group1]

Rather than just “This is the content”

We don’t have the payPal+Stripe Plugin, however we do have two Stripe addons for Gravity forms (which we don’t really use) so maybe that explains what I found:

For some reason the theme didn’t have the “wp_head()” and “wp_footer()” functions in the header/footer PHP files.

I added that in, and it seems to be working now, for the test cases I submitted for different conditional groups.

I’ll have to find a way to tell my boss I experimented with the theme (albeit in what seems to be an innocuous and even necessary way), and check with the theme developer for why those weren’t included.

For now, I’ll mark this one as resolved and open a new one if it pops up again.

Thanks a bunch!

Update: Added another group of

[trendgraphix]

That’s doing the same thing as the “onlysendoffice” group was at first, showing on everything even when the condition is not met

I initialized the group with the space between the opening and closing tag, just in case, but no dice.

I have commented it out of the email for the time being, it’s not a big deal to manually add it before forwarding it where it needs to go

Could this just be a case of too many conditional groups, and there isn’t enough time between clicking the “Send” button and when the Postmaster SMTP service sends it to process them all?

• This reply was modified 5 years, 6 months ago by rgreenstreet. Reason: Added a hypothesis to the bottom

Copied from the list of mail tags on the “Mail” tab of CF7 for this form

[adminhaseedge]
[doesadminhavewolfnet]
[showform]
[isexpansionapp]
[isexpansioneedge]
[isadminwitheedge]
[isregular]
[isadmin]
[isexpansion]
[ishidden]
[ismcstaff]
[isreturning]
[istransfer]
[toolkitcma]
[mlms]
[l2l]
[reprophet]
[onlysendoffice]

I really appreciate your attention with this!

That works to have it not show when it’s not supposed to

However now it won’t show when it is supposed to :-/

The odd thing is that there were already 10 or so groups that were set up without the space between the open/close that were working just fine.

I went ahead and added spaces to all of those groups, though, just in case.

• This reply was modified 5 years, 6 months ago by rgreenstreet. Reason: formatting

Going on what Jules said:

It’s not possible to say “if this is selected, then show make this field required”

You would need to use the workaround to say “if this is selected, show the required field” and then “if the other option is selected, show the ‘same’ field, but it’s not required”

Like he said, they would need to have different names/variables

• This reply was modified 5 years, 6 months ago by rgreenstreet. Reason: removed unnecessary word

My best recommendation would be to ensure that you copied and pasted the values from the radio button element exactly in the conditional rules.

Would you share the rules also?

Neil, nothing has changed with our email service or the recipient, or our themes/plugins.

On Friday, 5/17/2019, this form would successfully send the message to this address:

loop-SLMIDXAgreements-RosevilleMN427-10e02b29-abed-42cf-8752-c3e76e20e85fz94049701@upload.dotloop.com

Beginning yesterday, 5/20/2019, it would not send to that address

No plugins were updated, wordpress had not been updated, the theme had not been updated, nothing had been changed between 5/17 and 5/20

Other forms, sending to other addresses, work fine.

The issue, I’m guessing, is with the long, specific address used by Dotloop.com to send PDF attachments into a specific folder.

Since this is not a “real” email address with an account, login, inbox, etc. I’m assuming that the form/mail service is “pinging” the “upload.dotloop.com” server to see whether this address exists, and it’s not getting an “affirmative” message, which causes the message just to not be sent at all.

I would very much appreciate the option to just go ahead and **send it anyway**, even if the address “doesn’t exist”.

I would rather receive a bounceback message (which would not happen in this case) than not have the message sent at all.

We cannot use any other address for this, unfortunately

My forms aren’t sending either because of an error “address must be valid and of type string” even though it has sent to this address dozens of times previously. Nothing at all has changed. I did post my own topic just for good measure