Search Results for 'download link'
-
Search Results
-
How to Fix 403 Forbidden Error on WordPress
To help you fix the 403 Forbidden Error on your WordPress site io am describing it in detail:- ►File permissions
- ► .htaccess file
- ► Hotlink protection
1. File Permissions
Each folder and file on your WordPress site’s server has its own unique file permissions that control who can:Read – see the data in the file/view the contents of a folder.
Write – modify the file/add or delete files inside a folder
Execute – run the file and/or execute it as a script/access a folder and perform functions and commands.
These permissions are indicated by a 3-digit number, with each digit indicating the level of permission for each of the 3 categories above.Normally, these permissions just “work” for your WordPress site. However, if something gets messed up with the file permissions at your WordPress site, it can cause the 403 Forbidden error.
To view and modify your site’s file permissions, you’ll need to connect via FTP/SFTP.
Find all of the tools you need to manage your website (errors and all) in one convenient location.
For the screenshots in the tutorial below, we’ll be using the free FileZilla FTP program. The basic principles will apply to any FTP program, though – you’ll just need to apply them to a different interface.
Once you’re connected to your server, you can view a file or folder’s permissions by right-clicking on it:
Of course, manually checking the permissions for each file or folder isn’t really an option. Instead, you can automatically apply file permissions to all the files or folders inside of a folder.
According to the WordPress Codex, the ideal file permissions for WordPress are:
Files – 644 or 640
Directories – 755 or 750
One exception is that your wp-config.php file should be 440 or 400To set these permissions, right-click on the folder that contains your WordPress site. Then, choose File Attributes:
Enter 755 or 750 in the Numeric value box. Then, choose Recurse into subdirectories and Apply to directories only:
Once you’ve applied the correct permissions for directories, you’ll repeat the process for files. Only this time:
Enter 644 or 640 in the Numeric value box
Choose Recurse into subdirectories
Choose Apply to files only
To finish the process, you just need to manually adjust the permissions for your wp-config.php file to make them 440 or 400:
If file permissions issues were causing the 403 Forbidden Error, your site should now start working again.
2. .htaccess File
if you’re hosting uses the Apache web server, one common cause of the 403 Forbidden error is a problem in your site’s
.htaccessfile.The
.htaccessfile is a basic configuration file used by the Apache webserver. You can use it to set up redirects, restrict access to all or some of your site, etc.Because it’s so powerful, even if a little mistake can cause a big issue, like the 403 Forbidden error.
Rather than trying to troubleshoot the
.htaccessfile itself, a simpler solution is to just force WordPress to generate a new, clean.htaccessfile.To do that:
Connect to your server via FTP
Find the.htaccessfile in your root folder
Download a copy of the file to your computer (it’s always a good idea to have a backup just in case)
Delete the.htaccessfile from your server after you have a safe backup copy on your local computer
Now, you should be able to access your WordPress site if your
.htaccessfile was the issue.To force WordPress to generate a new, clean
.htaccessfile:Go to
Settings → Permalinksin your WordPress dashboard
Click Save Changes at the bottom of the page (you do not need to make any changes – just click the button)And that’s it – WordPress will now generate a new
.htaccessfile for you.3. Check to See If Hotlink Protection Is Misconfigured
Hotlinking is when someone adds an image to their site, but the hosted link is still pointed to someone else’s site. To prevent this, some will set up what is called “hotlink protection” with their WordPress host or CDN provider.When hotlink protection is enabled, it will typically return a 403 forbidden error. This is normal. However, if you’re seeing a 403 forbidden error on something you shouldn’t be, check to make sure hotlink protection is configured properly.
Still Having Issues? Reach Out to Your Hosting Provider
The 403 Forbidden error means that your server is working, but you no longer have permission to view all or some of your site for some reason.
The two most likely causes of this error are issues with your WordPress site’s file permissions or .htaccess file. Beyond that, some plugin issues might also cause the 403 Forbidden error. Or it could be that something is misconfigured with hotlink protection or your CDN.
By following the troubleshooting steps in this guide, you should be able to get your site back to working in no time.
thanks
Topic: another mistake
Hello, the plugin version is 1.2.6, which is according to the information from the provider of the latest version. The plugin does not even report that there is a newer version. I do not assume that this problem is in the older version. Please write me what the code should look like, which after clicking on the link or button will display the PDF in a pop-up window, as you state on your page. I tried the code:
<a href="[file_list]"> View PDF </a>, unfortunately this one only downloads the PDF again. I think this is the primary problem for all users of this plugin, because the Download manager does not offer document viewing by default.I have this [wpdm_tree] in this page: https://www.cm-pombal.pt/teste-5/ and this [wpdm_tree category=”atas-assembleia” download_link=1] in this
https://www.cm-pombal.pt/atas-reunioes-de-assembleia-municipal/deliberacoes-das-reunioes-assembleia-municipal/ but is not working.
I have Downloadmanager PRO updated, as well WPDM Extended Short-codes.
Can you help?
