How to Resolve “The Link You Followed Has Expired” Error in WordPress
The “The link you followed has expired” error in WordPress commonly occurs when you’re trying to upload a theme, plugin, or large file that exceeds the maximum file upload size or execution time limits set by your web server. It can also happen if there are issues with memory limits. Fortunately, there are several ways to resolve this issue by adjusting the server’s configuration settings. Here’s how to fix it.
Method 1: Increase the File Upload Size and Execution Time Limits in php.ini
One of the most common causes of this error is that the file you’re trying to upload exceeds the maximum upload size or execution time limits.
Steps:
- Access your server through FTP or the hosting control panel (cPanel or similar).
- Look for the php.ini file in the root folder of your WordPress site. If it doesn’t exist, create one using a text editor like Notepad or the file editor in cPanel.
- Add the following lines to increase the maximum file upload size, post size, and execution time:upload_max_filesize = 128M
post_max_size = 128M
max_execution_time = 300 - Save the file and upload it back to your server (if using FTP).
- Test the upload again to see if the issue is resolved.
- upload_max_filesize: Defines the maximum file size for uploads.
- post_max_size: Controls the maximum size for POST data (including file uploads).
- max_execution_time: Determines the maximum time a script is allowed to run before it’s terminated by the server.
Method 2: Update the .htaccess File
If you don’t have access to php.ini or can’t modify it, you can update the .htaccess file to increase the limits.
Steps:
- Access your server through FTP or the hosting control panel.
- Locate the .htaccess file in the root folder of your WordPress site.
- Open the file and add the following lines at the bottom:php_value upload_max_filesize 128M
php_value post_max_size 128M
php_value max_execution_time 300
php_value max_input_time 300 - Save the file and upload it back to the server.
- Test to see if the error persists.
- max_input_time: This controls the time the server spends processing input data, like uploads.
Method 3: Modify wp-config.php
In some cases, modifying the wp-config.php file can help solve this issue.
Steps:
- Access your server through FTP or cPanel.
- Locate the wp-config.php file in your WordPress site’s root directory.
- Open the file and add the following lines before the line that says /* That’s all, stop editing! Happy publishing. */:@ini_set( ‘upload_max_size’ , ‘128M’ );
@ini_set( ‘post_max_size’, ‘128M’ );
@ini_set( ‘max_execution_time’, ‘300’ ); - Save and upload the file back to the server.
- Check if the error is resolved by attempting the upload again.
Method 4: Increase Limits in cPanel
If your hosting provider uses cPanel, you can adjust the PHP settings directly through the interface.
Steps:
- Log in to cPanel.
- Scroll down to the Software section and click on Select PHP Version or MultiPHP INI Editor (depending on your host).
- Under PHP Options, locate and modify the following settings:
- upload_max_filesize: Set it to 128M or higher.
- post_max_size: Set it to 128M or higher.
- max_execution_time: Set it to 300 or higher.
- Save the changes.
- Try the upload again to check if the error is gone.
Method 5: Contact Your Hosting Provider
If none of the above methods work, the issue might be related to server-level limitations imposed by your hosting provider. You can contact their support team and request that they increase the upload_max_filesize, post_max_size, and max_execution_time values.
Summary
The “The link you followed has expired” error in WordPress can be fixed by increasing the file upload size, post size, and execution time limits. You can do this by modifying the php.ini, .htaccess, or wp-config.php files or using the cPanel interface provided by your hosting provider. If the problem persists, contacting your hosting provider for assistance is the best next step.
By increasing these limits, you’ll be able to upload larger themes, plugins, or files without encountering this error.