Avada 文档

Google Fonts Diacritics

Diacritics is a scripting type which is not supported by Google web fonts. Because of this, those letters will render as the fallback font and not in the font selected by the user. These characters may look like they』re bold, but in fact, that』s just the default style of Diacritics.
To solve this issue, please select a different font and see if the new font renders the diacritics in a better manner.
To learn more about this occurrence, please read this in-depth article.

Google Conversion Tracking With The Button Element

If you are a Google Analytics user, you can now use conversion tracking through the Button Element to track when someone clicks on a button on your website. Read on…
Read More About The Button Element!Setting Up The ButtonThe first step to set up conversion tracking is to add a custom attribute to the Button Element when you add it to the page. Add this in the 『Button Additional Attributes Field』 (customizing it for your URL):
Copy to Clipboarddata-ga-url='https://example.com/your-link' 1data-ga-url='https://example.com/your-link'Add Script To Theme OptionsThe second step is to add this script to the Advanced > Code Fileds (Tracking etc.) > Space before   Theme Options field:
Copy to Clipboard
jQuery( document ).ready( function() {
var $buttons = jQuery( '.fusion-button[data-ga-url]' );

jQuery.each( $buttons, function( index, element ) {
jQuery( element ).attr( 'onclick', 'return gtag_report_conversion('' + jQuery( element ).data( 'ga-url' ) + '');' );

} );

} );
​x 12 jQuery( document ).ready( function() {3 var $buttons = jQuery( '.fusion-button[data-ga-url]' );4​5 jQuery.each( $buttons, function( index, element ) {6 jQuery( element ).attr( 'onclick', 'return gtag_report_conversion('' + jQuery( element ).data( 'ga-url' ) + '');' );7​8 } );9​10 } );11That』s it! Your button is now set up to track conversions vis Google Analytics. For more general information on tracking clicks on your website as conversions see this Google article.

Fatal Error: Call to a member function have_posts() on a non-object

If you receive this message when updating your theme, most likely you need to delete the header.php and footer.php from your child theme, and copy the same two files from the new parent theme. Sometimes major changes are done to those files, which can results in your child theme files needing updated. In the future, we are going to eliminate the need for this process.

Fatal Error: Allowed Memory Size Exhausted

It』s very common to get fatal error messages about memory; 『Fatal Error : Memory Size Exhausted』. This can happen when you install themes, plugins or upgrade to the latest WordPress version. Such types of problems arise because the PHP Memory Limit of your Host is less than what the process requires for performing its functions. In such a case you would need to follow these 5 tips to Increase your host』s PHP Memory Limit – these were provided by Dailybloging.org
Tip 1: Increase the limit via PHP.ini fileYou can directly increase the PHP Memory Limit if you』ve access to the PHP.ini file. Most small Shared hosting servers won』t give you access to the PHP.ini file. But some servers allow you to create a duplicate PHP.ini in your respective site Directories whose data/values will override the default PHP.ini values. To do that you just need to create a file with the name 『php.ini』 in the directory where your WordPress site is installed. In that just add the command memory_limit = 128M in it to increase the Memory Limit to 128 MB.
Tip 2: Changing the Memory Limit via wp-config.phpIf you don』t want to mess with the PHP.ini file, then you can go for this method. In this you won』t be needing to create any extra file in your Directory. Just Adding define(『WP_MEMORY_LIMIT』, 『128M』); in your 『wp-config.php』 file would increase your PHP Memory Limit to 128 MB.
Tip 3: Modifying the .htaccess file to Increase Memory LimitA Default WordPress Installation won』t have a .htaccess file. But in case you already have it for some purposes like 『301 Redirection』, just add the command php_value memory_limit 128M in your 『.htaccess』 file and your memory limit will increase to 128 MB.
Tip 4: Changing the Memory Limit via wp-config.phpThis method is just an Alternate to the php.ini method. Because the function of the code we use in this method is same as what we put in the php.ini file.You just need to place the code ini_set(『memory_limit』,』128M』); in the 『wp-config.php』 file which is placed in the root folder of your WordPress installation.
Tip 5: Have a talk with your HostIf you are a person who is new to all these techie sounding things then it』s better to have a Live Chat / a Call with your Host right away. It』s your right to talk to them & get the necessary changes you need as you』re paying for it.

