In this video we’ll demonstrate how you can troubleshoot and fix the “Preview could not be loaded” error step by step by process of elimination, so you can get back to designing your website with Elementor in no time.
hi-oh at zip from Elementor the preview
could not be loaded notice is an error
that sometimes occurs an elemental the
cool thing though is that usually it’s
quite easy to fix the notice itself will
try to point you as close as possible to
the issue such as a missing theme or an
HT access file or perhaps an HTTP error
code however there might be cases where
you will see a more general notice we’re
sorry but something went wrong in this
video I’ll show you how you can easily
troubleshoot and fix this error step by
step so you can get back to designing
your website with Elementor in no time
before we get started it’s important to
know that if you get this error message
on a week on this page such as the check
out or shop page it’s normal because
these pages can only be edited with the
WooCommerce builder which is an
elemental pro feature this error also
occurs when you’re trying to edit your
blog page with elemental or when you set
a regular page as your posts page you
can click on preview debug to see which
page you’re actually trying to edit in
this case you need to use elemental pros
theme builder instead of trying to
directly edit with elemental you can
learn more about editing your blog page
and sharp-edged with elemental by
checking the links in the description
below
ok let’s dive in and see how to solve
this error first off an easiest thing to
do is just to try edit in incognito mode
in your browser this rules out issues
with add-ons or browser cache so first
copy the URL and in chrome click on the
three dots in the upper right hand
corner and choose new incognito window a
new window appears you’ll see this
incognito icon indicating that you’re in
fact in incognito mode go ahead and
paste the URL log in again to see if the
error persists you should also make sure
that no add-ons are working in incognito
mode you can also try a different
browser altogether now if the issue is
still present you should ask yourself
have I recently installed any new
plugins or updated existing ones in most
cases loading issues are caused by
conflicts between plugins or themes so
in order to confirm this you should
activate safe mode it creates a safe
environment that ISIL
it’s elemental and WordPress from the
themes and plugins that might be causing
the error there are two ways you can
activate safe mode you can click the
enable safe mode button that pops up at
the bottom of the screen or you can go
to elemental tools and in general select
enable from the safe mode drop-down and
click the Save Changes button using safe
mode opens the elemental editor on a
clean version of WordPress without
loading a theme or any plugins except
for elements or an elemental pro all
plugins are deactivated and an empty
theme file is loaded it’s also important
to know that safe mode doesn’t impact
your site’s front-end it only impacts
the editor if it solves the issue we can
safely say that it isn’t caused by
elemental or elemental Pro it also rules
out the possibility of it being caused
by the hosting which leaves us with
third-party plugins and themes as
potential culprits so keep this as a
rule of thumb if activating safe mode
helps it means that the issue is either
plugins or theme related so after
successful debugging with Safe Mode you
need to follow these steps to solve your
issue
first you should deactivate the recently
installed or updated plugins if it
solves the issue you know that one of
these plugins is the culprit
so reactivate each plug-in one at a time
and test your site with each
reactivation keep testing until you find
the plug-in that is causing the error
once identified you can get in touch
with the plugins developers to request
assistance or use another plug-in with
similar functionality if the issue still
remains after having checked all plugins
you need to have a look at the theme so
first check that the theme file exists
go to dashboard appearance and check to
make sure that your theme is selected
and active if your theme is neither
selected nor active go ahead and install
or reinstall it the next thing you
should do in case the Araneta still
shows is switched to a different theme
go ahead and switch to a default
WordPress theme such as 2016 or 2019
this helps rule out an issue with the
themes code if switching to a default
theme solves the issue
then a theme conflict is causing the
error in this case you should contact
your theme support and ask them to make
sure that the WordPress default loop is
used in your layout
now if safe mode doesn’t solve the issue
it means that the issue most likely is
related to the hosting so contact your
hosting provider and go through the
following steps first we will try to
save our permalinks again this will
regenerate the htaccess file which might
just solve the problem in the wordpress
dashboard and the settings go to
permalinks and hit save you’ll see the
permalink structure updated notice now
go back to your page and check if the
error is resolved if not you can also
try to change the permalink structure to
plain if it wasn’t already some servers
do not allow you to write to the
htaccess file and as a matter of fact
you cannot always modify your permalink
structure and edit in elemental so hit
Save Changes and check again the next
thing you should do is verify with your
host provider that your WordPress
install includes the HT access farm if
for some reason you still stuck with the
error message you’re most likely dealing
with an HTTP error pay attention that
these following steps are for advanced
users and should be performed by your
host provider or another professional if
you’re dealing with an HTTP error then
in the error notice the line that points
to the issue will be the HTTP error code
followed by its error message just like
you see here hitting the preview debug
link will try to open the preview in a
new regular page so not in the editor
you should see the error again in ruel
format which may provide more info for
developers to solve the issue another
thing you should do is verify that there
isn’t a redirect on the page if you’re
receiving 403 errors you should check
the following first off you may have a
corrupt htaccess file contact your
hosting provider to see if this is the
case if this didn’t help solve the issue
then your file permissions may not be
correct ask your host provider to check
that your WordPress directories and
files have the correct permissions for
our three errors might also occur due to
a security plugin
to sort this art activate the learning
mode of the plugin or contact their
support this issue can also be due to
the firewall of your server which is
something you should check with your
hosting company now if you are receiving
a page that requires authentication if
the page shouldn’t be asking for
authentication contact your host
provider for help in removing this
requirement or check security plugins
you may be using four options to turn
this off
if you receive 500 errors while using
Elementor you have to check the error
logs of your server to see what the
issue is these errors are survey related
so the logs need to be sent to your
hosting company beforehand if you do not
know how to produce PHP error logs
please send this guide to your hosting
company most of the time this error
message is received because of a memory
limit issue the memory limit has to be
set to at least 128 megabytes according
to our requirements you can go to
Elementor system info WordPress
environment to check it out there are
other things that can lead to this issue
for instance a fatal error or an issue
with a third-party plugin and without
the error logs it’s not possible to know
what the exact issue is the elemental
system info page has login capabilities
as well so if the error 500 results from
a bug in the code you should be able to
see the PHP error message there it could
look something like this so if memory
isn’t the issue
perhaps a plug-in is causing the error
you can identify the culprit here after
the plug-in directory now there are some
other less common reasons for this error
such as conflicts with membership
plugins so contact your hosting provider
and check your permissions on pages
built with elemental and membership
plugins another less common yet possible
cause for this error might be an issue
with cloud flares rocket loader we have
added a flag that disables rocket loader
for the elemental scripts in the editor
for version 2.5 and app you can check
out this link to learn more about
solving issues by creating specific
rules in cloud flare if your hosting
company is not able to solve the issue
and you are a pro user you
send the ticket with the error logs to
our support via support at elemental
comm or check out our fatal error guard
here well that’s it
now you know how to troubleshoot and fix
the preview could not be loaded error
step by step and get back to designing
your website with elemental don’t forget
to subscribe to our YouTube channel for
more tips and tutorials see you later
