hefin
Forum Replies Created
-
Thank you, Takayuki, for your response. I appreciate the clarification that the contact form ID corresponds to the ID of the form. Apolgises for my misunderstanding.
Thanks for letting me know and putting a fix in unfortunately, I have upgraded the site to use version v2.0.2, but these errors still remain. Again disabling the plugin removes these errors
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home /public_html/wp-includes/functions.php on line 6114
Warning: Cannot modify header information - headers already sent by (output started at /home/ /public_html/wp-includes/functions.php:6114) in /home/public_html/wp-admin/includes/misc.php on line 1438
Warning: Cannot modify header information - headers already sent by (output started at /home/ public_html/wp-includes/functions.php:6114) in /home//public_html/wp-includes/functions.php on line 7137
Warning: Cannot modify header information - headers already sent by (output started at /home/ public_html/wp-includes/functions.php:6114) in /home /public_html/wp-admin/admin-header.php on line 9Mailster – Email Newsletter Plugin for WordPress (Premium) Version 4.1.6
Mailster for WooCommerce Version 2.0.2
WooCommerce Version 9.4.3
Forum: Plugins
In reply to: [Mailster for WooCommerce] No more Updates on This Plugin?Hi, I’d like to echo the concerns raised here. After upgrading my eCommerce site to WooCommerce 9.4.2, I began experiencing significant errors. Upon investigation, I found the following issues tied to Mailster for WooCommerce:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator of some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:6114) in /wp-admin/includes/misc.php on line 1438
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:6114) in /wp-includes/functions.php on line 7137
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:6114) in /wp-admin/admin-header.php on line 9I narrowed down the issue by deactivating all other plugins, leaving only Mailster for WooCommerce, and the errors persisted. I then finally deactivated Mailster for WooCommerce and the errors were removed.
This strongly suggests the plugin is not compatible with the latest WooCommerce update.Mailster Developers, please could you address this as soon as possible? It is becoming increasingly difficult to rely on this plugin without timely updates. Three months are passed since this issue was raised and still no updates and still the issue is persisting.
Thanks @israelmartins that answers my question. Appreciate your time and help.
That’s very helpful @ibrahimsharif that’s answers my question, that guide you have is helpful too. Thanks
Many thanks Jaime, additional CSS no worries!
I’m only using the free version at the moment.
Forum: Plugins
In reply to: [WooCommerce] Where are the Change logs gone!marking as resolved
Forum: Plugins
In reply to: [WooCommerce] Where are the Change logs gone!Found it, you select the version number!
Glad this hadn’t disappeared, just select the latest version and get a nice pop. Please ignore this support post, all good
Hi Sadia,
That’s great it worked! 🙂
I have a question regarding the pro version. If I purchase it, will it retain all of the customizations I’ve made? Initially, I plan to use the basic/free version of the plugin to synchronize with Google Merchant Centre. Once everything is running smoothly, we intend to upgrade to the PRO version.
Also, I’d like to know if we have already set up and are using the basic version, will upgrading to the PRO version require us to go through the setup process again?
According to your website, the pro version requires the installation of the plugin “best-woocommerce-feed-pro-6.4.1.zip.” Does this mean that I will need to uninstall the free version and install the pro version separately?
Many Thanks
HefinI just tried the slug name, it didn’t work 🙁
Hi Sadia
Thanks very much, setting the availability is equal to ‘outofstock’ worked. One last thing is that I don’t appear to be able to filter out product categories I’m trying to filter out the product category of ‘Sold Highlights’. I put in a rule if the condition is ‘Contains’ or ‘is eqaul to’ but neither work. I have a video here of what I’m doing
Thanks for your assistance
- This reply was modified 2 years, 10 months ago by hefin.
Thanks for getting back to me Sadia. I can’t get a simple product filter to apply. I’ve reduced the product filter to just attempt to exclude any out of stock products. I have a screen recording here showing what I’m doing
https://youtu.be/2wPhKh0iFIgI’m not translating the page at all, I’m definitly seeing a spelling mistake ‘Reguler Price’ as you can see in the video
Yeah, I agree that your design is good and safe. And I understand now why you wouldn’t want to delete the original files.
Thanks for your additional details if did want to experiment (of course at my own risk) interesting to know, might have a tinker on site locally.
Thanks for your response. Plugin is great BTW I’ll drop a 5 star review now. Thanks
Forum: Plugins
In reply to: [Debug Log - Manager Tool] Debug log not could not be opened !Just checked
<?php phpinfo();The error log is location is set to
error_log/home/<mysite>/logs/<site_url>.php.error.log
Would I need to set the log location back to wp-content directory for the plugin to pickup the error logs.
Many Thanks