Custom Permalinks Return 404 Errors

If you are getting 404 error when accessing pages, please see the information below.
SymptomsI just setup my WordPress installation and my awesome new Avada theme. I went into WP Admin > Settings > Permalinks and selected something other than the default option. But now when I try and navigate to a page, it just returns a generic 「404 Error – Page not found」 message. What gives?
Likely CausesFirstly, this is not a theme issue. The problem involves your core WordPress installation, or your web server configuration. That said, there a few things that can cause this to happen:
Apache II mod_rewrite module is not being loaded by your web server.
Your WordPress .htaccess file is missing or not writeable by the web server.
Apache II is configured to disallow overrides by your .htaccess file.SolutionsThere are several solutions to this issue. Please see the bulleted list below.
First make sure that mod_rewrite is installed and enabled on your Apache II web server, and also make sure that the webserver allows your .htaccess file to override the server directory configuration.
Make sure that your WordPress .htaccess file is present in your WordPress installation. If it is not, simply create a blank file called .htaccess and upload it to your WordPress installation folder.
Set permissions on your .htaccess file that allows your web server to write to the file – CHMOD 666.
Go back and set your permalinks option to the 「default」 option and save the change. Then, set it to something other than the default and save the change.
If your .htaccess file is writeable by the web server, it will contain new directives that sets rewrite rules for your custom permalink option.
If it is not writeable, you will see a message below your permalinks screen that contains the rule set you need to add manually into your .htaccess file, save it, and upload it back to the WordPress installation folder.
Check to see if you can navigate from your front page menu links without error.If the issue persists, contact your web host support team for further assistance.For additional information on working with permalinks in WordPress, visit the WordPress Codex.

Common Issues – Broken Theme & Stylesheet Missing Errors

Some common issues you might run into when installing a WordPress theme are the 「Broken Themes…」 and 「Stylesheet Missing…」 error messages. This does not mean the theme you are using is broken or does not work; it means the theme has been uploaded incorrectly. Thankfully, Envato has a nice post about this information. Please see the link below to solve these two issues.
View The Envato Help Page For These Two Errors

Are you sure you want to do this? Please try again.

If you are installing your theme from the WordPress theme installer, but get a message that says Are you sure you want to do this?, most likely your web server is configured with low PHP settings that only allow a certain size ZIP file to be uploaded via WP admin.
Most hosting companies configure their servers to only have the maximum file upload size limit at 8-10 MB, some are less. The Avada theme ZIP is currently about 8 MB in size. So if you get this error, your web server is rejecting the upload due to the overall size of the Avada.zip file. WordPress is unfortunately giving you a rather ambiguous message in response. This is not a theme issue or bug.
To Solve The ProblemYou can get your web host to increase your PHP limits so a larger zip file is allowed to be uploaded. They will know which limits to set if you explain the issue.You can upload your theme via FTP. View our video tutorial in the Video section of the forum to learn how to install your theme via FTP. It is very easy and efficient.Recommended PHP Configuration Limitsmax_execution_time 60memory_limit 128Mpost_max_size 48Mupload_max_filesize 48MYou can verify your PHP configuration limits by going to the Avada > System Status tab in the WordPress admin area. Or by installing a simple plugin called WordPress phpinfo().

500 Internal Server Error

