Package manager can't install a mod (fresh install 2.0 RC 1.2)

[imrich]

I hope someone can tell me that I'm doing something simply wrong!

I have a fresh install of of 2.0 RC 1.2. All seems to be working very well, thanks!

So I decide to try to install a package (Aeva 6.0.101).

Upload the zip to my server... OK
Try to perform the install.. BAD.. seems it says some files are not writeable, I search here and find I need to manually create a temp folder (777) in packages. I did that and now the install seems to continue without reported errors.... BUT WAIT!
When the install tries to redirect me to the mod settings page... it does not exist! This is not good!


So I try to look into why this is happening  here is what I find:

Source files seem to be backed up ok (renamed with a ~), but the source files never were changed! They are set to 666. Is this correct?


So why am I having so many problems?

What else should I check?

Thanks for any help!

[Arantor]

So are all the files in all directories at least 666?

[imrich]

The files in sources are all 666.

Should I check any others?

[Arantor]

I'd check all the files in the forum, many mods install to places other than just Sources.

Also check the directories themselves, they should be at minimum 755.

[gbsothere]

Perhaps you could check with your server and find out if PHP's Safemode is on and see if they will disable it (just to see if this resolves the issue)?  I had the same exact issue, permissions were all chown 777, Package Manager wasn't placing the edits in the SMF files and wasn't actually installing the mod.  The "temp" directory (777) was ineffective. I received some good advice when I opened a ticket and this is what resolved it for me.

[imrich]

Safe mode appears to be off, thanks for the hint.

The funny thing is that the packagemanager can install files, create copies of files (copy a file xxx.php to xxx.php~ in sources), but it can't edit the xxx.php file.

This must be the clue... the changes are not being made to the source files. I can tell because the backup ~ files are the exact same size of the original files.

The sources directory is 777 now.  Source files are 666, what else should I check?

[Arantor]

What about the other directories?

[imrich]

Is there a list of directories I should check? Or should all be 777?

[Arantor]

All of them probably should be for now. You can use the Options part of the Package Manager to try setting permissions for you, remember.

[imrich]

I've tried to use the package manager options, but that doesn't seem to be able to set permissions. Is this another clue?

[Arantor]

Even if you give it FTP details?

[imrich]

there is no place for the ftp password, is that correct? It does ask for username.

I did manually set all directorys to 777, still doesn't work.

[Arantor]

That is usually correct, yes.

So you've set all directories, and their files recursively to 777? Then I'm quite confused since that should definitely solve it.

[gbsothere]

One thing I'll just add, imrich, and it may not make any difference: 

What I noticed, when this was happening to me, is that although the package installed "pretended" to install the mod, I kept getting sent to a white page and found, when checking the database, that no new tables had been added and, as I said, earlier, no edits were made to any of SMF's files.  Once I was assured by my server that everything on my test site was chown 777 and that all files and directories were writable and once the "temp" directory didn't work the only other thing I did, besides having the server turn off the PHP's SafeMode was make this small change to my Subs-Package.php file: 

I found this:

Code Select Expand

if ($current['checksum'] != $checksum)
return $return;

and replaced it with this:

Code Select Expand

if ($current['checksum'] != $checksum)
            break;


I don't know if that, in addition to all the other measures is what fixed things for me but I do know that it didn't hurt anything.  I always pull my file to be edited from my server (to preserve mod edits) and just "save as" to a temporary folder when I change it so that, if it changes something negatively, I can simply return the file I pulled from the server.  I don't know if this will work for you but it did seem to break me out of the loop.

[imrich]

I set all folders and files to 777.

Then I deleted all files in the packages/temp directory.

Now it works!

Why do I have to clear the temp directory manually?

Also, why does the packages/permissions not work? (and how can it work if the options doesn't ask for the ftp password?)

Thanks for your help!

[Arantor]

I don't know why you have to clear it, but if it's worked, great.

As for permissions, it doesn't always actually need a password because of how it can make it work since it can be handled as an internal connection where a password isn't always needed.

[gbsothere]

I'd forgotten (since I'm an old man and I've slept since then) but I ended up emptying my temp folder as well.     Not sure why I did, probably desperation.

[imrich]

Thanks for all your help!! 

[Arantor]

Can we mark this one solved?

[imrich]

It you consider having to keep creating and emptying (sometimes) the temp directory OK, then perhaps you can mark it as solved.

I see two problems with 2.0 RC 1.2:

1) when installing mods, one has to remember to create, and sometimes empty the ./packages/temp directory (sometimes it seems to be deleted, other times it is not deleted, but needs to be emptied. I haven't determined why yet.

2) the packages, file permissions, 'change file permissions' functions don't seem to do anything even though no error messages are in log when trying to use these functions (I've tried both 'free - all files writeable' and 'restricted - minimum files writeable').

[gbsothere]

