Uncaught TypeError: Cannot read property 'currentView' of undefined #3926
Comments
|
It's the same on my site, just after the update. |
|
Please contact with us in support at elementor.com |
|
I get the same issue. Can I downgrade to resolve the issue? |
|
@localhost80 Yes! |
|
Same issue, how do we downgrade? There's no information in your docs that I can find :/ |
|
Yo bro. I did but its all messed up. I will wait for update. |
|
You can download previous releases in github. its not working for me. |
|
Ahh right, rolling back to 1.9.8 fixed it for me. |
|
going to try that. 2.0.xx not working
… On Mar 27, 2018, at 11:37 AM, Gavin Coulson ***@***.***> wrote:
Ahh right, rolling back to 1.9.8 fixed it for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Just download this file and replace with your own: https://plugins.svn.wordpress.org/elementor/tags/2.0.0/assets/js/editor.min.js |
|
going to wait for the release. the downgrade worked. its groovy KingYes. |
|
Worked for me thanks @KingYes thanks |
|
@KingYes Great! it worked here |
|
Some of my subscribers have the same troubles. |
|
Please update to 2.0.2!!! Thanks for reporting. |
|
same bug again on other versions (2.0.x)
|
|
Hello, I have similar problem with a message
I roll back to Elementor version 2.0.0 as suggested in this topic, it works. |
|
@KingYes please reopen this issue |
|
Same issue after update to the latest. editor.min.js?ver=2.0.12:2 Uncaught TypeError: Cannot read property 'data' of undefined |
|
Having same issue on Version 2.0.14. |
|
Same on 2.0.15 with Elementor Pro 2.0.10 with this message I have 3 different scenarios
Still can't find out why it sometimes works or crash |
|
@KingYes can you please open this issue ? |
|
Juste updated to Elementor 2.0.16 with v. Pro 2.0.11, same issue. |
|
If anyone is having issues with it and single page Themes that take multiple pages and stuff them together I was able to edit all my pages by creating a dummy page with no title or content and setting it as first page/single page template. Then you can freely edit the normal pages without any ill effect |
|
Same issue for me on several Wordpress: Tried the editor.min.js of 2.0.0, 2.0.10, 2.0.11, 2.0.12, 2.0.14 and 2.0.16 without success. |
|
Looks like I found a solution. I'm not saying that it will be your solution but it works in my specific case. The content I am editing with Elementor is calling $args = array(
'post_type' => 'my_custom_content_type',
'post__not_in' => array($post_id),
'posts_per_page' => '3'
);
$custom_query = new WP_Query($args);
while ($custom_query->have_posts()) : $custom_query->the_post();
get_template_part('templates/block/block-small');
endwhile;If I remove the To make it work without changing my query, I just added a condition to hide my list of related content only in the editing page. <?php if (!isset($_GET['elementor-preview'])) : ?>
// my block that was causing the bug
<?php endif; ?> |
|
@crtlf in my case, it is not working. I do have : In another website where it is working : In the working one, there is the elements node with the data object. |
|
I found out what was wrong in my case. The elementor-preview into the url seems to be the revision Id and not the post id. Therefore, the is_preview_mode method is not working as intented. |
|
I didn't know this function, it can be useful. If it's not working, you can use my ugly workaround. Because if you check the current URL, even if you are in the editing mode, it will return your content URL and not the if (!isset($_GET['elementor-preview'])) {
// your stuff that breaks Elementor
} |
|
@crtlf I did try your solution but it was not working. That is why I went a little further and found out the function. I modified it as above to make it work. But it can hardly recommend it as it removes the security about modifying a post that is not the correct one. |
|
@KingYes when editing a page using the elementor on the learndash plugin the lessons menu part I can not edit the post and get an error like the picture. |
|
@masikhsanms , I'd run through the same error. It turns out that it's my Nginx configurations that need to be fixed. Here's my config :
and replaced with
and restart your server. Hope that helps. |
Just to confirm that this fixed my issue, thanks alot. I would advise all Nginx users to try this method. |
|
http://prntscr.com/u6sbuo |
I have same issue, I can't edit at all |
|
I’ve the same problem since I’ve made the upgrade. I'm not a developer, But it would be great if the bug can be rectified on a Litespeed server. |
Permalink: SIMPLE |
why does this solution work for me? i assume it has something to do with cloudfront and the check for a GET parameter? Should I adjust cloudfront distribution settings to account for this? If I disable cloudfront altogether, this is no longer a problem. But keeping CF in place and forcing this function to return true appears to resolve the issue. I'd rather not edit plugin code. edit: it appears to be related to variables being passed through http headers. allowing this as default behavior in cloudfront has allowed this to work without modifying the plugin code |
|
I am having a problem when trying to edit any page on site, it wont give me anything except a redirect into the footer section of the page, NOT the main page or any other page i am trying to edit with elementor.
looking at system info within elementor it gives me this error |
my case, it was the CloudFront cache policy, allow All query strings to include in the cache key makes it works |
and others
After update a new version (current version)
I can't access the elementor view with existing page.
The text was updated successfully, but these errors were encountered: