leonardorodriguez

Issue is still alive in last woo version for Argentina

But hey! We have new graphs! :facepalm

El problema no es el mapeo de estados. El problema es que la función que toma la nueva notificación, no chequea el estado actual antes de cambiar al nuevo estado

Cabe decir entonces que, como era de esperarse, vamos a seguir teniendo que mantener un fork del plugin, solo para que funcione correctamente?

Thank tou very much for your support

What i want is to disable that select dropdown filter, in order to prevent from appear at all

Grande Conrado!!

En mi caso son ventas de hace 14 días (venta 10/6 -> vuelve a procesado 24/6)

Casualmente tengo “Vencimiento de pago” (checkout personalizado ticket) en 14 días

Cambié a 13 días para probar si eso tiene algo que ver

Se imaginan cuánto tiempo va a pasar hasta que lo arreglen, no?

Diría de pensar alternativas. Alguien probó usando woo 4.2 con otra versión del mpago plugin?

I do use official 0.6, updated to last version, plugin

No cache or other plugin settings

It doesn’t work for CSS/JS from non wordpress core

@fransallen I’m ok with the service stop but, there was no notification at all?

I found out about this, only by waking up in the morning and watch my site go down

I get the free bla bla, but not the mistreatment

If you fail to notify a breaking change like this, how am i supposed to trust you with my money?

But when i don’t use Statically CDN URL in Wp-Rocket, only core WordPress css/js get fetched from Statically.

Other css/js get bypassed

Is it working for you now?

I haven’t checked yet

No creo que por código externo puedas cambiar en la api de mlibre

Entiendo que calcula igual, porque la api es la misma de mlibre y está en funcionamiento. Simplemente desactivan el me a los vendedores

me2 es el servicio asignado en la api

El error que te da es que no tenés Menvíos activo. Quiere decir que te lo desactivaron

Thank you but i’ll pass

Only needed this in functions.php:

add_action('wp_footer','dcms_add_footer_whatsapp');
function dcms_add_footer_whatsapp(){
	$tel = "#####";
	$ms = urlencode("@@@@@");

    //$url = "https://api.whatsapp.com/send?phone=${tel}?text=${ms}"; 
    $url = "https://web.whatsapp.com/send?phone=${tel}?text=${ms}";
	$img = get_stylesheet_directory_uri().'/assets/css/whatsapp-icon.svg';
	echo "<div id='float-whatsapp' class='show-for-medium' style='position:fixed;bottom:5px;right:5px;z-index:999;'>";
//  echo " <a href=${url} target='_blank'>";
    echo " <a href=${url} >";
	echo " <img src='${img}' width=40 height=40 />";
    echo " </a>";
	echo "</div>";
}

• This reply was modified 4 years, 6 months ago by leonardorodriguez.

Let’s see:

Export orders to csv -> answer prompt to save/open -> excel/openoffice/google sheets (and their clicks) -> save/export to csv again -> clicks to uploadload file

For a daily (and more than once a day) proccess, that’s a lot of clicks versus:

One click action button in orders panel -> get a list of orders with tracking number field -> fill numbers -> one click to save (and change order state to shipped)

There you go. Dev vs merchant. Lots of clicks vs user experience

Not pointing at you, even woo itself lacks UX from this era

Indeed, WOW

Millenials…