Uncanny Automator

Thanks @wpwebsites , we appreciate the suggestion! It looks like you have requested this a few times, and it is still being reviewed for development.

Thanks @arypneta , we were able to confirm the issue as you described and have fixed it internally. We will include the fix in the next release, but if you do need something sooner let us know and we’ll package something that you can use.

I will tentatively mark this as resolved, though it won’t be released until the next update.

• This reply was modified 3 months, 3 weeks ago by Uncanny Automator. Reason: typo

Interesting, so somehow something in your environment really is treating our view as a table. Thanks for the update here; I’ll pass this back to our developers for review.

It sounds like you’re okay now, but can you confirm?

Hi @paveldohnal ,

Thanks for the notice! I’m just confirming this is currently in development on our side and we’ll post here when the change is included in a release.

Sorry @atomicbong , did you adjust what we sent to target the specific site IDs for your network? Have you reached out to the host to have them drop the views? And sorry, did you also try installing Automator on the site with the ID that’s affecting, use our tool there to drop views and tables, and that failed as well?

And sure, if you want to reach out via our site with the additional details, our team can certainly resolve it for you.

Thanks

Sure. Based on what you sent us, something like the following would work (and you can adjust it based on how many sites you have using this as an example):

-- Drop views if they exist for uap_recipe_logs_view
DROP VIEW IF EXISTS wp_1_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_2_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_3_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_4_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_5_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_6_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_7_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_8_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_9_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_10_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_11_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_12_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_13_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_14_uap_recipe_logs_view;
DROP VIEW IF EXISTS wp_15_uap_recipe_logs_view;

-- Drop views if they exist for uap_trigger_logs_view
DROP VIEW IF EXISTS wp_1_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_2_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_3_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_4_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_5_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_6_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_7_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_8_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_9_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_10_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_11_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_12_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_13_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_14_uap_trigger_logs_view;
DROP VIEW IF EXISTS wp_15_uap_trigger_logs_view;

-- Drop views if they exist for uap_action_logs_view
DROP VIEW IF EXISTS wp_1_uap_action_logs_view;
DROP VIEW IF EXISTS wp_2_uap_action_logs_view;
DROP VIEW IF EXISTS wp_3_uap_action_logs_view;
DROP VIEW IF EXISTS wp_4_uap_action_logs_view;
DROP VIEW IF EXISTS wp_5_uap_action_logs_view;
DROP VIEW IF EXISTS wp_6_uap_action_logs_view;
DROP VIEW IF EXISTS wp_7_uap_action_logs_view;
DROP VIEW IF EXISTS wp_8_uap_action_logs_view;
DROP VIEW IF EXISTS wp_9_uap_action_logs_view;
DROP VIEW IF EXISTS wp_10_uap_action_logs_view;
DROP VIEW IF EXISTS wp_11_uap_action_logs_view;
DROP VIEW IF EXISTS wp_12_uap_action_logs_view;
DROP VIEW IF EXISTS wp_13_uap_action_logs_view;
DROP VIEW IF EXISTS wp_14_uap_action_logs_view;
DROP VIEW IF EXISTS wp_15_uap_action_logs_view;

-- Drop views if they exist for uap_api_logs_view
DROP VIEW IF EXISTS wp_1_uap_api_logs_view;
DROP VIEW IF EXISTS wp_2_uap_api_logs_view;
DROP VIEW IF EXISTS wp_3_uap_api_logs_view;
DROP VIEW IF EXISTS wp_4_uap_api_logs_view;
DROP VIEW IF EXISTS wp_5_uap_api_logs_view;
DROP VIEW IF EXISTS wp_6_uap_api_logs_view;
DROP VIEW IF EXISTS wp_7_uap_api_logs_view;
DROP VIEW IF EXISTS wp_8_uap_api_logs_view;
DROP VIEW IF EXISTS wp_9_uap_api_logs_view;
DROP VIEW IF EXISTS wp_10_uap_api_logs_view;
DROP VIEW IF EXISTS wp_11_uap_api_logs_view;
DROP VIEW IF EXISTS wp_12_uap_api_logs_view;
DROP VIEW IF EXISTS wp_13_uap_api_logs_view;
DROP VIEW IF EXISTS wp_14_uap_api_logs_view;
DROP VIEW IF EXISTS wp_15_uap_api_logs_view;

Hi @atomicbong ,

Sorry about the confusion in the other thread. It’s fine to mark it as unresolved too; we’ll see any updates you send and can flag it accordingly too.

Okay, we do want to confirm again that what’s reference is not a table; it’s a database “view”, so it does work differently. It’s odd that your plugins are detecting it as a table, because it isn’t one.

If you have access to PHPMyAdmin through the hosting, it’s fine to go in, find the views, and drop them from there.

With regard to the cleanup routine, we rely on the WordPress native uninstall.php capabilities, so we could potentially see how it might not target child site views. We’ll take a look, but given the urgency, dropping views using PHPMyAdmin will be fastest, or you could potentially reactivate Automator on the child site that’s causing the error, drop the views and tables from Automator > Status > Tools, delete the plugin, then try again.

Hi @atomicbong ,

Sorry about the confusion here. Please note that what you’re referencing are “views”, not “tables”, so the behaviour is a bit different. It’s unusual that whatever duplication tool you’re using is trying to treat views as tables.

When Automator is active, you can visit Automator > Status > Tools in /wp-admin/, then use the trash icons at the top to drop our views. You can also reset all tables from there. Or, if you visit Automator > Settings > General > Data management, you can check the “Delete all data” switch, save the setting, and then when you deactivate and delete the Automator plugin, everything related to Automator will be deleted from your database.

Hi @gabrielgekko ,

I know we have been talking about this issue via the Help Desk as well, so I’ll tentatively close this ticket on .org so that we’re just discussing it in the one location.

Thanks

Sorry @kingcooper , we’re going to say that Automator probably isn’t the right fit here. We checked the API documentation you sent and access tokens last for 15 minutes only, so you would need a way to first send data to get an access token back, then pass that to an authorization header to allow the communication between the 2 platforms. It’s possible, but a bit complicated with Automator to set that all up to ensure authorization would work reliably because of the short token duration.

Sorry about that.

Hi, as it has been over a month since the last update, we’ll go ahead and mark this thread as resolved. You’re welcome to reopen it if there are still unresolved issues and you’re able to provide feedback based on the reply above.

Thanks

Hi @kingcooper ,

Apologies for the delay.

We can send data out via webhook to other APIs and receive data back via webhook (please see https://automatorplugin.com/article-categories/wp-webhooks/ for more details), but this also depends on what you’re using to manage inventory. Is this Woo or something else? For integration with another platform we would really need to see what they can support for sending and receiving data; maybe you could provide a link to their API documentation so we could have a quick look.

Hi @eurisko , thanks for following up to confirm!

That is still an unusual behaviour. For some SaaS platforms we sometimes see delays where they queue requests, and that could be similar here, or in some cases we see large Action Scheduler delays. If the delay becomes problematic or starts taking longer, maybe reopen this ticket and include details from Automator > Status and our team can take a look.

Thanks @steveplugins ! We really appreciate the review.

That’s great! Glad to hear it was an easy fix and that things are resolved.