Hi @nikkelsenr
I hope you are doing well today.
I made a test on my lab site with the Beds24 Online Booking plugin and I was not able to replicate this issue. Please note I tried to change different settings in that plugin and none of those triggered this error.
In the first place, this error sounds like some missing Forminator files after an update. Can you download the current Forminator version, log in to FTP replace all Forminator files and folders, and see will that gives positive results?
If that will not help, please export your form, upload it to Google Drive, and share a link in your next reply, so that we can test it on our side. Also, it will be good to give us a screenshot from this page on your site: /wp-admin/options-general.php?page=beds24-admin-menu (settings page). NOTE: Please blur or hide those values on that screenshot:
Beds24 Owner Id:
Beds24 Property Id:
Custom URL Parameters:
as this is public forum.
Kind Regards,
Kris
Hello Kris,
Thank you very much for your message! I am now one step further. I have now discovered that the error between Forminator and the Beds24 plugin only occurs if my “Kadence” theme is active at the same time. With a default WordPress theme “Twenty-Twenty-Four” the conflict between the two plugins does not occur.
Now it’s getting crazy: In the “Page Builder” of Kadence (Kadence Blocks) the popup (date field) can still be opened regularly. Even with a ready-made form from you. However, as soon as I switch to the live page for the visitor, the error described and the log in the console appear.
Unfortunately, replacing the files has not brought any improvement. Enclosed you will find the desired screenshot: https://ibb.co/7KXc3P0
In fact, the settings should also be the default setting. I work with the shortcode options of the plugin to get the booking widgets.
Best regards!
Niklas
Hi again @nikkelsenr
Please email us at: wpsupport@incsub.com
Subject: ATTN: WPMU DEV support – wp.org
Please send:
– Link back to this thread for reference (https://wordpress.org/support/topic/referenceerror-datepickerlang-is-not-defined/)
so that we can review this case more for you and see what will be possible in this case.
Kind Regards,
Kris
Hi @nikkelsenr,
Hope this message finds you well, and sorry to hear you are experiencing this issue.
We were able to reproduce the issue on our end too, it seems Beds24 Online Booking + Forminator + Theme builder (like Kadence, Elementor, and probably others) is creating a conflict, that is not only related to only Kadence.
In such a case, I escalated this conflict to our Second Line Support, they will check further and provide more information about it. Since they work on complex issues, getting a reply from them could take more time than usual, we will back to this topic once we get a reply from them.
Best regards,
Laura
Hi @nikkelsenr,
Could you please try this snippet and see whether it helps?
<?php
add_action( 'wp_enqueue_scripts', 'wpmudev_dequeue_beds24_datepicker', 9999 );
function wpmudev_dequeue_beds24_datepicker() {
global $post;
if ( is_a( $post, 'WP_Post' ) && ! has_shortcode( $post->post_content, 'forminator_form' ) ) {
return;
}
wp_dequeue_script( 'beds24-datepicker' );
}
You can implement the above code using mu-plugins. Please check this link on how to implement the above code as a mu-plugins:
https://wpmudev.com/docs/using-wordpress/installing-wordpress-plugins/#installing-mu-plugins
Please do note that it would be better to not use the Beds24 shortcode on pages where you already have the Forminator form due to the compatibility issues noticed.
Please do check and let us know how the above snippet goes.
Kind Regards,
Nithin
Hi Nithin,
sorry for the late reply. I was traveling without my computer and couldn’t test your code until today. I have successfully uploaded the “plugin” using the instructions you sent and now the date picker is working again as usual. Super! Will it stay with this workaround for the time being or will you try to bring a bug fix in one of the upcoming updates? I can live with it for now and thank you very much for your support in this case!
Many thanks and best regards from Germany!
– Niklas
Hi @nikkelsenr,
Glad to hear the snippet solved the issue.
The permanent fix will be coming in future releases, but, I am afraid we can’t provide which one or an ETA. Stil, please check the Changelog for future references.
Best regards,
Laura
