Archinformatique
Forum Replies Created
-
In fact, that’s what’s causing the bug. Phew because I had a lot of articles with MetaSlider. Having said that, as Elementor is currently undergoing a major change, I’m going to use the WP option to insert shortcodes MetaSlider. On another note, thank you again for taking so much time over my problem. It’s really nice
Have a nice festive seasonHi : https://h24media.com/test/
This works with MetaSlider and Text, but not with Text Editor. I hope the screenshots will make it easier for you to understand, even if they’re not great.
Don’t work with this
Hi Yes, but it’s precisely when I do that that it doesn’t work. It works in 2 ways: the ‘simple’ WP text editor and WP MetaSlider. At the risk of repeating myself, it worked perfectly before with the Elementor text editor and I inserted the code directly…
Hi,
But I don’t have any features that block the REST API. The only one I have is in All In One WP Security and the box is not ticked. However, I think I’ve found it… after a lot of searching. When I create a layout with Elementor I use the text editor in which I insert the MetaSlider shortcode and that’s where it doesn’t work. In fact, the MetaSlider logo appears but when I click on it to insert the shortcode without having to copy the code, a blank page opens up. However, if I use the ‘simple’ WP text editor and insert the code, it works perfectly. So it’s an incompatibility between MetaSlider and the text editor offered by Elementor, I believe. And this has been the case since the last Elementor update. Knowing that I had tested by deactivating all the plugins. What do you think ? I hadn’t seen the possibility of inserting MetaSlider with WP and it works perfectly… That’s why we didn’t understand each other… sorry
- This reply was modified 1 year, 5 months ago by Archinformatique.
Hi,
I wish you could have reproduced the bug… :). This is rather strange as everything was working correctly until now. Here is a link to an article where MetaSlider works perfectly and if you refresh the page it disappears : https://h24media.com/lelysee-annonce-que-le-nouveau-premier-ministre-sera-designe-vendredi-matin/A another eg. : https://h24media.com/cyclone-chido-a-mayotte-bruno-retailleau-sur-le-terrain/
Hello
Actually True, I didn’t do it. It’s the automatic update!… Thank you for your reply. Looking forward to the new version!
👍
8.0
Yes of course (with false only)
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the
ml-sliderdomain 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/clients/client0/web4/web/wp-includes/functions.php on line 6114Hi,
Yes, but 🙂 it’s the “same” with MetaSlider. Just replace Yoast Seo with MetaSlider.
The solution is : you can define( ‘WP_DEBUG’, false ) in wp-config.php. Of course you know this.
Especially since this is a “bug” when the WP update is done automatically and not manually…And the WP documentation refers to one of the doc of version 6.7
I’d like to take this opportunity to tell you that MetaSlider works perfectly and renders very nicelyBest Regrads
To stop seeing this message while waiting for support, you can define( ‘WP_DEBUG’, false ) in wp-config.php if you know how;
To stop seeing this message while waiting for support, you can define( ‘WP_DEBUG’, false ) in wp-config.php if you know how;
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the
wpr-addonsdomain 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/clients/client0/web4/web/wp-includes/functions.php on line 6114Fatal error: Uncaught Error: Call to undefined function wpr_fs() in /var/www/clients/client0/web4/web/wp-content/plugins/royal-elementor-addons/admin/plugin-options.php:1634 Stack trace: #0 /var/www/clients/client0/web4/web/wp-includes/class-wp-hook.php(324): wpr_addons_add_upgrade_menu() #1 /var/www/clients/client0/web4/web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /var/www/clients/client0/web4/web/wp-includes/plugin.php(517): WP_Hook->do_action() #3 /var/www/clients/client0/web4/web/wp-admin/includes/menu.php(161): do_action() #4 /var/www/clients/client0/web4/web/wp-admin/menu.php(412): require_once(‘…’) #5 /var/www/clients/client0/web4/web/wp-admin/admin.php(158): require(‘…’) #6 /var/www/clients/client0/web4/web/wp-admin/plugins.php(10): require_once(‘…’) #7 {main} thrown in /var/www/clients/client0/web4/web/wp-content/plugins/royal-elementor-addons/admin/plugin-options.php on line 1634
Hello
In fact there are two “bugs”. The first is RA incompatibility with the latest version of Elementor & Elementor Pro. This requires an update of RA. And there’s a problem with access rights to the model with Elementor. You can follow the progress with this link: https://status.elementor.com/
Wait and see