LiamMcArthur

It does work, yes – but with errors in the Javascript console when minifying content. I’ll forward details of the issue to that email address now.

@jurasjo @andrewfitz @robin113 I’ve updated my ammended version of the plugin file so that it works with virtual orders too! https://github.com/LiamMcArthur/woocommerce-autocomplete-orders

UPDATE: This is not working in my local XAMPP version of the website in Windows. I’ve now tested the plugin in my live Linux environment and it appears to be working okay.

Please see my version of the plugin file here:
https://github.com/LiamMcArthur/woocommerce-autocomplete-orders/blob/master/woocommerce-autocomplete-orders.php

I’ve replaced depreciated $order->status calls with $order->get_status(). I haven’t tested this for virtual products, since I don’t have the need for them – but this is now working for me in WordPress 4.8 with WooCommerce 3.0.8.

Couldn’t you embed your full screen ‘popout’ link onto that page to achieve this? For example:

<iframe style="width:100%; height:500px;" src="https://tawk.to/chat/521727297ca1334016000005/18nms7gql/?$_tawk_popout=true&$_tawk_sk=593e60dfd64b9bda0dfa6d58&$_tawk_tk=0810f4293465081122c1b1f3c906fd01&v=555"></iframe>

I’m also getting these depreciated errors. Are there any plans to update this plugin?

• This reply was modified 7 years, 6 months ago by LiamMcArthur.

I did send an email to the address you mentioned, but I’m not in a position to give over Analytics or WordPress access unfortunately. The issue seems to be something to do with the following code in class-wc-enhanced-google-analytics-integration.php:

if(!isset($_SESSION) ) 
{ 
session_start(); 
}

Thanks – look forward to seeing a fix! In the meantime, commenting out statusContainer.innerHTML = ""; seems to correct the issue for me.

Thanks for pointing that out! I’ll get that fixed and uploaded.

There seems to have been a conflict with my template. This works now!

Thank you for the quick responses. I’ll leave it enabled for now. I just figured if there was ever a vulnerability in the API that wasn’t patched I’d be unnecessary vulnerable.

UPDATE: I’ve no idea how, but “Display Main ShiftNav Panel” was unticked! I’ve enabled that checkbox and it’s working magically now!

I can see all of the scripts and stylesheets loading correctly and yes I can confirm wp_footer() is included in the footer.

I’ve been comparing my site source with the demo on https://shiftnav.io/free/ and I’ve noticed that my “shiftnav-toggle-main” division is being added into the footer of the website, whereas the demo is generated in the header. Further to this, I have no division with a class of “shiftnav-shiftnav-main”. I’ll continue investigating the issue but unfortunately, I wouldn’t be able to provide a working demo at this stage because it’s a private on-going project for my employer.

Feel free to close this ticket, I just thought I’d check with you just as I wasn’t sure if it was a compatibility problem with 4.7 or something.

Perfect – that worked! I can’t however see the data on the database so I’m guessing that it didn’t get saved through – but I’ll try and suss it out ??