Mark
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] Transients expiringHi @litetim
Thank you! The issue has indeed been resolved in this new version. Also, in the mean time my host has restored the Redis cache connection.
All is fine again! Thanks for the help!
Regards,
Mark
Forum: Plugins
In reply to: [LiteSpeed Cache] Transients expiringHi @hailite ,
Thanks for providing the beta release. The transient issue seems resolved on my website. Page load times are back at approximately 1 second with OC enabled and all settings as usual.
I’ll keep using this version until the official release is available!
Thanks again and kind regards,
Mark
Forum: Plugins
In reply to: [WPC Grouped Product for WooCommerce] Pre-sale questionHi @janilyn409,
Thank you for getting back to me. Thank you for referring me to your other plugin, that is indeed exactly what we’re looking for. Especially with the possibility to bundle different products together in fixed quantities and with stock management based on the “product availability” for each individual product. I’ve read through your documentation and as far as I can tell that’s exactly what we need.
Thanks again!
Regards, Mark
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] Mollie plugin critical errorHello @femiyb
Obviously I’m not showing debug logs on screen on the live site. I merely pointed out to you that if you would like to see the on-screen error logs, please visit the staging website at staging.avstyle.nl.
Besides the errors in the debug log, this issue is causing critical errors on a regular basis on the live site. Can you provide me with a rough estimate for a timeline on this? So that I can inform the website owner.
Thanks for your time and effort!
Regards,
MarkForum: Plugins
In reply to: [Mollie Payments for WooCommerce] Mollie plugin critical errorHello Femi,
Thanks for looking into it. Do you need access to the staging website to investigate further? That saves you the hassle of trying to reproduce it. If so, please let me know how I can securely (privately) send it to you. Below is part of the debug.log file. Hope this helps.
Kind regards,Mark
—–
[07-Feb-2025 11:30:21 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the
mollie-payments-for-woocommercedomain 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 theinitaction or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-includes/functions.php on line 6114
[07-Feb-2025 11:30:21 UTC] PHP Fatal error: Uncaught Error: Call to a member function filter_translation_status() on null in /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-content/plugins/sitepress-multilingual-cms/addons/wpml-page-builders/classes/Shared/tm/class-wpml-tm-page-builders.php:318
Stack trace: 0 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-content/plugins/sitepress-multilingual-cms/addons/wpml-page-builders/classes/Shared/tm/class-wpml-tm-page-builders-hooks.php(91): WPML_TM_Page_Builders->link_to_translation_filter(‘https://avstyle…’, 7, ‘nl’, ‘7’) 1 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-includes/class-wp-hook.php(324): WPML_TM_Page_Builders_Hooks->link_to_translation_filter(‘https://avstyle…’, 7, ‘nl’, ‘7’) 2 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘https://avstyle…’, Array) 3 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(149): apply_filters(‘wpml_link_to_tr…’, ‘https://avstyle…’, 7, ‘nl’, ‘7’) 4 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-includes/class-wp-hook.php(324): WPML_URL_Filters->get_edit_post_link(‘https://avstyle…’, 7, ‘display’) 5 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘https://avstyle…’, Array) 6 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-includes/link-template.php(1499): apply_filters(‘get_edit_post_l…’, ‘https://avstyle…’, 7, ‘display’) 7 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-content/plugins/mollie-payments-for-woocommerce/src/PaymentMethods/Applepay.php(25): get_edit_post_link(Object(WP_Post)) 8 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-content/plugins/mollie-payments-for-woocommerce/src/PaymentMethods/AbstractPaymentMethod.php(153): Mollie\WooCommerce\PaymentMethods\Applepay->getFormFields(Array) 9 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-content/plugins/mollie-payments-for-woocommerce/src/Gateway/MolliePaymentGateway.php(174): Mollie\WooCommerce\PaymentMethods\AbstractPaymentMethod->getAllFormFields() 10 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-includes/class-wp-hook.php(324): Mollie\WooCommerce\Gateway\MolliePaymentGateway->init_form_fields(”) 11 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) 12 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 13 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-settings.php(704): do_action(‘init’) 14 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-config.php(97): require_once(‘/var/www/vhosts…’) 15 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-load.php(50): require_once(‘/var/www/vhosts…’) 16 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-blog-header.php(13): require_once(‘/var/www/vhosts…’) 17 /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/index.php(17): require(‘/var/www/vhosts…’) 18 {main}thrown in /var/www/vhosts/rebelwithatwist.nl/avstyle.nl/wp-content/plugins/sitepress-multilingual-cms/addons/wpml-page-builders/classes/Shared/tm/class-wpml-tm-page-builders.php on line 318
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] Mollie plugin critical errorHi Femi,
Thank you. My website uses WPML (main plugin), String Translation, Media Translation and WPML WooCommerce Multilingual.
The main language is Dutch and the secondary language is English. They are split by different domains (avstyle.nl pointing to the Dutch version and avstyle.com to the English version).
Let me know if you need additional information or access to the staging website to investigate further. The staging version is located at staging.avstyle.nl and has debugging enabled on-screen.
Thanks again and kind regards,
Mark
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] Mollie plugin critical errorHi Femi,
Thanks for getting back to me. WordPress, WooCommerce and all other plugins and themes are up-to-date. I’m running versie 7.9.1 (latest as far as I can see?) and there are no updates available according to the WordPress dashboard. When enabling WP_DEBUG the screen is filled with a few error messages, including:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the
mollie-payments-for-woocommercedomain 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 theinitaction or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/rebelwithatwist.nl/staging.avstyle.nl/wp-includes/functions.php on line 6114Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/vhosts/rebelwithatwist.nl/staging.avstyle.nl/wp-includes/formatting.php on line 2819
Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/vhosts/rebelwithatwist.nl/staging.avstyle.nl/wp-includes/formatting.php on line 2819
Etc, etc…
Check for reference: https://ibb.co/21QbQsnB and https://ibb.co/bgCzfjRp
The same error was generated for two other plugins and I’ve notified the applicable developers. Any suggestion on how to fix this? Apparently the issue should have been fixed in version 7.9.1, but I’m still getting these error messages and according to WPML developers this is possibly the root cause for other conflicts on my website.
Thanks again!
Mark- This reply was modified 1 year, 3 months ago by Mark. Reason: added another screenshot
Hi Kokomo,
Thanks for getting back to me and sorry to keep you waiting. For some reason I did not get a notification about your reply.
The mail client supports both semicolon and comma, but for some reason does not separate the e-mails automatically. I found a workaround by accident; selecting all the mail addresses and then deselecting them, makes the mail client rearrange the mail addresses and separates them. So it does seem to be a bug in the mail client in stead of your plugin. Sorry for the inconvenience. This topic may be closed.
Thanks again and kind regards,
MarkHi @miemie,
Thank you for getting back to me and for taking my suggestions into consideration.
I’m looking forward for any future updates.
Kind regards,
MarkForum: Plugins
In reply to: [Contact Form 7] How to disable/exclude specific day in date-pickerHi Erik,
Sorry for the long wait. I was enjoying some family time for a couple of days. Thank you for all your effort, input and references. I’ve learned a lot and it now works the way we wanted to:-)
Have a nice day and thanks again!
Mark
Forum: Plugins
In reply to: [WooCommerce] Wrong products showing on category pageHi @rainfallnixfig ,
Thanks for getting back to me. It is indeed an issue with the Astra Pro theme, the storefront theme does not show this problem. Next time I’ll try this first, sorry for the mishap.
I’ve contacted the Astra support team.
Kind regards,
MarkForum: Plugins
In reply to: [Contact Form 7] How to disable/exclude specific day in date-pickerJust one more question. If they want to disable another day in the future, let’s say Monday and Tuesday. How would that affect the javascript you provided?
Kind regards,
MarkForum: Plugins
In reply to: [Contact Form 7] How to disable/exclude specific day in date-pickerHi Erik,
I’ve placed this code
#ui-datepicker-div td { padding: 0; }in the custom CSS area which overwrites the normal CSS file. This works like a charm! Thank you so much:-)
Regarding the default datepicker i found the following solution which works for me if you check https://www.cafededokter.nl/reserveren/ on your phone. I changed your input type from “date” to “text” and added the readonly attribute:
[text* your-date id:datepicker readonly placeholder "Datum*"]I noticed your piece of CSS
input[type="date"]::-webkit-calendar-picker-indicator { -webkit-appearance: none; }which refers to “date” input type. It does not seem to influence the form in any way but maybe you can clarify this?
Once again thanks for all your help!
Kind regards,
MarkForum: Plugins
In reply to: [Contact Form 7] How to disable/exclude specific day in date-pickerHi Erik,
Thanks again for all the effort you’re putting into this! The datepicker works, however there are two small issues still. Maybe you can help me figure what’s going wrong.
First, the Saturday’s are falling outside the datepicker ‘grid’. Check https://ibb.co/0hXwfwH for a screenshot or you can find the original page here: https://www.cafededokter.nl/reserveren/
Second, on iPhones the default iOS (i think?) datepicker is showing up first. You can select any Tuesdays, but after using the default datepicker, your datepicker pops up and the Tuesdays are greyed out like it should.
Any suggestions on this? Most likely the first has to do with the theme styling sheets. I can approach them to check if they have specific CSS set for the datepicker somewhere.
Kind regards and thanks again,
MarkForum: Plugins
In reply to: [Contact Form 7] How to disable/exclude specific day in date-pickerHi Erik,
Thanks again. I tried putting the code within the wrapper you just provided, but unfortunately without success. Probably I’m just making a rookie mistake..
I would appreciate the help. Can I sent you a DM somehow to provide you with a temporary username and password so you can take a look?
Kind regards,
Mark