Alex Cicovic

Hi @mpsteel,

Thank you for your suggestion and sorry for the delayed response.

Are you aware that the plugin already updates metadata (using the https://api.parsely.com/v2/metadata/posts API endpoint) whenever a post is created or updated?

If your use-case is different from the above, can you describe it so we can be aware of it?

Thank you.

Hi @elanasparkle, thanks for getting back to me.

The version which was working “correctly for me” was 1.2.2 (yes, that old). However, the caveat is that the dev who had initially undertaken the project had modified the plugin’s code and had disabled its auto updates (yuck!) in order to avoid breakages. So, this functionality may have been one of the modifications he had made.

The way I found to solve my problem is to introduce a weforms_email_headers filter in line 122 of class-notification.php like so: $headers = apply_filters( 'weforms_email_headers', $headers );. This allows me to grab the header and to convert the BCC item to the correct email address that is needed in each case.

The obvious downside to this is that I (or someone else) will have to tinker class-notification.php by adding this line every time the plugin gets updated. I would prefer not to have to do this, so I wanted to ask if you think the team would be open to accept this as a PR. It’s just a one-liner, simple and clean.

Thank you!

Hello there,

I’m sorry for re-posting here and I don’t mean to put pressure on anyone. Unfortunately this is a problem for us so I wanted to re-launch this in case it can be looked into.

Thank you very much!

Hello there,

Setting position to inherit works for me without any bad side effects, so I’m marking this as resolved.

Thank you!

Hello @elanasparkle, thanks for the feedback.

Can’t really share a URL since I’m still testing this in local. Once I upload this for the client it will be a fixed version (I hope!) so this isn’t good either. The theme I’m using is Avada. I could probably upload a testbed somewhere, but I would need some days to do this, and I wouldn’t like to post a URL publicly. Let me know if this interests you.

Concerning the CSS fix, I had no time to investigate further but I’ll certainly play more with my finding and what you suggested to see what’s a better fit for my scenario.

Thanks!

Removing position: relative; from ul.wpuf-form .wpuf-el { ... } in frontend-forms.css fixes it for me, although I haven’t tested it enough yet to see if it has any undesirable side-effects.

Hi Ben,

Thanks for coming back to me. I’ve found another plugin that works for me, though I haven’t examined its source code.

So no need to send me anything.

Thank you very much.

For those who face the same problem, this thread might be of interest: https://www.ads-software.com/support/topic/doesnt-work-on-categories-and-filters/

Thank you very much, this works. If I see any problems I’ll let you know.

Thanks!

@benrich I would be interested to see what you’ve done, although I understand if you don’t want to ??

@adamrj01 thanks for the feedback.

I haven’t done anything in particular, but haven’t re-received the error so far.

@adamrj01 have you figured out if this actually stops the client’s payment flow or if it’s just a warning that has no effect on client experience?

@adamrj01 thanks.

@adamrj01 can you post the thread URL?

I get the same warning for BACS as @sanzal.