[Resolved] Changing image at productpage. It goes off stock

Hey there,

Thanks for your contact, and welcome to the WPML support forum!

Let's try a possible solution and some debugging steps for this issue. By looking at your debug info, it is possible to see that the WP Memory Limit is set to 40M, while the recommended is 256. Changing it can solve the problem. Please follow these steps:

- Find your wp-config.php file in the root directory of your WordPress installation
- Open the wp-config.php file with a text editor, then locate the line that includes: define('WP_DEBUG', false)
- Then add after it, the below line of code: define ('WP_MEMORY_LIMIT', '256M');
- Save the wp-config.php file, then refresh your website and check if the issue persists

If the problem remains, we might be facing an interaction issue with a third-party functionality, in this case:

- Deactivate all the plugins that are not related to WPML
- Switch for a moment to a WordPress default theme like Twenty Twenty-one
- If the issue is gone, activate one by one to see with which one there is an interaction issue

Could you tell me the results of this investigation? Also, can you enable the debug mode? Please add the following code in your wp-config.php file:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
  
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
  
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
  
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );

Please check the following links to read more about debugging with WordPress.
- https://codex.wordpress.org/Debugging_in_WordPress
- https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging

After adding the code above, try to reproduce the issue again and check if you'll find a debug.log file inside the wp-content folder. If you locate it there, please send us the last lines here in the ticket.

We're looking forward to your reply. Thanks!

Regards,
Mateus.

Hey there,

Thank you for providing the website credentials.

We have just checked the products, but we weren't able to reproduce the problem. By changing the images and the titles, the products (original and translations) remained in stock.

Am I missing some fundamental steps in order to replicate the issue? Please keep us posted about this.

Thank you,
Mateus.

Hey there,

Thanks for providing the website credentials, but unfortunately, we're still receiving this message: hidden link, since the login details are the same as before.

Could you please review it once more? Regardless, we have another option. In order for us to take a closer look at this issue, I'd like your help creating a package of your website and sending it to us.

Please use the plugin Duplicator(hidden link) to create a full copy of your website so we can take a look at it and see what's causing the issue with the large table.

Please check our tutorial on how to create a Duplicator package here: https://wpml.org/faq/provide-supporters-copy-site/

If you come across problems while creating it, please feel free to ignore(exclude from the backup) both uploads and cache folders.

I'm enabling the proper field for your to share this copy, you'll see it on your next response.

Alternatively, you may use any file sharing service that you prefer and share the link in the ticket(your next response is being marked as private, only you and I have access to it).

Thank you, please let me know.

Hey there,

Thank you for correcting the credentials.

The video is not necessary, we were able to reproduce the issue by changing the product image on the native WordPress edit screen.

The problem now is that after we recreated the product, in order to make it in stock again, the issue couldn't be replicated. Please check it: hidden link

Are you following any specific steps in order to create this product that we might have missed? Please let us know the exact step-by-step in order to replicate the problem and we'll continue debugging it. Thanks!

Regards,
Mateus.