Introduction to OceanWP Settings

Welcome to OceanWP!

In the OceanWP Settings category we'll go over the OceanWP Settings, also known as the Metabox Settings.

In order to enable the OceanWP Settings, the free Ocean Extra plugin must be installed and active on your WordPress website.

The OceanWP (Metabox) Settings allow you to experience the full power of OceanWP by taking control over your entire website. OceanWP (Metabox) Settings allow you to customize each of your pages, posts, products, etc independently from the global website (Customizer) settings and styling.

What does this actually mean? It means that with the OceanWP Settings you can:

  • choose a different header style for any page you want,
  • choose a different page layout,
  • choose a different sidebar content if the page layout is making use of sidebars,
  • choose a different menu,
  • disable or enable Top Bar,
  • disable or enable the Page Title or add custom title and subtitle (heading and subheading),
  • add templates through the Shortcode area,
  • set up different logos,
  • enable or disable the Footer Widgets area (or choose a custom footer),
  • enable or disable the Footer Bottom (Footer Copyright area),
  • and many, many, many more options depending on additional free and premium Ocean plugins.

In this category, we'll cover all default OceanWP (Metabox) Settings sections. These docs will help you get a firm grip of how the OceanWP Settings function and help you take full advantage of each aspect of your website without any coding knowledge.

New OceanWP Metabox Settings

As of OceanWP version 3.5.0 and Ocean Extra 2.2.0, our users will enjoy the brand new OceanWP Settings.

The main differences include:

  • based on React.js which is a default WordPress library. This eliminates all potential conflicts with third-party libraries, especially those based on Bootstrap which is the same library utilized by our now classic OceanWP Settings.
  • the new OceanWP Settings save applied custom settings faster when you hit the Save Draft, Publish or Update button and all because we're now utilizing the default editor options and WordPress library.
  • more options! The new method will allow us to add more options in the future without compromising your backend experience and functionality. That being said, more options are coming!
  • comfort! Freed up space below your content area.
  • the looks! Looks matter too ;)

The new OceanWP Settings are located in the Gutenberg Sidebar and you can access them by simply clicking the O icon in the upper corner of the main Editor Toolbar.

Old / Classic OceanWP Metabox Settings

We will still support the classic OceanWP Metabox Settings for all users running the Classic Editor or any other plugin that has the functionality to disable Gutenberg - nothing will change for you.

The classic OceanWP Metabox Settings will be supported as long as WordPress supports the option to disable Gutenberg.

New and additional features added to the OceanWP Metabox Settings will not be included in the classic OceanWP Settings.

The now old OceanWP Settings (and in case you're running the OceanWP version 3.5.0 and above, as well as Ocean Extra 2.2.0 and above, as well as third-party plugins that provide the option to disable the Gutenberg editor) are located below the content area, as shown on the image below

Accessing OceanWP (Metabox) Settings

You can access the OceanWP Settings by editing your pages, posts, products etc in WordPress (even if the content of the page has been built with the page builder), as shown in the image below.

Additional settings may appear in your OceanWP (Metabox) Settings based on the free and pro Ocean extensions you have installed and active.

Disabling OceanWP (Metabox) Settings

You can disable the OceanWP (Meta-box) Settings feature entirely or per supported page / post type via your WP Dashboard, OceanWP > OceanWP Panel > Extra Settings.

See this article to learn more about how to disable or enable OceanWP (Metabox) Settings.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.