m_disseny

Buenas Jose, disculpa, por si no quedó claro, en ningún momento mencionamos que el problema fuera de tu plugin, obviamente esto sucederá también con cualquier otro método de pago. Sólo era una observación por si te llegaba un alud de comentarios al respecto ya que Yoast es un plugin muy popular. Gracias y saludos.

Gracias Jose, tiene que ver con las redirecciones seguro, lo raro es que sólo afecta a usuarios no logueados. Si conseguimos más información te la dejamos aquí. Gracias y saludos.

Marc

Just found the solution by removing all the blank spaces between the html tags.

Thanks

Hi there,

just came across the same error.

Thanks @wpo365 for providing the link.

Hi there,

same issue here. In our case it seems like it’s only syncing transactional customers, we would like to sync all existing registered customers.

Thanks in advance

Muchas gracias Jose por la rápida respuesta.

Los responsables del servidor nos indican que no hay ningún tipo de bloqueo. Estamos sospechando si puede existir algún tipo de bloque a nivel de dominio, que este se encuentre en una lista “abused-legit”.

No sé si tienes experiencia en algún caso parecido, hemos preguntado a RedSys pero aún no tenemos respuesta.

Muchas gracias y saludos

After further investigation I can confirm that the issue is not related to the 2.4.1 update. I managed to successfully update several installations from 2.4.0 to 2.4.1 where profiles were not lost.

I still wonder how profiles can be lost, I would appreciate any clarification on this matter if possible.

Thanks in advance

Cheers

• This reply was modified 2 years, 1 month ago by m_disseny.

Hi @saifulananda,

many thanks for your interest. As you are the plugin developer I’d recommend you to get directly in touch with the WPML team. I’m pretty sure they will provide you the tools or the environment to make your plugin compatible.

Have a nice day!

Hi Martin,

did you try to update again the product? We faced a similar issue today. After re-updating the product (without changing the stock), the emails were successfully sent to subscribers. We use post SMTP so we were able to check that emails were not sent yesterday when we updated the product to get it back in stock.

Weird… hope someone can shed some light and debug the issue.

Thanks in advanced

M

• This reply was modified 2 years, 5 months ago by m_disseny.

Hi there,

I agree that this can be confusing at first, more information should be provided by the developer.

The three options are pretty self explanatory: dashboard, frontend and editor. There are three options or behaviours for each one as well:

Allow: allows the default WP heartbeat
Disallow: disables the WP heartbeat
Modify: allows to change the default WP heartbeat time of 15 seconds

If you want to leverage the CPU usage you’ll have to choose between the disallow or modify options. I guess there is no “magic” or optimal time for the “modify” option, as it depends on many factors. That being said, for example, you can increase the heartbeat time from 15 to 60 seconds, this would mean that you’ll be consuming 4 times less CPU usage.

If you had complains from your hosting provider you can ask them if they have a recommended set up.

Hope this helps

Cheers

• This reply was modified 2 years, 6 months ago by m_disseny.

Hi @arsalantariq

Thanks for fixing the issue, I confirm this Beta Version fixes the issue, now the email log is accessible without further errors.

Thank you!

Cheers

Hi there,

doesn’t work for me neither, php 7.4. I had to manually update the folders|extensions directly on the file lib/class-bulkmediaregisteradmin.php. Updating the db directly from phpMyAdmin didn’t work, all changes reset after reloading the settings page.

Also the alert message “Changed the way files and folders are excluded” appears after every page reload, even if closed or accepted.

Otherwise, many thanks for this great plugin.

Maybe its not related to @dvalken issue, but just to shed some light on the problem: In our case, after updating to 1.2.5, the only problem we faced was a server timeout while running this function. It was set to 30s and, after increasing the limit to 300s, everything worked properly. As I said on the reviews, this function should be run in background to prevent these timeouts on large product catalogs or with lots of variations.

That sounds great!

Many thanks for the quick fix.

Cheers

Same here…

Also there is an error on product pages, on the radio metabox inside variations the following notice appears:

Notice: Undefined index: id in /usr/home/andorrapneumatics.com/web/wp-content/plugins/woocommerce/includes/admin/wc-meta-box-functions.php on line 257 Notice: Undefined index: label in /usr/home/andorrapneumatics.com/web/wp-content/plugins/woocommerce/includes/admin/wc-meta-box-functions.php on line 257

This could be easily addressed by editing the public function variation_settings_fields, adding into the woocommerce_wp_radio array the id and label index:

woocommerce_wp_radio( array(
  'id' => 'woosv_enable[' . $variation->ID . ']',
  'label' => '',
  'name'    => 'woosv_enable[' . $variation->ID . ']',
  'value'   => get_post_meta( $variation->ID, 'woosv_enable', true ) ?: 'default',
  'options' => array(
    'default' => esc_html__( 'Default', 'wpc-show-single-variations' ),
    'enable'  => esc_html__( 'Enable', 'wpc-show-single-variations' ),
    'disable' => esc_html__( 'Disable', 'wpc-show-single-variations' ),
    'reverse' => esc_html__( 'Reverse', 'wpc-show-single-variations' )
  )
) );

• This reply was modified 3 years, 7 months ago by m_disseny.