parpalak wrote:Thanks for the detailed information. Looks like a command fopen('...', 'wb') fails. Is there a directory in extensions/ after this failure? In other words, please, run this command
ls /some_path/forum/extensions/ -la
EDIT: Well, I have already understood that there will be nothing
I couldn't reproduce this bug on my hosting. I ask you to edit sources of pun_repository (for bug searching). Can you do it for PunBB, please?
If yes, comment or remove the following lines (about 129-130) in pun_repository.php
unlink(FORUM_ROOT.'extensions/'.$ext_id.'.tgz');
@pun_repository_rm_recursive(FORUM_ROOT.'extensions/'.$ext_id);
and then see the output ofls /some_path/forum/extensions/ -la and ls /some_path/forum/extensions/pun_antispam/ -la (or any other extension that you will to install via pun_repository).
Last edited by parpalak (Yesterday 12:45:50)
No, there was no directory in there when I got a failed install originally (I did install these manually later, but I still want to troubleshoot how pun_repository works).
I commented out those lines for you in pun_repository.php, I assume that means that it won't remove the directory and archive if it fucks up. Right now, I am testing by installing extension pun_bbcode via pun_repository.
This is what happens when I now attempt it:
Error from forum:
ERROR! Files could not be extracted from the downloaded archive. The next errors appear while extracting:
Error while opening {'../extensions/pun_bbcode/styles.css'} in write binary mode
ls -lah /some_path/forum/extensions | grep pun_bbcode
drwxrwxrwx 2 apache apache 4.0K Nov 22 12:17 pun_bbcode
-rw-r--r-- 1 apache apache 13K Nov 22 12:17 pun_bbcode.tgz
NOTE: My punbb install is on a Plesk domain, and Plesk typically forces web content to have the following ownership scheme
user: username associated with domain
group: always 'psacln'
Now, there's nothing at all in the apache error_log, so this has got to be a permissions issue based on my environment. This is further proven since the archive has 644 perms belonging to the apache user, and the resulting directory is empty.
Is there anyway anything can be done from the development end to catch this? Or should I just continue to install extensions manually?