bradshawtm
Forum Replies Created
-
Note that this is the support forum for Jetpack CRM; if you are having issues with the WooCommerce Subscriptions plugin you will need to contact their support:
It appears you emailed us in our paid support queue, so I replied there before I saw this message.
For others who may see this, it is a known issue, and the only workaround at the moment is to directly manipulate the data in the database, which of course is outside the scope of support. We do have it logged internally, but it hasn’t been the highest priority, so we don’t have an ETA for it.
I wasn’t able to reproduce the issue on my end and we haven’t had any similar reports to date. Can you provide any relevant PHP logs that come up when this happens? Please ensure you don’t send any confidential information.
Also, what PHP version (e.g. 5.x, 7.x, 8.x) and web server (e.g. nginx, Apache) are you using?
Ah, that’ll do it as well!
We’ll go ahead and close this thread for now, but do feel free to open a new thread should you have further questions!
As to the blank page your contacts reach:
- Are they prompted to log in first, or is this before they log in?
- Can you get to the Client Portal pages (login page + others)?
- Does the WP menu show on the blank page?
- Are there any PHP error logs?
I would recommend testing with all other plugins disabled to rule out plugin conflicts as well. Let us know what you turn up!
You can only send email to one contact at a time via the free plugin. If you’d like to send to more than one contact, we recommend using one of these options:
- Export contacts to MailPoet via the included MailPoet Sync module: https://kb.jetpackcrm.com/knowledge-base/export-crm-contact-segments-to-a-mailpoet-subscriber-list/
- Use our paid Mail Campaigns extension: https://jetpackcrm.com/mail-campaigns/
I apologize for the confusion on our end; while contacts can update their information via the Client Portal after logging in and going to “Your Details”, your team members cannot. They would need to log in via WP Admin to make any changes to the contact. You can read about the custom WP user roles here:
https://kb.jetpackcrm.com/knowledge-base/setting-up-your-team/
Indeed, I can see how our current offering doesn’t fully match up to what you’re wanting to build. I will note that we do support disabling of various CRM modules if that would help, though:
https://kb.jetpackcrm.com/knowledge-base/how-to-activate-deactivate-core-modules/
Best of luck to the future!
Hello! This definitely sounds odd…the CRM plugin runs almost exclusively in WP Admin, and shouldn’t affect Page Speed scores. Are you using the Jetpack or Jetpack CRM (a completely separate plugin)?
If the latter, do feel free to update your review here and instead leave feedback in that other plugin’s support forums:
Hi there! It seems like the issue is that your OpenSSL implementation doesn’t support the
AES-256-GCM
cipher, or else is returning only a lower-case name for the cipher:https://bugs.php.net/bug.php?id=74116
That said, we’ve got a patch in the works; do you mind sending us a message here and we can provide that patched version to you to test?
Thanks for the report! We’ve got a patch on the way for this that should be out in the next hour or so; we’ll update you once it’s released.
Hi again! We’ve released 4.10.1, which should address this error. Thanks for the quick report. :^)
Hello! The Contact Form 7 integration is a paid CRM extension, either purchased individually or as part of a bundle.
Feel free to reach out if you have any further questions!
Hello! For your first question:
CRM Sites and Teams
is a popular request, and you can vote on it here:https://jetpackcrm.com/coming-soon/
We don’t have an ETA, but votes help us to determine where to prioritize our dev time. In the meantime, you’re welcome to review our process for feature requests here:
https://kb.jetpackcrm.com/requesting-features-for-zbs-crm/
As for project management, we don’t currently have any recommendations or specific integrations, so your developer might be the best resource on that.
Thanks for following up, and glad it was resolved!