Mati

check here the log luizaxl.nl/wp-content/debug.log, only when i activate the Mollie plugin i see the PHP Deprecated

• This reply was modified 1 month, 2 weeks ago by Mati.

thanks for the clarification. i use google for woocommerce then explain that.

Hello @glenwpcoder

I want to share the data but not make it public here because it contains sensitive data. Can I email it?

I tried the code changes but nothing helped

correct I had also placed the shortcode of flatsome and tested it individually. ignore flatsome for a moment that is not the issue. I have already done everything you have done before I asked support. have been working with wordpress and wc for more than 10 years so I have already followed the advice before I contacted. would you still like to see what the problem is? simple product and variable product with all discounts with sub variations works only if a variable product has a variation action then not

After updated tho the last version i get this:

PHP Deprecated: [24-Jan-2025 08:11:13 UTC] PHP Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in public_html/wp-includes/formatting.php on line 4467

thank you very much for your time and extensive action.

by the way could you confirm that the function I posted in the chat is correct?

I also requested support via woocommerce direct about your plugin and they advised to use these functions or pluin. is that also advisable for my situation?

https://actionscheduler.org/perf/
https://github.com/woocommerce/action-scheduler-high-volume

So far, I’m no longer experiencing any PHP warnings, so that seems to be resolved.

However, I’ve noticed that the plugin is no longer functioning as it should. The main product price does not change when I select a different variation. I’ve set only the “Crème” variation to have a discount, while the other variations have different prices. Yet, the displayed price remains the same when switching between variations.

It seems the issue lies with the display of the main product price.

This concerns the following product

Thanks in advance for looking into this!

Here’s a screenshot of the variation settings with the sale price:
[Link to screenshot] product link only the creme color is sale

And here’s a screenshot of the page where I’ve added the shortcode:
[Link to screenshot]

Additionally, I’ve included the system status of my site for more context:
[Link to system status report]

Thank you in advance for your help in resolving this issue.

Following up on my previous message: the reason I am asking about the synchronization of your plugin is related to my use of the Woosa vidaXL plugin. This plugin synchronizes products weekly, including stock, price, descriptions, and attributes.

I want to ensure that both plugins work correctly together, without conflicts or excessive server load

there sync cronjobs: https://prnt.sc/kaVkK5992fZD

• This reply was modified 1 month, 4 weeks ago by Mati.

Thank you for the helpful response and for explaining how the woocommerce_gla_batched_job_size filter works. I have a few follow-up questions about the synchronization process to better understand its behavior and identify optimization opportunities:

1. Incremental vs. Full Sync:
   • Does the plugin sync all products during every job, or does it intelligently handle only updated products (e.g., price, stock, or other changes)?
2. Batch Timing:
   • When processing batches (e.g., 500 products per batch), what is the typical time interval between each batch?
   • Is this timing configurable, or does it depend on server performance and resources?
   • Does the plugin pause between batches to reduce server load, or is it designed to process batches continuously until the sync completes?
3. Sync Triggers:
   • What events or conditions trigger a sync? For example, do manual updates, scheduled jobs, or specific product changes initiate synchronization differently?
   • Can we control or limit which events trigger a sync?
4. Sync Modes:
   • Are there different modes of synchronization (e.g., real-time, scheduled, or manual), and do they behave differently in terms of resource usage?
   • If so, which mode is recommended for stores with large catalogs to balance performance and accuracy?
5. Error Handling and Recovery:
   • If a sync is interrupted, does it resume from where it left off, or does it restart the entire process?
6. Batch Size Adjustment:
   • While the woocommerce_gla_batched_job_size filter is helpful, are there plans to add an option in the back-end to adjust the batch size? This would make it easier for users without coding knowledge.
   • Does the batch size affect the overall sync time significantly, and are there any risks in setting it too low (e.g., 100 products per batch)?

Here’s the code snippet I’m currently using to adjust the batch size. Could you confirm if this approach is ideal for stores of this size?

add_filter('woocommerce_gla_batched_job_size', function($size) { return 100; // Adjust the batch size to 100 products per job });

7. Performance Recommendations:
   • Are there server configurations or optimizations (e.g., increasing PHP memory limit, optimizing database queries) that you would recommend to handle large catalogs efficiently during sync?
   • Does the plugin benefit from specific caching mechanisms or database indexing to improve sync performance?
8. Future Enhancements:
   • Are there any upcoming features or enhancements planned to improve synchronization for stores with large catalogs? For example, options to prioritize specific products or optimize handling for unchanged data.

Thank you for your time and for helping the community tackle these challenges. I look forward to your insights and recommendations!

Hi,

I have updated the plugin let me test it. till now it works

luizaxl.nl/contact/

I am still encountering an error.

I am using the plugin with the correct client ID and have manually added the script to the body. Additionally, I am using two shortcodes:

• On the product page: [onsite_messaging data-key="credit-promotion-badge" data-theme="custom"]
• At the bottom of the mobile menu: [onsite_messaging data-key="top-strip-promotion-auto-size"]

However, I receive the following console error:
“Another Klarna Web SDK was already included in the page. Please consider using the data-client-instance-name attribute on the klarna.js script tag to avoid conflicts.”

If I remove the script from the body, the shortcode on the product page continues to work correctly, but the shortcode in the mobile menu no longer functions. Conversely, if I deactivate your plugin, the shortcode on the product page stops working, while the shortcode in the mobile menu works again.

This behavior suggests something isn’t configured correctly. Could you please investigate this issue?

thank!

for the php warning i used the shortcode placement i use custom product page [onsite_messaging data-key=”credit-promotion-badge”] i fergot to add “data-theme=”custom”” in de shortcod. i have add this to the shortcode and this whas the fix. thanx!

I think I found the problem. I just noticed that your plugin got a new look with a plugin update. Yesterday I looked in between and I also noticed that my country and Credentials were not filled in, while they were still there with the old plugin version. I placed the id and it works again. I will still keep an eye on it.

but in the debug list I still see the php warning and in the console the error with: Klarna Web SDK: The provided theme (mobile) is not a valid argument. Please use one of these valid values: default, dark, custom, light.