If you just installed WordPress, a WordPress plugin, or a theme for your site, and out of nowhere your site returns a 500 Internal Server Error, please read on. If you have been surfing the web for any length of time, you have probably encountered a 500 internal server error. These errors are not confined to WordPress. They are generic errors that report very little on what the actual cause is. First, don』t panic. Lot』s of people have been confronted with these errors, and they can be fixed.
There are five major reasons why these errors occur in WordPress: Incorrect web server configuration Incorrect folder/file permissions Corrupt files or files that contain errors in code PHP memory limits set too low Conflicting third party plugins1. Incorrect web server configurationIf your web server (whether it be Apache or IIS) is configured with incorrect directives, they can cause 500 errors to occur. The problem is that web hosting support will often blame the error on software you have installed without even checking to see what is contained in their error logs. Just know that after you have checked the following remaining causes, and they fail to resolve the issue, you will need to (sometimes forcefully) get your web host to help diagnose and fix the problem.
2. Incorrect file permissionsWith very few exceptions, file permission for WordPress, plugins, and themes need to be set at 755 for folders, and 644 for files. You may think that setting permissions more loosely, like 777, will relieve the problem, but you would be wrong. Setting permissions either too strict or too loose often cause this and other errors.
3. Corrupt files or files that contain errors in codeUsually improper/errors in file transfers to the web server cause corruption to occur. It may look like the file is sitting there just fine, but something in the process caused the file to be unusable by the server. For example, if you uploaded a text file in binary language instead of ASCII it will render the file unreadable by the web server. Coding errors can also create this error, whether that be in WordPress, a plugin, or a theme.

Often, the only way to resolve an error in WordPress core is to reinstall WordPress.
If it is plugin related, deactivating all plugins will relieve the error.If it is theme related, deleting and reinstalling the theme will often take care of the problem.By far the most common 500 error produced by a file is related to the WordPress .htaccess file. The .htaccess file is primarily designed to be used with custom permalink structures. But it is also used by some third party plugins, and for overriding certain server configuration directives if allowed. If it contains errors, it can return the dreaded 500 internal server error. The .htaccess file is located in the root folder of your WordPress installation (not the theme).

Log into your site via FTP (Filezilla, etc.).
Download a copy of your .htaccess file and rename the copy e.g. 「.htaccess-backup」.
Delete the .htaccess file residing on your Web server.

Create a new blank file called 「.htaccess」 on your PC/laptop/Mac.

Upload this new file to your Web server in the same place as the original .htaccess (which you deleted).

Navigate to your WordPress admin URL, e.g. http://www.yoursite.com/wordpress/wp-admin, and you should now be able to log in.

Finally, once logged in, navigate to the Permalinks settings page in the admin console and do nothing further. Simply going to the settings page should enable WordPress to write the correct .htaccess declarations itself. You should now be able to nagivate to www.yoursite.com or http://www.yoursite.com/wordpress (depending on whether WordPress is running your entire site or just a blog etc.) and all should be well once more.
4. PHP memory limits set too low, There two ways to solve this problem.You can either get your web host to increase your PHP limits.You can upload your theme via an FTP client. We offer a video tutorial located in the Video section that explains how to use FTP to install your theme.5. Conflicting Third Party Plugins Should Be DeactivatedIf you can access the admin area of your site, log in to your admin section and deactivate all plugins. After doing so, check your front end page again. If it loads without error, you have a plugin conflict. Now, start activating each plugin one by one. When you see the 500 error again on the front end pages, you will know that the last plugin you activated is the likely culprit. Deactivate it and continue checking all remaining plugins one by one to make sure there are no others.If you are getting the 500 error on the front end and the back end admin area, then you will need to access your site via an FTP client. A little known trick is to change the name of your /wp-content/plugins folder to something else temporarily like 「plugins.bak.」 This will make WordPress ignore your plugins. Then check to see if this resolves the problem. If it does, log into your admin section and then change your plugin.bak folder back to plugins . Then deactivate all of your plugins via your admin page.Recommended PHP configuration limits are as follows: max_execution_time 180 memory_limit 128M post_max_size 32M upload_max_filesize 32MHow To Verify Your Current PHP LimitsYou can verify your PHP configuration limits by installing a simple plugin found here. In addition, you can always contact your host and ask them what the current settings are and have them adjust them if needed. Please note though that many hosts will try to keep the PHP limits low without reason. However you are paying for it, and therefor should be getting your money』s worth.