Will Brownsberger

HI Antiapathy, this seems to be a post regarding the responsive-tabs-theme-for-wp theme, not the wp-issues-crm plug-in — wrong thread. But the solution would be to use a form plugin in that supports new posts and has recaptcha support, like Gravity Forms or Contact Form 7. You can put that within a tab in theme.

Good news: As of Version 4, WP Issues CRM supports fully secure connection to Gmail using OAUTH2.

Please see this link for a full explanation of how to get the most secure possible connection to GMail using OAUTH2.

Setting up OAUTH2 is intrinsically complicated. It requires you to open a developer account at Google. This may be worth the trouble in a multi-user installation of WP Issues CRM. Alternatively, you can easily connect WP Issues CRM to Google using a legacy IMAP connection. This older superseded post explains how to use WP Issues CRM with Google and a legacy IMAP connection. Please note that the superseded post was written before we upgraded WP Issues CRM to support OAUTH2.

Bottom line: If you want to use Gmail with WP Issues CRM, you have two options: (1) OAUTH2 (more work and more secure); (2) Legacy IMAP (easy and a little less secure — Gmail will call your app “less secure”).

• This reply was modified 5 years, 9 months ago by Will Brownsberger.
• This reply was modified 5 years, 9 months ago by Will Brownsberger.

Greetings.

WP Issues CRM does not have single notes field for constituents.

Instead, it has individual activity records for each activity. There is a note field on activity records. When you say “append”, it sounds like you want to create an additional activity record, which you can do in the upload process. In your upload file, you’ll need records that can match to the constituent (either an ID or just name and address), and then your activity notes. The upload will create new activity records for each constituent matched.

If you visit the WP Issues CRM support site, some of the pages and videos there should be helpful. Look especially under “Data concepts”.

Feel free to ping my email [email protected] if you want to start an offline conversation to sort this out.

• This reply was modified 5 years, 10 months ago by Will Brownsberger.

You’ve given the column a long label: ‘Yes! Nathaniel’s campaign may use my name as an endorsement’

The maximum column_name length in mysql is 64 characters. WP Issues CRM uses the label as a column name in exporting for clarity. It appends the slug ‘(custom_field_009)’ to the label, so you have about 40 characters to work with in the WP Issues CRM column label for a custom field.

Just use a shorter column label and you’ll be fine.

Not sure I understand the second question — maybe start a new thread on that.

• This reply was modified 5 years, 10 months ago by Will Brownsberger.

Further note: Versions 4.3.2.3 (releasing approx. 4/16/19) includes bullet-proofing to prevent this styling conflict.

Final resolution of this problem turned out to be that an inadvertent change by the user’s web hosting company had increased the sensitivity of security rules so that they were generating false positives and bouncing legitimate transactions.

I offered the guidance pasted below, but the issue was resolved by the webhosting company reversing their inadvertent change.

For future reference:

The error logs showed that what was happening is that a particular apache mod_security rule was triggering a false alarm and blocking the request.

ModSecurity: Access denied with code 44 (phase 2). Match of “eq 0” against “MULTIPART_UNMATCHED_BOUNDARY” required. [file “/etc/httpd/conf.d/mod_security.conf”] [line “34”] [id “xxxx”] [msg “Multipart parser detected a possible unmatched boundary.”] [hostname “XXXXXXX.com”] [uri “/wp-admin/admin-ajax.php”] [unique_id “XXXXXXXXXXXXXX”], referer: https://XXXXXXXX.com/wp-admin/admin.php?page=wp-issues-crm-main&entity=advanced_search&action=new_blank_form&id_requested=0

If you google parts of this phrase, you will see that it is not an uncommon problem with multiple applications. This security rule does trigger false positives.

The solution is to downgrade the response to this particular rule (“MULTIPART_UNMATCHED_BOUNDARY”) firing from ‘block’ to ‘log’.

In fact, the relevant mod_security documentation recognizes the possibility of false positives and suggest the solution here:

https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-%28v2.x%29#MULTIPART_UNMATCHED_BOUNDARY

Basically, the fix is to modify one line in the mod_security configuration file to set the variable MULTIPART_UNMATCHED_BOUNDARY as follows:

SecRule MULTIPART_UNMATCHED_BOUNDARY "!@eq 0" \
"phase:2,id:31,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'"

It would appear that you just want to REMOVE the word “deny” from this rule line, but check mod_security documentation.

https://support.kemptechnologies.com/hc/en-us/articles/209635223-How-to-write-a-WAF-rule-Modsecurity-Rule-Writing

• This reply was modified 5 years, 10 months ago by Will Brownsberger.
• This reply was modified 5 years, 10 months ago by Will Brownsberger.
• This reply was modified 5 years, 10 months ago by Will Brownsberger.

Mark as resolved.

Closing as resolved (mark).

Closing as resolved.

Closing as resolved.

Great. Keep me posted if I can help further.

The popup box being jammed right sounds like a plug in styling conflict. I’ve seen a styling conflict happen at least once that related to a backup plugin. Try deactivating other plugins temporarily and it should resolve (make sure you refresh and clear cache, especially Cloudflare cache if you are using Cloudflare). For my info and future bullet-proofing, please let me know which element you had to restyle.

There is an activity amount field that you can map to. As to the other fields, you want to create custom fields through the fields menu. Then you should be able to map to them.

/w.

• This reply was modified 5 years, 11 months ago by Will Brownsberger.

In absence of further inquiry, I’m marking this as resolved, but feel free to reach out if you want to pursue it further.

Yes, you just need to set the Gravity form that you are using to connect to PayPal up as an Interface in WP issues CRM.

Any entry you can do through a Gravity form to your payment system can be simultaneously synched to WP Issues CRM.

Try the “Interface” menu. For a working example, see https://votebrownsberger.com/wordpress/donate/

Please let me suggest that you do not want to create an option group for financial contributions. You should be just adding those values as possibilities to the existing activity type option group. Financial activities need to be saved and manipulated like other activities.

You can integrate WP Issues CRM with a payment processor. I recommend using Gravity Forms as a front end form generator and Stripe as a payment processor. You can then set up a WP Issues CRM interface from your form to record contributions that are made through the form.

That does not explain the error, which I would like to get to the bottom of for you anyway. The area of the software that you are you are activating has been stable for a long time, so I am not sure why you are seeing this response. It could be some kind of local condition unrelated to the software itself. To debug it I would need to see your debug log. You might also be able to get additional error data viewing your error console.

• This reply was modified 5 years, 11 months ago by Will Brownsberger.