标签： wordpress

Enabling Your Home Page

This is the first page that your website visitors will see when they arrive on your site. Setting up your home page is the same as setting up any other regular page, except that you need to specify in the WordPress settings which page will be allocated as your site’s static front page. You can change your site’s static front page at any time as often as you wish.
How To Set Your Home PageStep 1 – Login to your WordPress Dashboard and navigate to the Settings > Reading section.
Step 2 – Select A Static Page option.
Step 3 – Choose the page you want as your home page from the Front Page dropdown list.
Step 4 – Once done, click ‘Save Changes‘.

How to Set Up Parent and Child Pages in WordPress

The WordPress page structure does not have to be a flat structure (i.e. all pages on the same level).
WordPress allows building a page hierarchy by creating child pages under a parent page. The WordPress admin interface has the option to mark a page as an independent page, or to put it in a parent-child relationship. The page hierarchy can have an infinite level of subpages, but it’s rare to see more than 3 levels of pages, as this can complicate navigation.
Setting a Child PageYou find this option in individual pages. It is not available on posts or other custom post types. This page hierarchy is useful for Side Navigation Templates and the Vertical Menu Widget, as well as providing a clear structure to your pages in the back end.
To create a child page, simply create or edit a page in WordPress like you would normally do. Under the Page Attributes meta box, choose a parent page from the drop down menu.
Note: If you do not see the Page Attributes menu, then please click on the Screen Options button on the top right hand corner of your screen. It will display a menu where you need to make sure that Page Attributes is checked.

Make Menu Items Open In A New Window

You can set main menu items to open up in a new window using the default WordPress option ‘Link Target‘. See the the steps below.
1. To enable the option, please login to your WordPress Dashboard and navigate to Appearance > Menu. In that new section, click the Screen Options button in the top right corner of the screen and select ‘Link Target‘.
2. You will see a new option in each menu item called ‘Open link in new window/tab’, check that box for the menu items you want to open in a new window/tab.
3. Once done, click ‘Save Menu‘.

WordPress 5.3 And Avada Custom Image Size Generation

With the 5.3 WordPress update, a new way of saving additional image sizes to the database was introduced for when images are uploaded to the library. Unfortunately, this adjustment was not compatible with the internal naming convention for Avada’s custom image sizes.
The problem will only occur for images that are uploaded to WordPress 5.3 and versions of Avada prior to 6.1.2. For these images, Avada’s custom uncropped image sizes are not available as a choice in the sizes drop-down option in the media library when you insert them to a post or page. And some of the responsive image sizes won’t be available. Updating to Avada 6.1.2 resolves this issue.

The 3 Types Of Images And How They Are Affected

Images uploaded to your media library before updating to WordPress 5.3.

Images uploaded to your media library on WordPress 5.3, before the update to Avada 6.1.2.

Images uploaded to your media library on WordPress 5.3, after the update to Avada 6.1.2.
Images Uploaded Before Updating To WordPress 5.3Nothing to do here. These images work as expected, even for Avada versions older than 6.1.2. And of course, they also work fine on Avada 6.1.2 or later.
Images Uploaded To WordPress 5.3 Before The Update To Avada 6.1.2As mentioned above, the problem for images uploaded on WordPress 5.3, but prior to the update to Avada 6.1.2, is that you can’t select Avada’s custom uncropped image sizes in the sizes drop-down of the media library when you insert them into a post or page. In addition to that, some of the responsive image sizes won’t be available.
Unfortunately, this can’t be auto-fixed through a theme update, as WordPress has already stored the data incorrectly in the database. Still, there is an easy way to correct this. Install and activate the Regenerate Thumbnails plugin, then go to the Tools > Regen. Thumbnails tab in your WP Admin sidebar and choose ‘Regenerate All Thumbnails.’ Doing this regenerates all images and adjusts the Avada custom image sizes to their new naming conventions. Once the regeneration is complete, it is business as usual.
Images Uploaded To WordPress 5.3 After The Update To Avada 6.1.2Nothing to do here. All images uploaded to WordPress are generated as expected on your Avada site.

