"The PHP temporary folder is not set"

[1outlaw3]

I have searched for days to get rid of this warning. Although there is no apparent functionality issues with the site, obviously something is not right. The path is set in the php.ini file (/tmp) but does not show a path when you check php.info? Im going to do my best to explain what I have done:

First, my joomla site is not the main domain on my shared server, it is a subdomain. The only php.ini file that I can find on my server in in the root of the server (not the main domain or subdomain) is this normal?

I have read through many forums and articles that all seem to say to just set the path to /tmp and I feel I have done that. I have also set that in global config on the backend of joomla 4.4. I have contacted hostgator about rebooting apache which they cannot do on a shared server.

1. How do I confirm that joomla is reading from the above php.ini file?
2. Do I need a php.ini file in the root of the joomla installation (subdomain)?
3. If I have to create a new php.ini, can I just copy the one from the servers root directory?

I am limited in my knowledge in this area, (php) and whether or not the site is working, if there is no way to correct the warning, it seem a bug in joomla that is overlooked because it doesn't effect usability of the site.

Is there a solution other than "dont worry about it if its not causing a problem"?

[gws]

Ignore it, it defaults to temp if it is not set.

[Per Yngve Berg]

The php temp folder is a server wide setting. It cannot be set in your site. Contact the Administrator of the server.

[JAVesey]

Ignore it, it defaults to temp if it is not set.

Agreed.

I have a warning saying "not set" on my live site (shared server) but the site functions perfectly normally. Uploads, extension installations and updates all function as they should.

[1outlaw3]

The php temp folder is a server wide setting. It cannot be set in your site. Contact the Administrator of the server.

When you say cannot be set in your site, are you saying that the php.ini file belongs in the servers root directory. I am the administrator for the server and the site. why does php.info show the upload_tmp_dir = ""? nothing in the quotes but the php.in file reads upload_tmp_dir = "/tmp".


For the other two: Ignoring it is not a solution.

[1outlaw3]

php.info: upload_tmp_dir no value no value
php.ini: upload_tmp_dir = "/tmp"

[Per Yngve Berg]

upload_tmp_dir string
The temporary directory used for storing files when doing file upload. Must be writable by whatever user PHP is running as. If not specified PHP will use the system's default.

It must be set in the Master PHP.INI File

[1outlaw3]

It must be set in the Master PHP.INI File

Due to being on a shared server with hostgator, the only part of the "file upload" that can be changed is the max upload size. Apparently changing the php temporary upload could effect other users on the server. I'm sure joomla is aware of this, so there should be a way to disable this warning, since there is no way to set that value for joomla. I realize it doesn't effect my site , but to me its still a bug as small and insignificant as it may be. Joomla cant change it, I cant change it... joomla should not be warning about it if it doesn't matter. Or at least have a switch to turn it off until such time a dedicated or VPS hosting is purchased and the file can be modified.

[Webdongle]

Ignore it, it defaults to temp if it is not set.

Agreed

[1outlaw3]

Ignore it, it defaults to temp if it is not set.

Agreed

Agreeing with someone else with no solution is not a solution. Usually that means you don't know... So just say you don't know. Maybe the only solution is for joomla to get rid of the warning???? So until some explains WHY it still has to be there, users will complain and one word nescient comments just waste efforts. There is always a workaround, and if the joomla "experts" don't want to help, then what is the forum for? I'm not the only one wanting a FIX for the warning. Obviously I'll have to ignore it until I can figure out how to get rid of it , or someone wants to help figure it out.

[Webdongle]

...

Agreeing with someone else with no solution is not a solution. ...

But it is the solution.

IF
the temporary folder is not set in php.ini file
THEN
the site's /tmp folder is used

This is not problem and can be ignored when extensions can be uploaded. Only when extensions cannot be uploaded is there need to check if that warning is a problem.

Now do you understand?

[1outlaw3]

Leaving a false warning in the admin is NOT a solution nor a workaround... that is a known bug whether you comprehend that or not... My post asked for a solution. I get your probably tired of answering a question you don't have an answer to. Your so-called solution fixes nothing if the warning persists. I get that the file isn't set which creates the warning, I hear you. It has to be known that there are thousands of users on shared servers that are not authorized to modify that portion of the php.ini file. So knowing that the file cant be set for those users, leaving the warning on when everything is working (extension installs, file uploads ect) is irrelevant and unnecessary; a bug. I would prefer a way to figure how to make the annoying warning disappear, and I'm sure (from what I searched through over the last few days trying to do such), hundreds would agree. So I'll ask again, is there any solution to this issue? solution meaning making it go away?