I agree that you shouldn't have to keep creating a temp directory but, in the meantime, if you only want to do it once, this mod will keep it from being deleted:

http://custom.simplemachines.org/mods/index.php?mod=724

[imrich]

I agree that you shouldn't have to keep creating a temp directory but, in the meantime, if you only want to do it once, this mod will keep it from being deleted:

http://custom.simplemachines.org/mods/index.php?mod=724

Does this mod mean that this is a known problem to be solved in the next RC or release?

Thanks for your help.
Rich

update: This mod does not appear to support 2.0 RC 1.2. So I can't install it now.

[gbsothere]

Does this mod mean that this is a known problem to be solved in the next RC or release?

Thanks for your help.
Rich

Well... the mod was also made compatible for 1.x because, every once in a while, complicated permissions issues have forced 1.x users to have to create a temp folder but there are some known issues in RC1.2 that I am told have been fixed for the 2.0 release. 

[imrich]

Does this mod mean that this is a known problem to be solved in the next RC or release?

Thanks for your help.
Rich

Well... the mod was also made compatible for 1.x because, every once in a while, complicated permissions issues have forced 1.x users to have to create a temp folder but there are some known issues in RC1.2 that I am told have been fixed for the 2.0 release. 

However this mod doesn't appear to support 2.0 RC 1.2, is there an update coming for this? Or Must I install it manually/

[Arantor]

You can install it manually, however the Package Manager is slightly more advanced in 2.0.

From the Browse Packages screen, in the bottom right corner is the word 'Advanced'. Click on it, and up pops a box, which should say 2.0 RC1.2. Edit it to say simply 2.0 RC1 - then save and attempt to install the mod again.

At first glance it should work just fine in 2.0 RC1.2.

[gbsothere]

Right now, I'm getting a "cannot be parsed" message on all versions but I talked to someone here last week using RC1.2 who did install it.  Let me try it on my RC1.2 test site and come back and tell you how it goes.

If you smell smoke, run.

[Arantor]

The mod site doesn't do so well with tgz files. But you don't need to parse it manually; it should install just fine given what I said above. (Did for me at least)

[gbsothere]

The mod site doesn't do so well with tgz files. But you don't need to parse it manually; it should install just fine given what I said above. (Did for me at least)

Right, doing what you said (Advanced Tab) allowed it to install just fine.  I did, however, send up a fresh Packages.php from the SMF zip before, though, because I had a nagging feeling that I've edited that file and didn't want the one on my server to be overwritten until I check.

[imrich]

You can install it manually, however the Package Manager is slightly more advanced in 2.0.

From the Browse Packages screen, in the bottom right corner is the word 'Advanced'. Click on it, and up pops a box, which should say 2.0 RC1.2. Edit it to say simply 2.0 RC1 - then save and attempt to install the mod again.

At first glance it should work just fine in 2.0 RC1.2.

Thanks for this tip! It seemed to install.

I'll have to find a mod to test to see if it installs now and if it keeps the temp directory.

I sure would be nice know know why this is happening. I don't have these problems with my SMF 1.1.10 on the same web servers.

[gbsothere]

You can install it manually, however the Package Manager is slightly more advanced in 2.0.

From the Browse Packages screen, in the bottom right corner is the word 'Advanced'. Click on it, and up pops a box, which should say 2.0 RC1.2. Edit it to say simply 2.0 RC1 - then save and attempt to install the mod again.

At first glance it should work just fine in 2.0 RC1.2.

Thanks for this tip! It seemed to install.

I'll have to find a mod to test to see if it installs now and if it keeps the temp directory.

I sure would be nice know know why this is happening. I don't have these problems with my SMF 1.1.10 on the same web servers.

You might just want to make sure first, if you've had to create yet one more temp directory after installing this mod, to set those tiresome 777 permissions on it.

[imrich]

You can install it manually, however the Package Manager is slightly more advanced in 2.0.

From the Browse Packages screen, in the bottom right corner is the word 'Advanced'. Click on it, and up pops a box, which should say 2.0 RC1.2. Edit it to say simply 2.0 RC1 - then save and attempt to install the mod again.

At first glance it should work just fine in 2.0 RC1.2.

Thanks for this tip! It seemed to install.

I'll have to find a mod to test to see if it installs now and if it keeps the temp directory.

I sure would be nice know know why this is happening. I don't have these problems with my SMF 1.1.10 on the same web servers.

You might just want to make sure first, if you've had to create yet one more temp directory after installing this mod, to set those tiresome 777 permissions on it.

Yes, I recreated the temp directory 777. Thanks for the reminder!

Now if we could only get the 'file permissions' feature of the package manager working, things may not be so painful.

thanks for your great support and help!

[Arantor]

The file permissions stuff is going to be highly server configuration dependent; it will work on some configurations and not others, and there is - unfortunately - not a great deal you can do about it.