Templately won’t open
-
It used to work just fine, but now every time I try to open Templately, either from the WordPress dashboard or Elementor edit page, it displays for a few seconds and then the page just goes white and it doesn’t load. I’ve tried deactivating, uninstalling and reinstalling, etc.
-
Hi @ruthhill236,
That seems strange. Can you please share your console log with us so that we can see whether you are getting any error or not?
Besides, you can check for plugin conflicts as well by deactivating all plugins except for Elementor and Templately.
Let me know how it goes. Thank you!
Hi @ruthhill236 ,
If the above solution not working for you, you can also create a support ticket from here: https://wpdeveloper.net/support/new-ticket/
Our Support Team will get back to you and resolved this issue don’t worry.
-
This reply was modified 5 years ago by
Abid Hasan.
Hi @rafinkhan,
Thanks for your reply! I tried deactivating all plugins besides Elementor and Templately, and this didn’t help.
Is this what you mean by the console log?
DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 [Exception... "Favicon at "https://dimensions4.mercuryanalytics.com/favicon.ico" failed to load: Not Found." nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 253" data: no] FaviconLoader.jsm:253:22 NS_NOINTERFACE: Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIWebProgress.DOMWindow] WebNavigationContent.js:263 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 [Exception... "Favicon at "https://assets.wpdeveloper.net/favicon.ico" failed to load: Not Found." nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 253" data: no] FaviconLoader.jsm:253:22 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. 2 ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813 DataCloneError: The object could not be cloned. ExtensionChild.jsm:813Thanks so much for your help!
Hi @ruthhill236 ,
Hope you’re doing good.
Well, You can open your browser console by clicking the right mouse and select Inspect. Choose Console tab there just like this screenshot: https://d.pr/i/6fvw9W (This screenshot taken from the Chrome Browser)After that click on the Templately icon on the Elementor page. Let me know if you get any errors in the browser console.
Besides that, let me know your configuration (PHP version, WP version) so that I will try to reproduce your issue and get back to you.
Thank you!
Thanks for your help, I appreciate the clear instructions and screenshot!
This is the error in my console:
https://drive.google.com/file/d/1myyMCYb6iYFksf-DlryRzHkM6NBU5shn/view?usp=sharingMy WP version is 5.7 and my PHP version is 7.3.27
Thank you very much!
Hi @ruthhill236 ,
Thanks for the screenshot!
Our dev team just reproduced this issue on our end. We will resolve this issue and release a new version as soon as possible don’t worry!Thanks for your patience!
Hi @ruthhill236 ,
Hope you’re doing good today.
We’ve just released a new version of Templately where we fixed this issue.
So please make sure to update the latest version of Templately(v1.2.2) to resolve this issue.Thank you!
Thanks so muchh for letting me know! I appreciate it
-
This reply was modified 5 years ago by
The topic ‘Templately won’t open’ is closed to new replies.