ronin Creativos

thank you. issue fixed ??
awesome work.

Yes, issue is corrected. thanks!

Hello there. Thanks for the *very* quick response. I can wait till the update.
Thank you, great work.

@webdevwp yeah, having to pay to use custom fields, which you can add for free with ERF, is truly “magical” u.u-
and btw that “site down” thing.. i call bs.

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

are you sure its not the guttenberg thing..? just saying.

hello.
thanks for the redaction, thats quite alright. (but thats exactly how it feels ??
however.. i still think you guys will. mess. this. up. though this is your show and you’re totally entitled to do so.
cheers and thank you.

hi, thank you for your response.

as i stated, the main reason i believe this is a mistake is that you are doing this upside down. the plugin should be in order to activate this “mode” of editing, not to disable it. read again: “a plugin to disable a feature”. what kind of logic is that?

also, i can only assume you used the survey data (i myself answered to) and conclude that “the masses” are bloggers? i was given to understand that mostly wordpress (.org self hosted) was used by developers to offer solutions to third parties (clients), and that bloggers had, well, wordpress.com for blogging only. you could even make just an option to activate this on that platform.

choking thousands of developers and webmasters with this huge change and messing up sites and plugin compatibility (both functional and visually wise) in the process.. im sorry but i cannot fathom what are you guys trying to accomplish here, truly. maybe im just dumb.

theres nothing wrong with changing a paradigm, and sorry if im blunt, but it kinda feels like [inapropriate text redacted]

you guys should really think this through.
thanks

• This reply was modified 7 years ago by Marius L. J.. Reason: Modified inappropriate text

@marcelo-mika
Gracias Marcelo. funcionando sin problemas hasta el momento.

@marcelo-mika
con respecto a lo otro, no se esta aplicando doble impuesto. se utiliza un plugin de terceros para a?adir un cargo fijo o en porcentaje a los medios de pago. en este caso mercadopago. el impuesto de woocommerce global no se esta utilizando.

@marcelo-mika
hola Marcelo. voy a tratar de explicar mejor.
si es necesario, puedes visitar este enlace este enlace donde estan los pantallazos del plugin de mercadopago.
cuando el usuario elige pagar con tarjeta o a traves de PSE, el valor del pedido se multiplica por el número de items en el carrito, asi tal cual. puedes ver las imagenes mas arriba: habiendo 3 items en el carro, el pedido suma 54.450, pero al ir a pagar, aparece 1 cuota de 163.350, 2 cuotas de 81.675, 3 de 54.450 y asi sucesivamente. es decir, se esta triplicando el monto a pagar (3×54.450) . debido a esto se tuvo que deshabilitar por completo mercadopago, e incluso intentamos con varios plugins para adicionar el cargo extra. si se hace manualmente (functions.php) mercadopago ignora el cobro adicional.
no se si quedo claro :v quedo atento

@germanero es decir que debe colocarse el valor adicional como impuesto, cosa de que se aplique al final? que diferencia hay entre eso y agregar un cargo fijo mediante third-party plugin (que es lo que estamos haciendo aca)? en los pantallazos no lo capture, pero se ve igual al que pones, pero en lugar de poner “cmp” dice “mercadopago” (claro la etiqueta es de libre uso, puede decir lo que sea).
gracias por la ayuda.

@marcelo-mika
Hola Marcelo. hay un inconveniente con el plugin. Si se a?ade un item al carrito, no hay problema. pero si se a?aden 2 o mas, al pasar a PSE el plugin multiplica el total por el número de items en el carrito, lo que obviamente altera el precio a pagar.

imagen 1
imagen 2

@marcelo-mika
gracias Marcelo por la solución! Tampoco encuentro opción para comunicarme desde el perfil :v pero debo preguntar: si actualizas el plugin, donde lo obtiene uno? de nuevo mil gracias por esto! buen trabajo!

edit: ya vi en el sitio web ?? gracias.

• This reply was modified 7 years, 5 months ago by ronin Creativos.

hi there.
yes the progress bar is that of the rich text editor inside the post. it doesnt generate the icons as seen in the video. this may be due to server not reading the files, server trying to generate thumbnails (with or without thumbnail generation option ticked) or just because of the file size..

the single column is not honoring the column size set in options or gallery creation dialog when descriptions are enabled. the div has 100% width so it takes up all the space, thus creating a single column. no description, no 100% and it behaves as expected (divs 24% for 4 columns).

__EDIT i just read carefully the options and it says “The number of columns to display **when not rendering descriptions**” so it is indeed the intended behavior.. kind of odd since the user probably expects 4 columns even with the descriptions ??

i would like to see a list style option– so ill [try to] hack some css and if it works then ill share it so you may include it in future release ??

–ronin

well it is indeed. but when i updated the plugin in one installation, the error persisted. i installed anew in a nother instance, and the error was gone. so yes, it is fixed ?? (weird though)
thank you