🐞 Bug report: Instant.js #18885
Comments
|
Hi @nathansimons , I followed your "Steps to reproduce" could not find the issue. P.S. if it's an Elementor bug, we need steps to recreate it in other Elementor sites. Otherwise, we won't be able to find the bug and fix it. If it's and issue on your site, it's not a necessary an Elementor bug. |
|
I am also experiencing this error on the admin side when loading the Elementor editor. This causes the editor not to fully load and the
|
|
Hi @fatimaburke As mentioned above, we need "Steps to reproduce" to recreate the issue in other environments. If we cant recreate the issue in other sites, we won't be able to fix the issue, as it can be a unique case for your site. Maybe one of the Elementor Addons, one of the WordPress plugins or a bas server configuration. |
|
I have same issue. I can confirm that it's related to Elementor's page transitions & preloader feature. If I disable this features, then there is no error. Please check it. |
|
+1 - This is happening with the Page Transitions. |
|
@rami-elementor Steps to reproduce:
This is because instant-page.min.js is trying to declare const |
|
Same issue here |
|
Same issue here.... Uncaught SyntaxError: Identifier 'a' has already been declared (at instant-page.min.js?ver=3.7.5:1:1) |
|
Got the same issue. But when i deactivated a 3rd party plugin related to elementor, it is working. |
|
just go in general => permalink and revalidate your permalink and the problem is solved normaly |
|
I got this when adding the plugin "Royal Elementor Addons". |
|
I can confirm Page Transitions create this error. Disabling them “fixed it”. |
|
Same problem and same solution, disabling Page Transitions in Elementor/Settings/Experiments. Elementor 3.81 with Elementor Pro 3.8.0. |
|
6 months later, still open? |
|
I am also facing this issue, I can also confirm that Page Transitions create this error. Disabling them “fixed it”. |
|
I can confirm Page Transitions create this error. Disabling them “fixed it”. |
|
confirm Page Transitions create this error. Disabling them “fixed it”. |
|
I am surprised that such an experiment team as Elementor cannot figure out this issue after nearly a year! I am also experiencing the same error (I use Elementor Pro), I am not complaining but it's really disappointing to see plugin developers more concentrating on developing new features rather than to fix existing bugs/issues to make the system better... |
|
May 2023 and the error still persists, it still occurs when using page transitions. Disabling this feature prevents the error, but it is a necessary feature for me. I hope the Elementor team pays attention to this long-standing bug. |
|
I can confirm Page Transitions create this error. Disabling them “fixed it”. |
|
Disabling and fixed... |
|
@rami-elementor @nicholaszein Please check into this again! |
|
We have the same issue with v4-shims.min.js, any way to disable the v4-shims.min.js file? |
|
It's now July 2023 and the error is still persisting, despite the fact that it gets resolved when the Page transition is disabled. @rami-elementor, instead of continuously saying that you cannot reproduce the error and therefore cannot assist, it would be more proactive to request temporary access to a staging environment and investigate the issue yourself. That's a normal procedure for all the plugin troubleshooting. Really dissapointing! |
|
Same issue here ... +1 It's disappointing how the Elementor development team handles issues like this. We are a small marketing agency, and this is our first Elementor site. We are thinking about switching from Gutenberg to Elementor. But since the support team doesn't seem to care about our problems, I'm not sure it's a good idea anymore. |
|
Same issue here ... +1 |
|
ran into this issue with the Theme Builder templates (regular pages were fine). Editor would not load. |
|
I got the same problem, after enabling the DEBUG mode, I found out it was caused by a "lack of memory". This is the debug log:
I simply changed my hosting plan and added more memory and the issue was resolved. Hope it helps. |
This bug is about a client-side JS error. Your solved problem must be unrelated, @emami-io . As for this issue, proof it can be solved by wrapping the instant.page plugin in an IIFE (it's honestly amazing it isn't already by that script's dev): Find Voila, no more error. Obviously this file will be overwritten upon update of Elementor, and thus your change reverted, which is why the Elementor devs should fix this. @rami-elementor Also, why is instant.page js when set to active/default only active on Elementor editing pages? Anyway, I'm disabling this Elementor feature. |
|
Looks like no one from Elementor has looked at this unresolved bug and ongoing issue since rami-elementor on Jul 20, 2022??? I am also seeing this error in the browser console when I try to edit certain pages ("edit with Elementor"). The error goes away when I switch off the "Page Transition" feature. |
It's honestly ridiculous, especially considering how easy it was to find the problem & fix it (see my previous comment). |
|
I have tried the fix of @youri-- without result We have this bug at all update of Elementor, it take my time every time... |
I'm quite confident my fix works. The browser console messages point to that file and the problem of a global variable that script tries to use. After my quick fix, the visual editor pages where that error occurred, no longer suffered the instant page error. Although I'm not here to offer support in lieu of Elementor, I'll tell you this: if it doesn't work for you, it's more than likely a caching issue, where the old, unedited version is still being loaded. Make sure any site caching (CDN, WP Super Cache, Autoptimize, etc) is cleared, as well as (lastly) your browser cache. In any case, it's still not permanent, because the fix will be overwritten with the next update. |
|
I have disabled this parameter in "settings/advanced" and it's fixed. |
Yep, that works. I did same, because of the update issue. |
I can confirm that @youri-- solution does indeed work. I've had this error in the console for quite some time too, never knew what caused it. Thanks @youri--! P.S - Make sure you're editing the minified instant-page JS file, and also that you're adding |
|
Thank @Selah1337 but in my case I prefer to disable this broken feature. ;-) |
|
I can confirm that this persistent problem occurs when Page Transitions are active and disappears when Page Transitions are disabled. I'm thrilled that the Elementor dev team are taking this issue seriously and... oh, I see, never mind. |
|
This is happening to me after applying @youri-- fix. Also turned off Page Transitions, problem still persists. The only error that I am having is a 500 error when sending an ajax request. action: elementor_ajax My site is hosted with Flywheel. Support increased the memory to the hosting server to 512M which resolved the issue. Perhaps disclosing a minimum system requirements is necessary to avoid this issue. |
Not caused by this bug, nor by the fix. The problem described in this thread is with client-side JavaScript. That has nothing to do with PHP memory_limit on the server. Sounds like you have a "heavy load" site, requiring a lot of RAM, or perhaps one or more shoddily written plugins (unfortunately there are many), causing memory to fill up beyond what's reasonable. So your response is off-topic, glad you got your issue sorted though. |
and others
Prerequisites
Description
There is a js error in the console. I have tested by disabling all plugin but it still persists.
Error: Uncaught SyntaxError: Identifier 'a' has already been declared (at instant-page.min.js?ver=3.7.1:formatted:1:1)
Steps to reproduce
Click here: https://scheckterspeed.co.za/steps-to-sell-your-car/
Inspect page
View console
Isolating the problem
System Info
== Server Environment ==
Operating System: Linux
Software: Apache
MySQL version: mariadb.org binary distribution v10.4.25
PHP Version: 7.4.29
PHP Memory Limit: 96M
PHP Max Input Vars: 5000
PHP Max Post Size: 128M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected
== WordPress Environment ==
Version: 6.0
Site URL: https://scheckterspeed.co.za
Home URL: https://scheckterspeed.co.za
WP Multisite: No
Max Upload Size: 128 MB
Memory limit: 40M
Max Memory limit: 1024M
Permalink Structure: /%postname%/
Language: en-ZA
Timezone: Africa/Johannesburg
Admin Email: support@scheckterspeed.co.za
Debug Mode: Inactive
== Theme ==
Name: Twenty Twenty-One Child
Version: 1.0.0
Author: Elicus Technologies
Child Theme: Yes
Parent Theme Name: Twenty Twenty-One
Parent Theme Version: 1.6
Parent Theme Author: the WordPress team
== User ==
Role: administrator
WP Profile lang: en_ZA
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36
== Active Plugins ==
Advanced Custom Fields
Version: 5.12.2
Author: Delicious Brains
== Must-Use Plugins ==
ManageWP - Worker Loader
Version: 1.0.0
Author: GoDaddy
== Elements Usage ==
== Elementor Experiments ==
Optimised DOM Output: Active by default
Improved Asset Loading: Active by default
Improved CSS Loading: Active by default
Inline Font Icons: Inactive by default
Accessibility Improvements: Active by default
Import Export Template Kit: Active by default
Additional Custom Breakpoints: Active by default
Hide native WordPress widgets from search results: Active by default
: Inactive by default
Flexbox Container: Inactive by default
Default to New Theme Builder: Active by default
Landing Pages: Active by default
Colour Sampler: Active by default
Favorite Widgets: Active by default
Admin Top Bar: Active by default
Page Transitions: Active by default
Notes: Active by default
Form Submissions: Active by default
Scroll Snap: Active by default
== Log ==
Log: showing 20 of 302022-05-10 14:42:04 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor Pro',
'from' => '3.6.5',
'to' => '3.7.0',
)]
2022-05-10 14:42:04 [info] elementor-pro::elementor_pro_updater Started
2022-05-10 14:42:04 [info] Elementor Pro/Upgrades - _on_each_version Start
2022-05-10 14:42:05 [info] Elementor Pro/Upgrades - _on_each_version Finished
2022-05-10 14:42:05 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor Pro',
'from' => '3.6.5',
'to' => '3.7.0',
)]
2022-05-18 10:20:58 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor Pro',
'from' => '3.7.0',
'to' => '3.7.1',
)]
2022-05-18 10:21:05 [info] elementor-pro::elementor_pro_updater Started
2022-05-18 10:21:05 [info] Elementor Pro/Upgrades - _on_each_version Start
2022-05-18 10:21:05 [info] Elementor Pro/Upgrades - _on_each_version Finished
2022-05-18 10:21:05 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor Pro',
'from' => '3.7.0',
'to' => '3.7.1',
)]
2022-05-18 10:21:07 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor Pro',
'from' => '3.7.0',
'to' => '3.7.1',
)]
2022-05-18 10:21:07 [info] elementor-pro::elementor_pro_updater Started
2022-05-18 10:21:08 [info] Elementor Pro/Upgrades - _on_each_version Start
2022-05-18 10:21:08 [info] Elementor Pro/Upgrades - _on_each_version Finished
2022-05-18 10:21:08 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor Pro',
'from' => '3.7.0',
'to' => '3.7.1',
)]
2022-06-08 17:03:39 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.6.5',
'to' => '3.6.6',
)]
2022-06-08 17:03:40 [info] elementor::elementor_updater Started
2022-06-08 17:03:41 [info] Elementor/Upgrades - _on_each_version Start
2022-06-08 17:03:43 [info] Elementor/Upgrades - _on_each_version Finished
2022-06-08 17:03:44 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor',
'from' => '3.6.5',
'to' => '3.6.6',
)]
PHP: showing 6 of 6PHP: 2022-05-09 11:58:09 [notice X 15][/usr/www/users/scheccwfwb/wp-content/plugins/elementor/core/common/modules/ajax/module.php::171] Undefined index: data [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2022-05-10 14:42:45 [notice X 141][/usr/www/users/scheccwfwb/wp-content/plugins/elementor/modules/dev-tools/deprecation.php::301] The $control_id argument is deprecated since version 3.5.0! [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> rest_error_handler()
#1: /usr/www/users/scheccwfwb/wp-content/plugins/elementor/modules/dev-tools/deprecation.php(301): class type trigger_error()
#2: /usr/www/users/scheccwfwb/wp-content/plugins/elementor/includes/managers/controls.php(523): Elementor\Modules\DevTools\Deprecation -> deprecated_argument()
#3: /usr/www/users/scheccwfwb/wp-content/plugins/elementor/includes/managers/controls.php(501): Elementor\Controls_Manager -> register()
#4: /usr/www/users/scheccwfwb/wp-content/plugins/visibility-logic-elementor/core/helpers/Controls.php(74): Elementor\Controls_Manager -> register_control()
',
)]
PHP: 2022-05-10 14:43:30 [notice X 1022][/usr/www/users/scheccwfwb/wp-content/plugins/elementor/modules/dev-tools/deprecation.php::301] The $control_id argument is deprecated since version 3.5.0! [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2022-05-10 14:47:36 [notice X 8][/usr/www/users/scheccwfwb/wp-content/plugins/elementor/includes/managers/image.php::81] Undefined offset: 2 [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2022-05-12 15:55:10 [error X 1][/usr/www/users/scheccwfwb/wp-content/plugins/elementor-pro/modules/notes/usage.php::161] Uncaught Error: Call to a member function format() on null in /usr/www/users/scheccwfwb/wp-content/plugins/elementor-pro/modules/notes/usage.php:161
Stack trace:
#0 /usr/www/users/scheccwfwb/wp-content/plugins/elementor-pro/modules/notes/usage.php(43): ElementorPro\Modules\Notes\Usage->get_first_interaction()
#1 /usr/www/users/scheccwfwb/wp-content/plugins/elementor-pro/modules/notes/usage.php(27): ElementorPro\Modules\Notes\Usage->get_usage_data()
#2 /usr/www/users/scheccwfwb/wp-includes/class-wp-hook.php(307): ElementorPro\Modules\Notes\Usage->ElementorPro\Modules\Notes{closure}(Array)
#3 /usr/www/users/scheccwfwb/wp-includes/plugin.php(189): WP_Hook->apply_filters(Array, Array)
#4 /usr/www/users/scheccwfwb/wp-content/plugins/elementor/includes/tracker.php(563): apply_filters('elementor/track...', Array)
#5 /usr/www/users/scheccwfwb/wp-content/plugins/elementor/includes/tracker.php(141): Elementor\Tracker::get_tracking_data(false)
#6 /usr/www/users/scheccwfwb/wp-includes/class-wp-hook.php(307): Elementor\T [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2022-06-01 13:43:45 [notice X 2][/usr/www/users/scheccwfwb/wp-content/plugins/elementor-pro/modules/query-control/module.php::748] Trying to get property 'name' of non-object [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
JS: showing 6 of 6JS: 2022-05-10 11:19:27 [error X 1][https://scheckterspeed.co.za/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.6.5:2:310649] Cannot set properties of undefined (setting 'footerSaver')
JS: 2022-05-12 11:25:20 [error X 3][https://scheckterspeed.co.za/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.6.5:2:242684] Cannot read properties of undefined (reading 'html')
JS: 2022-05-12 11:34:48 [error X 1][https://scheckterspeed.co.za/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.6.5:2:406153] Cannot read properties of null (reading 'id')
JS: 2022-05-12 15:16:12 [error X 1][https://scheckterspeed.co.za/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: "view1844") has already been destroyed and cannot be used.
JS: 2022-06-01 11:27:14 [error X 1][https://scheckterspeed.co.za/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.6.5:2:344386] NProgress is not defined
JS: 2022-06-01 11:32:07 [error X 1][https://scheckterspeed.co.za/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.6.5:2:335004] Blocked a frame with origin "https://scheckterspeed.co.za\" from accessing a cross-origin frame.
== Elementor - Compatibility Tag ==
== Elementor Pro - Compatibility Tag ==
The text was updated successfully, but these errors were encountered: