Skip Navigation

[Resolved] When using Types Starter Theme, Elementor gives this error

This thread is resolved. Here is a description of the problem and solution.

Problem:
"Sorry, the content area was not found on your page" error occurs when trying to use the Elementor page builder with the Toolset Starter theme.

Solution:
Themes which are fully-integrated with Layouts—such as the Toolset Starter Theme—do not output the content using the standard the_content() function, and so are incompatible with Elementor.

This support ticket is created 6 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 4 replies, has 2 voices.

Last updated by Justin 6 years, 11 months ago.

Assisted by: Nigel.

Author
Posts
#609585
2018-01-24 15_14_06-Elementor _ Home.png

I get this error when using the starter theme, Elementor gives me this error.

Sorry, the content area was not found in your page.
You must call 'the_content' function in the current template, in order for Elementor to work on this page.

I am using the Child Theme of WP-Types (Starter). Help!

#609651

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Justin

With the Toolset Starter Theme if you are using Layouts then the theme templates do not use the_content() and so you cannot use Elementor at the same time.

You'll find the same if you convert the Astra theme to fully-integrate it with Layouts. The integration involves replacing the standard WordPress output from the_content() with the output from Layouts (as well as replacing the standard header and footer with Layouts output).

#609660

That error that popped-up was from Elementor.

For example, if I created my own theme, but wanted to use Elementor, as well, it wouldn't work because of the "the_content()" would be gone, and replaced with the Layouts() functions.

Is that correct?
If that is, what's the work-around here? Seems to be very vital in any page-builder.

#609675

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

That's right.

But Layouts is the page builder, and not just any page builder, because if you use it with an integrated theme it allows you to design the entire page, and not just the content area.

So with an integrated theme Layouts is your page builder.

If you prefer other page builders, such as Elementor, then go ahead and use Elementor instead of Layouts, but not with an integrated theme, because the theme integration is specific to Layouts, and may not be compatible with other page builders such as Elementor.

The theme options that were introduced with the Beyond Pages programme are intended to bridge the gap.

Use your page builder of choice on a non-integrated theme (whether that is Layouts or a different page builder) to design the content area of the page, while defining per-template settings for theme options such as whether to include a sidebar, custom header settings etc.

With some page builders there is an extra compatibility layer so that they can be used to design Views Content Templates, including Visual Composer/WPBakery, Beaver Builder, and the page builders of Divi and Avada. Elementor will be added to that list but the integration is not complete yet.

#609898

Thank you for the information Nigel, much appreciated. I am going to look into this some more! Thanks again.