Skip to main content

#57 Error right after installation: "Uploads directory does not exist"

Posted in ‘NorrCompetition’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information (available for public)

PHP version
8.1.16

Latest post by b2z on Wednesday, 19 July 2023 11:08 EEST

technicalrs
After uploading the package files, I got a successfull installation message, but also a error that reads "Uploads directory does not exist."
I get this message on the top of every NorrCompetition page on my Joomla backend. I would assume this is the reason that my test entry photos do not display.

b2z
Hello,

Please make sure that Joomla has enough permissions to create folders. For instance the component by default is trying to create a folder named "ncuploads" under your Joomla root installation folder.

Kind regards,
Dmitrijs

technicalrs
After testing the component, Joomla ended up creating the ncuploads folder as it should've, and I can see my test entry photos in my root folder. But they do not display at all to the user on the site.

b2z
Please elaborate about the display as it hard to understand without seeing the site itself.

In the admin area of the component the photos are also not visible?

Kind regards,
Dmitrijs

technicalrs
Here's how it looks on both ends of the site: https://i.postimg.cc/3wyhrhjD/Competition-Issue.png

b2z
Are you sure that photos are created?
What is the link to photo that the component cannot display (it should be visible in the source code of the page and looks like yoursite.com/ncuploads/photos/1/1/blablabla_11111111.jpg

technicalrs
https://www.ccefga.org/ncuploads/photos/1/1/big_6478bd3dbfe48_1685634365.jpg

b2z
When I try to open this link it says to me:

Error 403 - Forbidden
You don't have permission to access the requested resource. Please contact the web site owner for further assistance.

technicalrs
Would this be a permissions issue for the component? I can't think of why it would be restricting viewing that file to the user.

b2z
Nope it's a hosting server restriction.

The component itself does not restrict access to files. It creates photos as it should and the link to photos is there in the source code of the page, but it cannot be displayed in the browser. So you have a broken image link instead.

System Task
system
The ticket information has been edited by Arlene Dickerson (technicalrs).

technicalrs
After reviewing hosting server configuration we are still having issues with the component displaying images. The component worked on our J3 site with no permission changes at all. Can you please review that we have the component configured properly?

b2z
Arlene,

There is no configuration option. The component is doing it's job as it should - uploads images and then displays the img link correctly. But then the browser cannot display it.

403 Forbidden – you don’t have permission to access this resource is an HTTP status code that occurs when the web server understands the request but can’t provide additional access.

Often, HTTP 403 forbidden errors are caused by an access misconfiguration on the client-side, and could be caused by a malfunctioning security plugin, incorrect file permissions or a corrupt .htaccess file.

You mention in the start of this topic, that the component was not able to create "ncuploads" directory. So it was a permission issue. Probably now it is the same issue and sub-directories inside "ncuploads" directory has incorrect permissions.

Overall what I try to tell is that 403 is clearly a server issue.

My personal guess is that something is blocking media resources that are not inside the "images" directory. You can try to copy the overall "ncuploads" directory to your "images" directory and after that set the "Uploads Folder" option inside the component configuration to "images/ncuploads". Probably images will be displayed correctly.

Kind regards,
Dmitrijs

ssnobben
I also have a problem with this after changing the /upload folder to a customised one so seems be a bug for when your component for these settings.

I will try to make a new install again after 3 trials before and I have been working with Joomla with hundreds of components but never had this problem before..

thks

sulpher

-- Quote:
"The 403 Forbidden error indicates that the server understands the request but can't provide additional access. This means that the web page you're trying to open in your browser is a resource that you're not allowed to access."
End of quote ---

I have an assumption that there might be the following scenario: the site has a modified .htaccess file which blocks access to all folders which are not allowed. E.g. such a file could be generated by Admin Tools.
Try to temporary replace .htaccess with the core file taken from Joomla. E.g. rename existing .htaccess to .htaccess and take default file htaccess.txt and rename it to .htaccess to take action and check out the front-end. If it will help, then it means the /ncuploads/ folder which is placed in the root of the site is blocked by .htaccess and you have to add exceptions.

b2z
ssnobben,

You have a completely different issue, so no need to be confused here. If you changing the /upload folder to a customised one, you need to move all the contents from this /upload folder to a new one and change "Uploads Folder" option in settings pointing to your new upload folder location.

Kind regards,
Dmitrijs
Support information

Support hours: You can get our help: Monday - Friday / 09:00 to 17:00 (GMT+3), but not limited. Our staff is pleased to provide Premium support to every paid subscriber asap, but sometimes you should be ready to wait for our reply for up to 3 days.


Our time: / Your time:

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. We also ask you to remove temporary credentials at your site after the problem is resolved. Thank you.

Support of free extensions is not provided on this forum. Please submit your questions or report issues via Github tracker. See link on the product page.