If your pages return a 404 Page Not Found error after enabling custom permalinks in WordPress, the issue is typically related to your WordPress or server configuration — not Avada itself.
Common Symptoms
“I just setup my WordPress installation and my awesome new Avada Website. 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?”
Common Causes
Firstly, this is not an Avada issue. The problem involves your core WordPress installation, or your web server configuration. There a few things that can cause this to happen:
The server rewrite module is not enabled (for Apache servers, this is usually mod_rewrite)
The .htaccess file is missing or not writable
Apache II is configured to disallow overrides by your .htaccess file.
Rewrite rules have not been refreshed correctly
A permalink slug conflict exists
How To Fix It
There are several solutions to this issue. Please see the list below.
1. Reset Your Permalinks. The simplest fix is often to refresh the rewrite rules. Go to Settings > Permalinks. Select your preferred permalink structure. Click Save Changes. If needed, switch temporarily to Plain, save, then switch back and save again.
2. Check Your .htaccess File. Make sure a .htaccess file exists in the root of your WordPress installation. If it doesn’t exist: Create a blank file named .htaccess, and upload it to your WordPress root directory. Also ensure the file is writable by the server so WordPress can update rewrite rules automatically.
3. Verify Server Rewrite Support. On Apache servers, ensure: mod_rewrite is enabled and htaccess overrides are allowed (AllowOverride All). If you’re unsure, contact your hosting provider for assistance.
4. Add Rewrite Rules Manually. If WordPress cannot write to .htaccess, you’ll see rewrite rules displayed on the Permalinks page after saving. Copy those rules into your .htaccess file manually and upload the file back to the server.
5. Check for Slug Conflicts. 404 errors can also happen when multiple pages, post types, or plugins use the same permalink slug. For example: /blog/, /portfolio/ or /events/. Try changing conflicting slugs and then resave your permalinks.
6. Clear All Cache. After making changes, clear all forms of cache, including: Browser cache, Caching plugins & Server or CDN cache.
Still Having Issues?
If the problem persists after following the steps above, contact your hosting provider to check your server configuration.
For additional information on working with permalinks in WordPress, visit the WordPress Codex. 
