No Code Attached Yet
avatar arnoldnijboer
arnoldnijboer
28 Aug 2021

Steps to reproduce the issue

directory and/or file permission are not writable

/home/{user}/public_html/administrator/components/com_actionlogs/models/fields/plugininfo.php

after changing it manual with chmod to 775 (file and directory) running the update Joomla sets file permission back to 644 and directory permission to 755. and throws an error with write permission during the update

Expected result

run the update without error's

afterwards set file permission back (automatic or manual)

Actual result

throws an error "could not open /home/..../plugininfo.php for writing"

System information (as much as possible)

running apache 2.4.46,php 8.0.5, webmin 1.980, virtualmin 6.16

standard directory/file permission user = owner www-data = group dir 755 file 644

ubuntu 16.04.6 (i know!)

Additional comments

avatar arnoldnijboer arnoldnijboer - open - 28 Aug 2021
avatar arnoldnijboer arnoldnijboer - change - 28 Aug 2021
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 28 Aug 2021
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 28 Aug 2021
avatar PhilETaylor
PhilETaylor - comment - 28 Aug 2021

Not a joomla issue - but a hosting issue.

If your server requires 775 for a file to be writable then it is non standard.

http://www.filepermissions.com/file-permission/755
http://www.filepermissions.com/file-permission/775

The standard of 755 for folders and 644 for files is pretty standard and will work on a standard ubuntu/apache build as long as the ownership of the files is correct.

avatar arnoldnijboer
arnoldnijboer - comment - 28 Aug 2021

"Not a joomla issue - but a hosting issue."

sure, but the update sequence changes it back to standard, and then try to update Joomla.

if it first updates, and then changes it back to stock everything is fine.

It should not do that, as is i can't update it.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35405.

avatar arnoldnijboer
arnoldnijboer - comment - 28 Aug 2021

changed owner of public_html and subfolders/files to www-data
now i get an error "invalid login" when trying to do the update


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35405.
avatar PhilETaylor
PhilETaylor - comment - 28 Aug 2021

"invalid login"

Which means that Joomla doesn't have access to create a file at /administrator/components/com_joomlaupdate/restoration.php

avatar arnoldnijboer
arnoldnijboer - comment - 28 Aug 2021

checked with "ps aux | egrep '(apache|httpd)'"
and apache is running as www-data

if file permission is set to 644 and directory permission set to 755,
as you stated is standard than it should work.

but even if i change it to 775 (file and directory) i still get the error.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35405.

avatar arnoldnijboer
arnoldnijboer - comment - 28 Aug 2021

changed everything to 777 and then it would update at last!
afterwards it didn't set it back to standard this time.
so i set it back to 755 and 644.
but then the website wasn't working as the user was wrong had to change user from www-data back to {user}

so either something in my system is not functioning, or Joomla update is not handeling the permissions correct.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35405.
avatar brianteeman
brianteeman - comment - 28 Aug 2021

You have an ownership problem

avatar arnoldnijboer
arnoldnijboer - comment - 28 Aug 2021

You have an ownership problem

thanks, but how was this not showing before 3.10.1

and as i stated apache is running as www-data so when setting file/directory permission to www-data:www-data it should be working right.

how could this work with webmin/virtualmin, as they give permission to public_html as user:www-data.
apache running as www-data and write permission as user.

WP has similar issues
|https://archive.virtualmin.com/node/57063


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35405.
avatar PhilETaylor
PhilETaylor - comment - 28 Aug 2021

WP has similar issues

Thus proving this is a hosting issue and not a Joomla issue.

avatar joomla-cms-bot joomla-cms-bot - close - 13 Sep 2021
avatar jwaisner jwaisner - change - 13 Sep 2021
Status New Closed
Closed_Date 0000-00-00 00:00:00 2021-09-13 01:37:51
Closed_By jwaisner
avatar joomla-cms-bot joomla-cms-bot - change - 13 Sep 2021
Closed_By jwaisner joomla-cms-bot
avatar joomla-cms-bot
joomla-cms-bot - comment - 13 Sep 2021

Set to "closed" on behalf of @jwaisner by The JTracker Application at issues.joomla.org/joomla-cms/35405

avatar jwaisner
jwaisner - comment - 13 Sep 2021

Closing as this has been identified as a hosting issue, not related to Joomla.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35405.

Add a Comment

Login with GitHub to post a comment