wpsharks / woocommerce-intercom-pro

WooCommerce Intercom Pro

WooCommerce Intercom Pro

WooCommerce Intercom Pro plugin.

WooCommerce Intercom Pro is a commercial plugin available at https://wpsharks.com/product/woocommerce-intercom-pro. The plugin is hosted here on a public Github repository in order to better facilitate community contributions from developers and users alike. If you have a suggestion, a bug report, or a patch for an issue, feel free to submit it here. We do ask, however, that if you are using the plugin on a live site that you please purchase a valid license from the https://wpsharks.com/product/woocommerce-intercom-pro. We cannot provide support to anyone that does not hold a valid license key.

woocommerce-intercom-pro's Issues

Notice: Array to string conversion in JsSnippet.php on line 108

The customAttributes() method in src/includes/classes/Utils/JsSnippet.php is producing the following:

Notice: Array to string conversion in /app/src/wp-content/plugins/woocommerce-intercom-pro/src/includes/classes/Utils/JsSnippet.php on line 108

Notice: Array to string conversion in /app/src/wp-content/plugins/woocommerce-intercom-pro/src/includes/classes/Utils/JsSnippet.php on line 108

Notice: Array to string conversion in /app/src/wp-content/plugins/woocommerce-intercom-pro/src/includes/classes/Utils/JsSnippet.php on line 108

Notice: Array to string conversion in /app/src/wp-content/plugins/woocommerce-intercom-pro/src/includes/classes/Utils/JsSnippet.php on line 108

Notice: Array to string conversion in /app/src/wp-content/plugins/woocommerce-intercom-pro/src/includes/classes/Utils/JsSnippet.php on line 108

Notice: Array to string conversion in /app/src/wp-content/plugins/woocommerce-intercom-pro/src/includes/classes/Utils/JsSnippet.php on line 108

https://github.com/websharks/woocommerce-intercom-pro/blob/dev/src/includes/classes/Utils/JsSnippet.php#L108

This is because wc_get_customer_available_downloads() returns an array of arrays.

Can't activate the plugin

While trying to activate the plugin, I get the following error message:

Warning: require(//wp-content/plugins/woocommerce-intercom-pro-160909.7530/src/vendor/websharks/wp-php-rv/src/includes/check.php): failed to open stream: No such file or directory in //wp-content/plugins/woocommerce-intercom-pro-160909.7530/plugin.php on line 27 Fatal error: require(): Failed opening required '//wp-content/plugins/woocommerce-intercom-pro-160909.7530/src/vendor/websharks/wp-php-rv/src/includes/check.php' (include_path='.:/usr/share/php') in //wp-content/plugins/woocommerce-intercom-pro-160909.7530/plugin.php on line 27

Ubuntu 16.04, EasyEngine stack (Nginx, Redis, PHP7).

TODO: Create a plugin option that lets you define the scenarios where the widget should be loaded.

Referencing: https://github.com/websharks/woocommerce-intercom-pro/blob/160909.7530/src/includes/classes/Utils/JsSnippet.php#L48

Document Ability to Provide Descriptions

See: https://docs.intercom.com/faqs-and-troubleshooting/your-users-data-in-intercom/can-i-add-descriptions-to-my-custom-attributes-and-events

Update @since Tags

@since 000000 can be set to first release date.

Enhancement: Improve Event Names

The current event name for an order being received (which follows the advice to use verb-noun as suggested by Intercom API docs) is placed-order. This works well because it follows the idea of this being 'Their Activity'; i.e., the reason for a verb- prefix.

However, we are listening for both processing and completed status changes, and potentially others in the future. As it stands now, there are going to be duplicate events (same order, same event name, back-to-back) posted to Intercom whenever this is running on a site that does implement a processing phase.

Instead of placed-order, we could do something that is WooCommerce-specific, such as: order-[status] and subscription-[status]. That would allow for additional statuses to be tracked later as well, without needing to use a different naming scheme. For example, it might be nice to add an order-refunded status event, or order-on-hold.

That doesn't work quite as well with the idea of this being 'Their Activity' though, because the leading verb is dropped. However, it does seem to me like a more informative approach given that what seems most important is to see the customer's activity as it relates to WooCommerce order statuses.

@raamdev Thoughts on this?

SyntaxError: Unexpected token F in JSON at position 1

When placing an order:

Don't Jump to a New Major Release of Intercom

This should be 3.* to avoid jumping over into a new major release without first reviewing the new API. https://github.com/websharks/woocommerce-intercom-pro/blob/160909.7530/composer.json#L34

TODO: Add other WooCommerce-related user-data, such as products purchased.

Referencing: https://github.com/websharks/woocommerce-intercom-pro/blob/160909.7530/src/includes/classes/Utils/JsSnippet.php#L120

Add Event support for Subscription Order Statuses

@jaswsinc writes...

If the shop owner is also running the WooCommerce Subscriptions extension, then you have 'Subscriptions' statuses to deal with also, which are different from Order statuses. For this reason, my suggestion would be to work through Orders first and get those just the way you want them. Then at some point in the future when you have more time to test Subscriptions extensively, you can take a look at all of the possible Subscription statuses.

Update to use Personal Access Tokens (API Keys being deprecated)

Intercom is switching from API Keys to Personal Access Tokens:

If you are currently using API Keys, you will need to switch these to Personal Access Tokens by January 2017 - read more about API Key deprecation here.

https://developers.intercom.com/docs/personal-access-tokens

We need to update the WooCommerce Intercom plugin to support personal access tokens. I'm not sure if there's anything more needed than simply changing the wording and the link in the inline documentation.

Bug: Incorrect Decimal

Intercom recorded 1.03.

The actual sale amount recorded by WooCommerce was 103.20

Feature Request: Origin Site/URI

Add the following fields to the JS Snippet:

'wp_site' => c::clip(home_url('/'), 255),
'wp_uri'  => c::midClip(c::currentUri(), 255),

WooCommerce Intercom Pro v161124.6961-RC (Release Candidate)

Target Date for General Availability Release: November 29th, 2016

Downloads

• WooCommerce Intercom Pro v161124.6961-RC (requires membership in WebSharks organization on GitHub)

Changelog

• See WooCommerce Intercom Pro v161124.6961-RC (requires membership in WebSharks organization on GitHub)

Reporting Issues / Feedback

Please report any issues or feedback related to this Release Candidate using this GitHub issue. Please post a comment below with details.

If you are reporting a UI-related issue, please include a screenshot.

If you are reporting a bug, please provide list of steps to reproduce and if the bug is related to an existing GitHub issue, please provide a link to that GitHub issue as well.

---

Reported Issues to Fix

None at this time.

TODO: Add support for Intercom Engage?

Referencing: https://github.com/websharks/woocommerce-intercom-pro/blob/160909.7530/src/includes/classes/Utils/JsSnippet.php#L86

Move JavaScript Snippet Into Template

Move this snippet into a template file for easier maintenance.
https://github.com/websharks/woocommerce-intercom-pro/blob/160909.7530/src/includes/classes/Utils/JsSnippet.php#L49

identity verification

So I've been doing quite a bit of digging here into this plugin. Unfortunately, this isn't actually an official integration with Intercom at all, as an official integration will never ask you for your Access Token, as it seems that WooCommerce Pro seems to do 🤔
Recently Intercom started using identity verification, which this plugin doesn't support and therefore won't load the chat for logged in users. Also won't transmit the purchase information over to Intercom at all.

These Access Tokens should be treated in the same way as passwords, and should never be handed out to external parties like this, as they get access to your customer's personal information and can do what they like with it.

I would actually advise the developers to apply for OAuth with Intercom, which they can do here https://developers.intercom.com/docs/applying-for-oauth.

In the meantime, the fastest and safest way to resolve this issue would be to stop using the WooCommerce Pro integration, as it is the main cause of the issues at play here.

I know this isn't an ideal solution, but for your own security it really is the best solution right now!

Compat: Support Email Address if User ID Missing

In the case of guest checkout, support email addresses in event reporting.
https://github.com/websharks/woocommerce-intercom-pro/blob/160909.7530/src/includes/classes/Utils/Events.php#L175