WordPress Menu Not Saving / Displaying All Items

Let’s say you have created a nice menu for your theme, saved it and then viewed it on the front end, only to see that a portion of your menu items are not showing. Or maybe even the entire menu does not show. You have assigned it to the main menu, and saved it, but then it drops out and will not show on the front end.
What happened? Did the menu items disappear? Is this a theme issue? Or a plugin issue?
The answer is no, it’s a server configuration issue. Please read this detailed article written by CHRIS MAVRICOS (better known as SevenSparks) to help understand why this can happen, and what you can do to fix it: http://sevenspark.com/wordpress/menu-item-limit

Avada and WordPress Gutenberg Compatibility

According to Automattic, the driving force behind the development of WordPress – the world’s leading CMS, Gutenberg is a new publishing experience, that was released with WordPress version 5.0, on December 6th, 2018.
In this document, we will be covering everything Gutenberg, Avada and what you need to know.
OverviewWhat Do I Need To Do In Preparation For WordPress 5.0?Already running Avada 5.7.2? Nothing to do!Running Avada below 5.7.2? Don’t panic!What If I Can’t Update Avada, Will My Site Break?If I Choose Not To Update WordPress, Will Avada Work?The WordPress 5.0 Editor Overview,What Do I Need To Do In Preparation For WordPress 5.0?This will depend on the Avada version you are currently running. If you are already running Avada 5.7.2 (latest available version is: 7.6) you are all set and good to go. Otherwise we recommend updating Avada to the latest version. Always make sure that you check and follow the detailed instructions for updating your theme. The importance of maintaining your site by making sure that your theme and plugins are regularly kept up to date, cannot be overstated. If you can’t update to the latest version of Avada just now, we have you covered too.

Already running Avada 5.7.2 or up? Nothing to do!
Running Avada below 5.7.2? Don’t panic!What If I Can’t Update Avada, Will My Site Break?Already running Avada 5.7.2 or up? Nothing to do!You can expect the same seamless working experience that you are used to with Avada and WordPress. Both, Avada and the Fusion Builder, will be unaffected and this includes the front-end of your site. Additionally, feel free to try the WordPress 5.0 Gutenberg editor. We added options to either create a post on Gutenberg or within Fusion Builder, your choice. You can’t edit a page/post created with Gutenberg in the Fusion Builder or vice versa, however, you are free to try Fusion Builder Elements in Gutenberg. More information please read our help file.
We have implemented the option to choose between the Fusion Builder and Gutenberg when creating new pages or posts as illustrated below.
IMPORTANT NOTE: If you create a page/post with Gutenberg you can’t edit/maintain the same page/post with the Fusion Builder and vice versa. They are not interchangeable.Choosing Add New > Fusion Builder gives you this.
Choosing Add New > Gutenberg gives you this – note the Edit with Fusion Builder button, top left.
Choosing Add New > Classic Editor gives you this.
Can I Also Use The New Block Editor?Yes, you certainly can. What must be noted is that if you create a page/post with Gutenberg you cannot edit/maintain the same page/post using the Fusion Builder and vice versa. They are not interchangeable. Any Gutenberg page/post created will display perfectly on the front end of the site to anyone viewing it.
Running Avada below 5.7.2? Don’t panic!Update Avada To The Latest Version – Here Is HowWhether you are running an old version of Avada or not, regular maintenance is critically important. Furthermore, making sure that your theme and plugins are kept up top date should be a part of your maintenance procedure. These are our detailed update instructions:
Important Update InfoHow To Update The ThemeUpdating From An Old Version Of Avada?Apply Any Released PatchesAvada ChangelogSomething else that is important is to also ensure any patches that our team releases between update cycles are applied as part of ongoing maintenance for your install and always clear your cache plugins post update.
Current Avada version is 7.6Current Fusion Builder version is 3.6Current Fusion Core version is 5.6What If I Can’t Update Avada, Will My Site Break?The short answer is: No. The front-end of your site will be unaffected and everything will remain perfectly functional, not affecting your website visitors. It is the WordPress back-end of your install where you will have obstacles. If you have not updated your Avada theme to the latest version, it won’t be possible to edit posts/pages with the Fusion Builder, that is why we strongly recommend updating to Avada 7.6+ before you update to WordPress 5.0. See our detailed update instructions.
If you are not able to update your theme just yet, you have two other options as listed below:
1 – Install And Activate The Classic Editor PluginThe Classic Editor plugin is developed and maintained by the core WordPress team and will be officially supported until December 31, 2021. Install and activate the Classic Editor plugin.
It does what it says on the tin and will sideline the WordPress Gutenberg editor upon activation. The plugin also makes it possible to keep both the Gutenberg and the Classic editor at the same time, configured the in the plugin’s settings. Go to WordPress Dashboard >> Settings > Writing page, you will see the option under “Classic editor settings”.
All of this means that the traditional WordPress editor is active and Fusion Builder is enabled for all pages and posts.

