Hello!
I've just installed Update Manager for Joomla 1.5 v 1.5.1

Upon installation I've received this warning message:

I looked in the global configuration/ server / temp folder path on our Joomla installation and found this:
/home/users/web/b270/sl.01041958/public_html/space/tmp

However, there is no clue as to what I should do with the information provided by the Update Manager. It does not give any suggestion. Obviously it should be added to some file somewhere, but which file? Where? Am I supposed to change the path in my global configuration based on the Update Manager installation report?

If the Update Manager software can see this information, why can't it use the information on its own to update the path information somewhere, or in a program run try both paths if it encounters an error?

Undaunted by the mocking throngs, I forged ahead...I clicked on the "So lets continue our travels and download the update file >>>" link and promptly received this error message:


Well, it appears that Update Manager disregarded the path information in my global configuration, tried its own suggested path and failed. I think...I don't really know. I'm just saying what I say based on what I'm reading. I guess another question should be, "How do I tell Update Manager to disregard its own path suggestions and trust what is there?"

I'm very excited to use the Update Manager for all the obvious reasons. Indeed, your work on this component should be integrated into the core Joomla product as it is an obvious and important element that would make Joomla vastly more attractive, especially with frequent and ongoing patch updates.

Thank you in advance for any suggestions and assistance you may have.
Regards,
-RR

Hi,

This is very strange, though I do love your post style.

The update manager does its best to guess what might be wrong but it isn't always accurate which is why its a simple warning not "thou shalt not pass" message. There are a few situations where what it guesses are wrong: the first is that you really want a different tmp directory for security reasons and the second is that you're running on some awkward FTP/writing setup so the tmp path makes sense...sort of.

In your case I'm going to err on the side of number two which is unfortunately not something I know a lot about because I don't have a server set up that way. But what I think you've found is a bug in the stream class. It looks like its prepending a path somewhere that it shouldn't. By default the system should have taken care of that but I think the mismatch between the two paths has caused some confusion - it thinks its using a relative path not an absolute path so wacks the two paths together. So its not ignoring it, but the JStream class just isn't behaving properly with it.

As a simple test, try replacing in your global configuration the temp path with what JUpdateMan suggests and see if this makes a difference. It will behave slightly better and if it works it was a misconfigured path. I'll have a look over the code to see how I can make a change which fixes the problem in future to ensure the mismatch doesn't happen.