Quantcast
Channel: Joomla! Forum - community, help and support
Viewing all articles
Browse latest Browse all 1475

Administration Joomla! 5.x • User-defined settings for media paths are not respected in Content > Media list

$
0
0
Joomla 5.0.3
PHP 8.2.17
MySQLi 10.5.24-MariaDB-1:10.5.24+maria~ubu2004-log

Description:
In Joomla 5.0.3, there appears to be a bug affecting the media path settings within the administrative interface. Specifically, user-defined settings for "Path to Files Folder" and "Path to Images Folder" under Options > Component > Media do not reflect in the Content > Media section. Despite setting these paths to a custom folder (e.g., "files" for the files folder), the media manager continues to default to and list contents from the "images" folder only.

Steps to Reproduce:
  • Navigate to System > Global Configuration.
  • Select the Media component under the Components tab.
  • Set 'Path to Files Folder' to a custom folder (e.g., "files").
  • Set 'Path to Images Folder' to a different custom folder if desired.
  • Save the settings.
  • Go to Content > Media.
  • Observe that the media list still points to and shows contents from the "images" folder rather than the newly specified paths.
Expected Result:
The media manager should reflect the user-defined settings for both "Path to Files Folder" and "Path to Images Folder", displaying files and folders from the specified paths.

Actual Result:
The media manager ignores the custom settings and continues to display contents from the default "images" folder.

Additional Information:
No errors are displayed on the interface or in the Joomla logs that indicate a failure to update or read the new settings.
The user can set a Path to Files Folder to an inaccessible directory (administrator) and than an error comes up as expected. But files folder is not this case.

Statistics: Posted by tychapogoy — Mon Apr 15, 2024 12:33 pm



Viewing all articles
Browse latest Browse all 1475

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>