SMF Support > SMF 2.0.x Support

"the Packages directory or one of the files in it are not writable!" BUT IT IS!

<< < (5/6) > >>

Arantor:

--- Quote from: MrPhil on February 27, 2012, 01:23:27 PM ---
--- Quote from: InternetFazoni on February 26, 2012, 10:52:12 AM ---SOLUTION FOR THIS IS REALLY CLEAR, OK?

If you using shared hosting, just set permissions to your packages directory to 777.

--- End quote ---
SIGH. 777 (World Writable) doesn't always work!. Many hosts forbid such permissions and will bar access to such directories, Maybe you'll get a 500 error, maybe you'll just get an inability to write. But STOP GIVING OUT BAD ADVICE -- you should always start with 755, and only if that doesn't work try 775, and as a last resort, 777.

You need to understand how your hosting service has configured PHP, so that you know when PHP is allowed to write to a given directory.

--- End quote ---

Add to that, any new files written by that process (e.g. new mod files) are still entirely vulnerable because they're owned by the web server.

The entire damn process of packages for SMF is vulnerable and there's no way to solve it without redesigning the entire system.

christopher94523:
I am getting the same errors and have tried the same folder permissions of 755/777

   "An Error Has Occurred!
   You cannot download or install new packages because the Packages
   directory or one of the files in it are not writable!"

This was NOT a problem when I upgraded to 2.0.1, so I am confused.
All that I have done is create a Pair Networks linking from https to the http code.
Perhaps the "install" code is hardcoded or expects something else?

Note that I had no problems when upgrading to 2.0.1 but had not added the SSL-based link.

best,
chris

christopher94523:
The "solution" of enabling suexec does not fix the install problem w/r/t package and SMF upgrades.;
I was already set up to run PHP using the mod, as per the 2.0.1 upgrade, which gave me no problems, or all of the packages which I added:

   System CGI Enabled
   Virtual FTP is Disabled
   suEXEC is Enabled

There have been no installation-related changes on my VPS (at Pair Networks).
What changed in the installation process that -- not being adequately tested -- broke installs for many of us?

Rather than having each of us "reinvent the wheel", how about backing out the code changes that broke this for all of us?

I suggest undoing your code changes and then individually testing them as you add them, and using BETA testing format so that real world networking gets tested and not just the system upon which it was deemed "okay": core QA.

best wishes,
chris

MrPhil:
Did you also try 775 permissions? Do you have the "temp" subdirectory under Packages?

Arantor:

--- Quote ---Rather than having each of us "reinvent the wheel", how about backing out the code changes that broke this for all of us?

I suggest undoing your code changes and then individually testing them as you add them, and using BETA testing format so that real world networking gets tested and not just the system upon which it was deemed "okay": core QA.
--- End quote ---

None of the changes in any release after 2.0 are to the package manager code, so it's not because of that that broke it.

The entire package process is fragile - and any of a number of host related changes could have broken it. I may be critical of SMF but I'm more critical of people jumping to conclusions without nearly enough information.

(Did you, for instance, actually look at what's in the packages to see what's changed?)

Navigation

[0] Message Index

[#] Next page

[*] Previous page