@tushevorg can you add some testinstructions how we can test this?

1. make any of the files inaccessible to PHP's copy (chmod 444 some-file.css for instance)
2. Upload update package that will replace the read-only file
3. You will receive informative error - which file failed to be copied, not the general "Something failed" error, so you will remember that you've chmod'ed the file half a year ago for some reason and will be able to quickly resolve the issue

   ---

   _{This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8136.}

Reverted, and added one more notification (as well in ftp)

Any updates?

Hi,

Can you create a full test scenario including test package.
With the information Before Patch and After patch

Then I will test it and if successful I will ask someone else to test this.

Hi, @conconnl

I'm not very sure about what are you asking for. Could you please explain?

The scenario looks like:
1. Install any extension, for instance http://extensions.joomla.org/extensions/extension/style-a-design/personal-layout/blank-component
2. Make any file, like controller.php, read-only (on Unix chmod 444 controller.php)
3. Install the Extension again, to simulate an update. Due to read-only restrictions, copying the new file will fail, and an error will raise.
4. This error without the patch will be just the general "Copy file failed" error. With the patch, it will contain the name of the file as well.

It's all very simple, just a slight modification of the error message, but extremely useful for end-users.

I have tested this and i don't see any difference.
So I think you didn't test it for a while on new Joomla! versions.

Before Patch:

After Patch:

As @conconnl said above I find no difference applying patch. File name already showing without patch too.

I am closing this at this time as it would appear to have been fixed elsewhere. If that is not correct then it can always be reopened