Getting this error while trying to activate the plugin.
Fatal error: Cannot declare class ComposerAutoloaderInita3d2bcc47a549b1aa1b41cc9fbc764c9, because the name is already in use in … public/wp-content/plugins/wootomation/vendor/composer/autoload_real.php on line 5
Could you help resolve this error or suggest a work around?
]]>Hello, first of all, thanks in advance for building this product.
I installed it on the site https://emporium.com.gt/, they run on average 10 to 20 orders per day, and have around 800 products published.
On the cart page, you can check out that the products that are shown through the plugin are always the same, it does not matter the products on cart.
The plugin has been installed for around two weeks now.
I checked the programed actions on Woocommerce and apparently the wootomation_ai_train_orders hook has been executed correctly.
If you had any idea on how to fix, I would greatly appreciate it.
]]>Hello
I have installed the plugin and it gives a critical error on the cart page where the product should be shown.
First it is good but after some our it gives this error
]]>Hello and thanks for this great plugin!
Is it possible to show the recommended products with a shortcode in product page or somewhere else?
That would be very good!
]]>Hi, first, thanks for this great plugin!
In mobile view the recommended products appear after products in cart but before totals and checkout button. It s possible to reposition the recommended products to appear after checkout buttons? (for mobile view at least).
thanks a lot
]]>Would be great if we would have an option to select the number of products to show in the cart page per row!
Currently (based on my theme), it shows 3 per row (i believe this takes your woocommerce settings)
However within the cart page, 3 per row causes the products to appear really big, so ideally it’ll show 6 per row.
]]>Will this “remember” products based on their SKU or based on the woo page ID?
]]>Hello,
was trying to add different product in my cart to see how related the AI is.
But for some reasons, php errors shows
Warning: Invalid argument supplied for foreach() in /www/wp-content/plugins/wootomation/wootomation.php on line 246.
i need to disable it ??
]]>[09-Sep-2020 02:53:09 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘)
AND meta_key IN (”)’ at line 3 for query
SELECT post_id as variation_id, meta_key as attribute_key, meta_value as attribute_value
FROM wp_postmeta
WHERE post_id IN ()
AND meta_key IN (”)
made by require(‘wp-blog-header.php’), wp, WP->main, WP->parse_request, do_action_ref_array(‘parse_request’), WP_Hook->do_action, WP_Hook->apply_filters, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, Automattic\WooCommerce\Blocks\StoreApi\Routes\AbstractRoute->get_response, Automattic\WooCommerce\Blocks\StoreApi\Routes\Products->get_route_response, Automattic\WooCommerce\Blocks\StoreApi\Schemas\ProductSchema->get_item_response, Automattic\WooCommerce\Blocks\StoreApi\Schemas\ProductSchema->get_variations
Hi!
I tried testing this in a staging environment on our online store. I relay like the idea and want to try it ??
We run Php 7.3 and we cant activate the plugin. It tries for a full minute and then we get 504 gateway timeout. We have 3000+ orders saved, might that be what causes the timeout?
Victor
]]>I’ve noticed products that are out of stock are being included in the recommendations. This is not desirable in my store.
However, simply excluding out of stock products altogether would not necessarily fit all scenarios. For example, if a store allows backorders on some/all products then including those products in the recommendations may still be desirable.
I’d suggest adding a couple of checkboxes to control this, e.g.
– Exclude out of stock products from recommendations (yes/no)
– Include out of stock products that can be backordered (yes/no, only available if the first option is selected)
I installed this plugin yesterday, and the messages that should be triggered 1 month and 2 months after installation appeared on the admin dashboard the same day.
I assume this is a bug in the code that needs fixing.
]]>