Will Brownsberger

All set. I have committed this change as Version 2.5.3.

It should momentarily propagate to your plugins page and you can update.

My recommendation would be to set up the match passes in this order:
email
phone
name

Not sure how many possible dups you may have in your database, but you always want to match by the most unique combinations first. If the matcher finds more than one record matching in a given pass, it will fail the match and not reattempt in subsequent passes.

Let me know how it goes for you. I appreciate the feedback.

Your understanding is correct — match criteria are used to determine whether to add new or update. The matcher works down the match list trying the match combinations in order.

We didn’t make phone one of the options for matching, but there is no reason we can’t. I can make this addition within a couple of days.

I can make phone a match option alone or in combination with any standard field. I can’t make make phone in combination with a custom field an option. In other words, I can try to match by phone and then by a custom field, but I can’t combine phone and a custom field in a single match pass — I don’t think that’s what you wanted, but I just wanted to confirm.

Just confirm your need a little further and then give me a day or two to turnover a minor release. My thought would be to add fn/phone and phone as two new match options.

Greetings. Thanks for posting the question.

There are no known bugs in that function and it is working fine in other installations.

However, it does sound like a javascript error is crashing the page.

Diagnostics to try:

1. Possibly this is a plug in conflict. Try disabling all other plugins that might use javascript or jquery and then return to the page (via the menu, so you are getting a fresh copy). This shouldn’t happen because the key functions are all in a self-executing anonymous namespace.
2. A less likely possibility is that you have an old copy of the javascript that supports the page. Do a shift-refresh to make sure you are not carrying an older incompatible copy of the javascript module that supports the page — since you tried multiple browsers, that is not likely.
3. To see what javascript is complaining about, right click some place on the page and do an “inspect element”. Then, click on the console tab. Leave the console tab open and navigate to and from the upload map. If there is a javascript error occurring when the page is loaded it should show on the console and I would very much like to know what you are seeing.
4. I’m assuming that you are talking about the drag and drop interface for mapping fields in the upload process. Also, I’m assuming you are using it as intended — attempting to drag fields from the right hand column headed “Upload fields to be mapped”.

Eager to hear the result of your further experiments. If there is a plug-in compatibility issue, I should be able to bulletproof to avoid it.

Note: This issue should not be sensitive to browser choice (unless you were using something really ancient, which you clearly aren’t).

The major data constructs in WP Issues CRM are as follows:

-Constituents (possibly classified by custom fields)
-Issues (posts tagged or categorized)
-Activities (which belong to a constituent and pertain to an issue). (Comments are really a special kind of activity, although they have their own data table in WordPress. We associate comments with constituents through the email address recorded with the comment record.)

If you want to associate constituents with an issue, they need to have an activity with respect to the issue — e.g., send an email about the issue. You can create custom activity types, through the Options submenu if you want to link issues and constituents without an activity like email. You could define an activity “Has an interest in.”

If you view an issue, you’ll see all constituents with activities associated with the issue. And conversely viewing a constituent shows all activities by the constituent.

If you just want to classify constituents, then you can add custom fields and options for those fields through the Fields and Options submenus.

I think you’ll be able to do what you want to do. I wouldn’t use tags — that will be very hard to keep organized.

It works with the favorites/assigned lists on the main menu (the buttons with the stars)

Open issues or constituents that are past their review dates are highlighted with a red border in the favorite issues and favorite constituent lists. These appear on the main menu as star-smile — *;) — and star-paper (sorry, can’t get the dashicons into this comment).

You can set review dates for constituents or for issues. It makes most sense to set a review date for issues/constituents that are assigned to a person. Assign them to yourself if you want them to appear on your favorites list. Open issues/constituents are highlighted with colors based on review dates. Closed issues/constituents don’t show on the list. Issues/constituents that are neither open or closed have a neutral border regardless of review date.

Make sense?

You can also use review date in the basic searches and in the advanced search (double magnifying glass on the main menu).

Yes! Exactly.

Open issues or constituents that are past their review dates are highlighted with a red border in the favorite issues and favorite constituent lists. These appear on the main menu as star-smile — *;) — and star-paper (sorry, can’t get the dashicons into this comment).

You can set review dates for constituents or for issues. It makes most sense to set a review date for issues/constituents that are assigned to a person. Assign them to yourself if you want them to appear on your favorites list. Open issues/constituents are highlighted with colors based on review dates. Closed issues/constituents don’t show on the list. Issues/constituents that are neither open or closed have a neutral border regardless of review date.

Make sense?

You can also use review date in the basic searches and in the advanced search (double magnifying glass on the main menu).

Thanks for the review! Let know if you see things you’d like improved.

You could, instead use the Responsive Tabs theme — completely unrelated, which offers front page tabs and a rich approach to presenting content:

See it here: https://www.ads-software.com/themes/responsive-tabs/

Berger.bpb is not related to me — just the data manager in another state house office.

You can disregard this warning in part. If you have WP 4.4, you definitely want Responsive Tabs 2.25. However, Responsive Tabs 2.25 will work with WP 4.3 — not originally tested for this version, but not incompatible.

Disregard this warning. We did not originally test our comment scroll changes with the current version, anticipating the upgrade, but they do work.

That’s 2.4.1, not 4.2.1 for the version number in the post above.

Hi PatM2G,

Thank you for identifying this bug.

I have fixed this immediately in version 4.2.1 (now live). You can upgrade immediately through the normal plugin update process and should see the change in Dashboard access for the Constituent Manager role immediately.

Please be aware that in order for the Constituent Manager role to have any access to WP Issues CRM the setting in Dashboard > WP Issues CRM > Settings > Security > WP Issues CRM has to be "Only Constituent Managers and Administrators". Unless this is enabled, the Constituent Manager role will not see WP Issues CRM on the dashboard.

Note also that, even if so enabled, the Constituent Manager role has no privileges to administer WP Issues CRM — i.e., it cannot access WP Issues CRM Settings, Fields, Options, Uploads or Manage Storage. It can only access the daily WP Issues CRM functions and set user preferences.

Please ping me directly at [email protected] if you have any difficulty at all with the plugin. We want this to work well for everyone.

Thanks again for letting me know.

Sorry this took so long. However, it is fully fixed in Responsive Tabs, versions 2.23 and above. The fix was to use the site_url() function in the lines that you located correctly (and also in a few other places — breadcrumbs and login links). I should have figured that out in the beginning.

This is all set. Sorry it took a while to fix this. It is now done automatically in Responsive Tabs version 2.23 and above.