mathdaniel
Forum Replies Created
-
Hi,
We completely understand no worries at all.
In this case, we kindly ask you to get in touch with us through our official support portal so we can continue assisting you directly.
Please note that, due to community forum guidelines, we’re not allowed to request or share credentials, patches, or any sensitive information in this space.
We’ll be happy to continue supporting you once we’re in contact through the proper channel.
Best regards,
Peace!- This reply was modified 9 months, 2 weeks ago by mathdaniel.
- This reply was modified 9 months, 2 weeks ago by mathdaniel.
Forum: Plugins
In reply to: [Pre-Orders for WooCommerce] No e-mails sent after installing WPML part 2Hi @s7ors,
I hope you’re doing well.
Thanks for the information you’ve shared — it’s been helpful for understanding the context.
This case has already been passed to the development team and is now part of our internal review list. As part of our workflow, we evaluate each report in order, based on its overall relevance and benefit to all users.
We appreciate your input, and if there are any updates or confirmed adjustments related to this, we’ll be happy to share them here once clarified.
Best regards,
Peace!Hi @marisqa,
I hope you’re doing well.
I’m really sorry to hear about the issue you’re experiencing — we completely understand how frustrating it can be, and we truly appreciate you reaching out to us.
To assist you more efficiently, please follow these steps:
#1. On a test site with only our plugin, WooCommerce, and the Storefront theme active, try replicating the issue you mentioned. This will help us rule out any internal conflicts or issues with third-party plugins.
#2. Record a short screen capture showing the issue from the moment you configure your settings.You can use a free screen recording app like CloudApp or Loom.
Also, please include screenshots. This is especially important as it helps us understand the situation accurately and avoid any confusion.
Best regards,
Peace!- This reply was modified 9 months, 3 weeks ago by mathdaniel.
Hi @toddbenton,
Thank you for taking the time to explain everything in such detail.
We’ve already shared your case with the development team for internal evaluation. As we usually do, each situation is reviewed based on its overall impact and how it fits within the plugin’s structure.
We truly appreciate your input. If there are any updates regarding this in the future, we’ll be happy to share them here.
Best regards,
Peace!Hi @matmayer,
Thank you for your update, and we fully understand your decision.
This notice was indeed triggered by changes introduced in WordPress 6.7 and is something we already had on our roadmap prior to this thread. As mentioned earlier, we’ve planned to update the translation loading method in the next release to comply with the new standard.
We also appreciate the contribution shared by @eisteed as a temporary fix for those who wish to address the notice immediately.
Even though you’ve switched plugins, we thank you for having used ours and for your valuable feedback. Your comments help us improve and better support the community.
Wishing you continued success with your project.
Best regards,
Peace!Hi @hendrikhere,
Thank you again for following up over this time.
We completely understand your concern. Both issues you mentioned (the empty payment options display and the behavior of the “Paid Status” toggle) were carefully reviewed and passed on to the development team as part of our internal planning sessions.
These points are currently still under evaluation for potential future improvements. As you may know, we work in development sprints, and each reported case is assessed based on its overall impact and alignment with the plugin’s direction. While we can’t offer a specific timeline, we want to assure you that your feedback has not been ignored.
We’d also like to mention that many advanced features—typically available only in premium versions—are provided for free in our plugin.
We sincerely appreciate your input and the clarity with which you explained the situation. If any related improvement is included in a future release, we’ll be happy to share it here.
Best regards,
Peace!- This reply was modified 9 months, 3 weeks ago by mathdaniel.
Hi everyone,
Thank you so much for taking the time to share your tests, experiences, and possible solutions. We understand that stock behavior can be sensitive depending on each store’s workflow, and we truly appreciate the level of detail you’ve all provided.
From the support side, this information has already been forwarded to the development team for review. As part of our process, each case is evaluated based on its overall impact and how it aligns with the current structure of the plugin.
A new version is currently in the works, and within that context, certain related behaviors are being reviewed.
We want you to know that the team is working with everyone’s benefit in mind.
We’ll remain attentive to any further comments, and once again, thank you for your collaboration.
Best regards,
Peace!Hi,
Hope you’re doing well.
Thank you for sharing this case. What you mentioned has already been passed on to the development team for internal evaluation.
As part of our workflow, we assess each suggestion based on the value it may bring to all plugin users. If there are any updates regarding this in the future, we’ll be happy to share them here.
Best regards,
Peace!Hello,
I hope you’re doing well.
We’re glad to hear that the plugin has been useful to you — thank you for your kind words!
We truly appreciate the time you took to share this feature suggestion. Your idea is valuable, and our team will review it carefully to evaluate its potential usefulness for the broader community.
We’ve already added your request to our internal review pipeline for further consideration.
Wishing you a great day ahead!
Best regards,
Peace!Hello,
Thank you for reporting this notice and for providing detailed information.
This issue is related to a change introduced in WordPress 6.7, where a PHP notice is now triggered if the plugin loads its translation domain before the init hook. This is part of new validation logic added to improve internationalization (i18n) handling and ensure that translations are loaded at the correct time.
You can find more details in the official WordPress core update here:
(more information here)
While this notice does not affect the functionality of the plugin, we understand that it can clutter your debug. log , especially during development. We’ve already planned to adjust the translation loading point (bp-custom-order-status) to ensure full compatibility with the updated WordPress standards.We truly appreciate your feedback. This fix will be included in an upcoming release, and we’ll keep you posted.
Best regards,
Peace!- This reply was modified 10 months, 1 week ago by mathdaniel.
We understand.
To provide you with the best support, please follow these instructions:
#1. On a test site with only our plugin, WooCommerce, and the Storefront theme, you can perform the test you mentioned. This way, we can rule out internal conflicts or issues with third-party plugins.
#2. If the behavior persists, please record a step-by-step clip demonstrating your issue so we can reproduce it if necessary. To record a video of the problem you are experiencing, use a free screen recording application like CloudApp or Loom.
Let us know how it goes.
Best regards, peace!
Hello, @nikkiusky25
I hope you are well.
Thank you for your message and for sharing the screenshot; it has been very helpful.
We have noticed that in your current settings, the “Status View” option is set to “Status Name,” which only displays the text of the status in the orders list.
To display the icon instead, simply change that option to “Status Icon” in the dropdown menu. This way, the selected icon will replace the name in the status column.
We are here if you need help with anything else.
Best regards, peace!
Forum: Plugins
In reply to: [Pre-Orders for WooCommerce] DokanHello,
I hope you are well!
As we haven’t received a recent response, I’ll mark this as resolved.
Feel free to open a new ticket, if you continue encountering issues or reopen this ticketWe’d be happy to assist. Thank you!
Best regards, peace!
Forum: Plugins
In reply to: [Custom Order Status Manager for WooCommerce] TranslationHello,
I hope you’re doing well.
Thank you for reaching out. Indeed, Loco Translate can only translate static strings that are directly defined in the code. In this case, the string “Change status to” is generated dynamically, so it is technically not recognized as a translatable string by Loco Translate and therefore does not appear in the language files.
However, we already have plans to adjust this part of the code so that the string becomes translatable in an upcoming plugin update.
Let us know if you need anything else.
Best regards,
Peace!Hello,
Thank you for reporting this notice. It is related to a recent change in WordPress 6.7, which now triggers a warning if translations are loaded before the init hook. This is not an error exclusive to the plugin, but rather an adjustment introduced by the core (more information here).
As we mentioned, we have already planned to adjust the loading point of the translation domain in an upcoming version.
We appreciate your input regarding this matter.
We remain available for any questions or contributions.
Best regards, peace!