Download Classic Editor or install via WordPress Dashboard >> Plugins
Active installations: 600,000+WordPress Version: 4.5 or higher2 – Or, Install The Disable Gutenberg PluginThis method allows you to to disable the WordPress Gutenberg editor for certain or all user roles and post types and override any Gutenberg related nags. Install and activate the Disable Gutenberg plugin. Upon activation, go to the >> WordPress Dashboard > Settings > Disable Gutenberg page to configure the plugins settings.
Download Disable Gutenberg or install via WordPress Dashboard >> PluginsActive installations: 10,000+WordPress Version: 4.9 or higherIf I Choose Not To Update WordPress, Will Avada Work?Yes, of course, Avada will work perfectly with the 4.9.8 version of WordPress. You can delay updating to WordPress 5.0 if you have accessibility concerns or are simply not ready to do so at this time.
767,650 Businesses Trust Avada
Get Avada767,650 Businesses Trust Avada
Get Avada767,650 Businesses Trust Avada
Get Avada,The WordPress 5.0 Editor OverviewThe new WordPress 5.0 Welcome screen greets you with:

“You’ve successfully upgraded to WordPress 5.0! We’ve made some big changes to the editor. Our new block-based editor is the first step toward an exciting new future with a streamlined editing experience across your site. You’ll have more flexibility with how content is displayed, whether you are building your first site, revamping your blog, or write code for a living.”
At the very top of the page the following prompt is visible “Learn how to keep using the old editor.”, clicking that takes you to the “Keep it Classic” and plugin install option, as shown below:

“Prefer to stick with the familiar Classic Editor? No problem! Support for the Classic Editor plugin will remain in WordPress through 2021.
The Classic Editor plugin restores the previous WordPress editor and the Edit Post screen. It lets you keep using plugins that extend it, add old-style meta boxes, or otherwise depend on the previous editor. To install, visit your plugins page and click the “Install Now” button next to “Classic Editor”. After the plugin finishes installing, click “Activate”. That’s it!
Note to users of assistive technology: if you experience usability issues with the block editor, we recommend you continue to use the Classic Editor.”
There has been significant discontent with regard to overall accessibility and the new Gutenberg editor. On October 30th, WP Tavern released an article with a sobering assessment of the accessibility status of Gutenberg. You can read the full report from Joe Dolson here.
Back to installing the Classic Editor plugin from the WordPress welcome screen, your next step will be as follows:
In the subsequent WordPress Dashboard >> Plugins screen, click “Install Now” then activate the plugin. Installing the Classic Editor disabled the new Gutenberg editor as default and gives you the traditional editing experience for pages and posts.
There are two settings for the Classic Editor plugin, the default is > “Replace the Block editor with the Classic editor.” and the secondary is > “Use the Block editor by default and include optional links back to the Classic editor.”
There are two settings for the Classic Editor plugin, the default is > “Replace the Block editor with the Classic editor.” and the secondary is > “Use the Block editor by default and include optional links back to the Classic editor.”,ResourcesWordPress 5.0, Avada, And You. All That You Need To Know.WordPress 5.0 Development CycleWordPress Slack ChannelGutenberg HandbookGutenberg Reviews