[#20437] - folder & file names with spaces in the media manager
- Closed
- 17 May 2018
- Medium
- Build: 3.8.7
- # 20437
Steps to reproduce the issue
Just recently wrote a simple plugin-editors-xtd button, based on the frame com_media. But then opened a very unpleasant thing.
I cannot select a folder or a file that contains space characters in the material through editors-xtd image button.
The same in media manager. It explicitly States that the name should not contain any space characters.
Previously created folders with space characters are displayed,but there is no navigation.
Expected result
Go to the selected folder.
Actual result
Folder that contains space characters is not navigated.
System information (as much as possible)
Joomla 3.8.7 17-May-2018
Apache/2.4.33(Win64) PHP/7.2.3
Additional comments
And this is the 21st century and the development of technology? Even filtering input->get(folder,", 'path') requests does not support spaces.
It turns out that the Joomla project is now developing for themselves, not for users.
Guys, what the hell?
joomla-cms-bot
- 
Thanks @brianteeman. I tried to find positive words I wanted to compile in an answer but failed.
Dear friend, I have no purpose to offend anyone. I was shocked. How could that be? This is not a mistake, as I first thought, and a special measure. And I've always loved Joomla, but it's a very strange way.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/20437.
I've had issues in the past myself with whitespace in filenames. Mainly when using in JS/Flash mediaplayers.
So it's not unproblematic. Of course it works for most cases and browsers itself obviously don't have issues with it, but if I have to give a recommendation, I still say try to keep filenames lowercased and without whitespace or any other special characters. Better safe than sorry
@infograf768 ,
the first thing I wanted to do was solve the problem with URL decoding. But it gave a little, because the problem was at the level of libraries. There are, of course, reasons for the prohibition of gaps. But another question. Why not immediately build a new architecture with these albeit unpleasant features...
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/20437.
@Bakual ,
Thin recommendation.:)) However, it is not good to drive users into some framework. Moreover, the gaps are used everywhere. I have in my project thousands of images and different documents, and all the materials links to them. My plugin certainly places them in HTML-tags without any problems. But when using standard libraries and plug-ins, you don't want to run into an impenetrable wall. Then the components as well as the engine lose their meaning if they can't be used for different tasks.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/20437.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-05-17 11:27:01 |
| Closed_By | ⇒ | mbabker |
Closing as a duplicate as already pointed out in #20437 (comment)
Comments like that are unlikely to get a positive response