mlnick

Resolved via support emails.

@mr_pa by the way, we only pop up notifications in a few situations:

1. When the plugin is activated – we put a notice to provide a shortcut to the Graphflow settings page in case you can’t find it. It goes away on the next request.

2. We put up a notice when settings are saved to confirm that your Graphflow Client and API key settings are correct. If they are not, we highlight this with an error notice so that you can put in the correct keys – otherwise the plugin will not work.

3. We put up a notice when orders or products successfully export to let you know this has been ok – this also goes away on next request.

If you’re seeing other notices or issues with the notices please shoot us a message with any supporting screenshots or logs that can help us identify the issue. If you need to send sensitive info please use our support email address found here: https://graphflow.com/contact-us/

Thanks
Nick

Hi

Just wanted to update you on this.

We’re not 100% sure of the cause – but we think most likely it is due to bots that try to access a “feed” URL in WordPress / WooCommerce. We’ve seen this occur in some of our demo sites and now a few customers’ sites too.

We’ve added some checks to try to avoid capturing product info on these page loads if there is no product. We’ve also added some logging using the WC Log, to try to help diagnose and record when and why issues occur with product and order export.

We’re almost ready to release that new version but not quite there yet. We’ll let you know when we do.

Finally, we have fixed the original issue with “PHP Fatal error: Wrong parameters for Exception” and that will be in the new version.

Hi Gregorio,

Sorry for the delay. I sent you an email also via our Support desk.

We’re not 100% sure of the cause – but we think most likely it is due to bots that try to access a “feed” URL in WordPress / WooCommerce. We’ve seen this occur in some of our demo sites and now a few customers’ sites too.

We’ve added some checks to try to avoid capturing product info on these page loads if there is no product. We’ve also added some logging using the WC Log, to try to help diagnose and record when this occurs.

We’re almost ready to release that new version but not quite there yet. We’ll let you know when we do.

Thanks
Nick

Hi Gregorio

We have been seeing this issue quite a few times and we’re trying to find the cause but have not yet been able to reproduce it.

Could you send as much log detail as possible, as well as the output of your WooCommerce System Report (WooCommerce -> Setttings -> System Status -> Get System Report) to our support email address listed on our contact page: https://graphflow.com/contact-us/

Thanks
Nick

Hi

Yes – you can just leave it and products will be exported on every page view (if it has not already been exported).

Having said this, it is still beneficial to try to export them all upfront, so our engine can get to work quickly (as we make some use of the product data such as title and description, as well as categories, for recommendations). So, while it is not strictly necessary, the plugin will work a lot better if you are able to bump up the memory limit (at least temporarily) to export all the products.

We have seen customers exporting many thousands of products successfully so it should work (but certainly for that size often a higher memory limit is needed).

Hope this helps
Nick

Hi Jan

Thanks for pointing that out about the email address posting.

We provide our support emails listed at https://graphflow.com/contact-us/. Do feel free to post any queries to that email address.

Simon has sent that to us (thanks!) so we will look into this and get back to you as soon as we figure out the root cause.

Thanks for your patience and support.

Nick

@mr_pa

Thanks for letting us know. We will look into this issue again further. We have done extensive testing and this issue does not seem to be happening in all cases.

So in order to track down the root cause, we rely on you our users to help us out. Please could you email our support address (listed at https://graphflow.com/contact-us/), and provide us with the output of your System Report (under WooCommerce -> System Status).

If you can also provide any access and error logs to us that would help us find out exactly what is causing the error, that would be very helpful.

Thanks
Nick

Hi Simon

Thanks for letting us know.

Is it possible to provide any debug log output at all? Also, please provide the output of the System Report, found under WooCommerce -> System Status) -> Get System Report button.

Thanks
Nick

Hi

Thanks for letting us know. How many products are in your store?

It may be that increasing the WordPress memory can solve this. From our FAQ (https://www.ads-software.com/plugins/woocommerce-recommendations-by-graphflow/faq/):

I’m getting errors when trying to export products or orders

While we aim to make the export process as lightweight and efficient as possible, you may need to ensure you’ve allocated enough memory to WordPress to make sure the export works as expected. If you run into problems, you can try to increase the memory allocated (check out this link for more details: https://codex.www.ads-software.com/Editing_wp-config.php#Increasing_memory_allocated_to_PHP).

If you can’t do this or it doesn’t work for any reason, don’t worry – we collect your data on the fly with each customer interaction, so we will quickly build up the information we need to power your recommendations.

Hi Luke

I understand you would wish to deactivate it. Are the errors being logged impacting the site performance at all?

It’s a little difficult to debug fully remotely without more detail on which requests are causing these. As I mentioned above, it could be due to a certain type of request in which case we can fix it easily enough. Or it could be a bug that we need to track down.

We would really appreciate any assistance you can provide with error/debug logs in order to track down the exact cause. If you’re able to email that to our support email that would be really helpful.

We will also work on improving the error handling and logging the issue and error messages to the WC log.

Thanks
Nick

Hi Luke

I’ve seen the 2nd error you mention in the logs on our test site. It appears that it may be related to bot activity.

For example, here is an entry in the log that caused an error.
“GET /?product=gumby-the-movie&feed=rss2 HTTP/1.1” 200 1182 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +https://www.google.com/bot.html)”

Are you able to check your access and error logs to see whether these are being caused by similar requests? If this is the case we can push a fix to exclude the product data export attempt if it is a feed request.

For the other errors, any request / debug logs would help us.

Thanks
Nick

Hi Luke

Are you able to provide a few example calls / debug information / stack traces for when this is occurring? It seems related to trying to export product data. If you are able to email us at support at graphflow dot com with more detail that would help us track down what is going on.

In the meantime we’ll see if we can try to reproduce the issue on our test sites.

Thanks
Nick

Hi Gaston

We have released version 1.0.6, which fixes this issue. It was due to a conflict with the widget id and that of the built-in WooCommerce Product widget.

Note that you will need to delete and re-add the widget to get it to work again (see this post for more detail: https://graphflow.com/version-1-0-6-woocommerce-recommendations-released/)

Thanks for bringing it to our attention, and do let us know if you run into any further issues.

Nick

Hi Luke

Thanks for letting us know. We will look into it and get back to you as soon as possible.

Which version of the plugin do you have installed? And which WooCommerce version are you using?

Nick