[Per Yngve Berg]

So, you are on a Shared host. You said you where the admin of the server. Have you contacted you host?

[Webdongle]

Leaving a false warning in the admin is NOT a solution nor a workaround...

It is not a false warning nor is it a workaround. It is there to help with diagnosing if a site isn't working. Think of it as a Jack in car. If you get a flat tyre you need the Jack to help when you change the wheel. It doesn't mean the Jack shouldn't be there.

If you still don't understand perhaps tell us
Your age range eg 8-12, teenager etc.
Your education level primary school, college etc.
Computer experience etc.
Myself or someone else might be able to explain in a way that you can understand.

[1outlaw3]

So, you are on a Shared host. You said you where the admin of the server. Have you contacted you host?

yes, I have contacted my hosting service. They are the ones that informed me that setting the folder is not possible on a shared server. I have seen that every other error and warning report can somehow be turned off except this one which is why Im here. If joomla system cant be satisfied and everything still works, whats the point of leaving the warning up? It seems there should be some way to disable it if its serving no purpose.

[Webdongle]

... If joomla system cant be satisfied and everything still works, whats the point of leaving the warning up? It seems there should be some way to disable it if its serving no purpose.

It serves a purpose. If it was turned off and the site moved to a server where there were problems then that warning might be needed to show.

Turning off a warning that (is not needed at the time but) might be needed is a little like cutting a wire to a fire alarm because you have not needed it in the past.

Again I request
Your age range eg 8-12, teenager etc.
Your education level primary school, college etc.
Computer experience etc.
So we know what level to explain things

[abernyte]

If you have cPanel with variable php versions then it can be set in the options for that php version.

[nacc]

I'm not going to argue the merit or implications of "the PHP temporary folder is not set[/url]" message for J! websites.

This "warning" message has been something that's lived within Joomla for over a decade. In Tim Davis' excellent [two-and-a-half minute] video presentation—Maintentance Monday Ep. 244—which you can watch on that website we're not allowed to mention here on this forum, the advice is that you can make this warning disappear by contacting your webhosting provider and ask them to set the PHP temporary folder.

If the advice given here and elsewhere doesn't address the "concern"—namely that the Joomla project developers have been over-cautious in generating this warning message and there should be some mechanism to remove it—then this forum is not the place to obtain a fix (if that fix involves implementing an override within the J! core CMS that allows users to disable the warning). The place to ask for that "fix" is to raise an issue on the J! Issue Tracker and discuss the matter with the J! developers.

I've seen this warning message on some of my websites over time. I can't tell you over what time period I've seen these "temporary folder is not set" messages and I can't remember if, or how, I was able to remove them but, in the long run, I learned to live with the niggle. Even though I don't have a specific set-procedure to answer the OP's question directly, if the matter is important enough then reporting it to the J! developers and asking them to address it would seem to be the next-best way to go.

Good luck.

[1outlaw3]

I'm not going to argue the merit or implications of "the PHP temporary folder is not set[/url]" message for J! websites.

This "warning" message has been something that's lived within Joomla for over a decade. In Tim Davis' excellent [two-and-a-half minute] video presentation—Maintentance Monday Ep. 244—which you can watch on that website we're not allowed to mention here on this forum, the advice is that you can make this warning disappear by contacting your webhosting provider and ask them to set the PHP temporary folder.

Thank you, I will check out the video. I do understand the purpose of the warning, I just hate 1 word answers when I'm clearly here for a solution providing there is one, which for myself it appears there isn't due to my hosting provider and will have to take Webdongles advice to "ignore" it..... for now.

[1outlaw3]

Webdongle, Although I respect your knowledge for joomla and PHP (I've read many of your other posts, some pertaining to this subject matter) I will not entertain your polite smart-ass comment. I made it clear that my knowledge of PHP was limited in the OP. I am not afraid of having less knowledge about PHP or joomla then yourself. That is why I am here; to learn and comprehend. You my friend came in here with (strictly my opinion) no intention of helping which I believe is because this seems to be un-resolvable for anyone in my situation, and your tired of repeating yourself so you feel agreeing with some one else's post to ignore the warning if everything is working is some kind of helpful solution. So, with all due respect, it's not helpful, it's annoying and makes you come across as an unintelligent intellect and I want to thank you for giving me the impression that joomla masters are just a bunch of keyboard jockeys looking to stir it up. But I know that is not true. I guess this is resolved, I gracefully accept the solution is to "ignore" the warning since it defaults to /tmp if it can't be set.