Download
2013-04-01, 04:07:10
(This post was last modified: 2013-04-01, 04:09:40 by dikkewalter.)
found a annoying bug when upgrading to 3.2.0
now it seems that directories that I created thru the backend (FTP) like "Baron Bruce" are being rewritten to "baron-bruce" when you create those directories from the front. Now I find myself wondering?
1. Do I have to "respect" the urlfriendly "baron-bruce" naming when uploading content with FTP
2. Is there a way to keep "Baron Bruce" etc. map naming without giving me this annoying error?
When reverting back to 3.1.2 the warning message is gone.
Please help.
Quote:Warning: opendir(../data/uploads/honden/Baron%20Bruce) [function.opendir]: failed to open dir: No such file or directory in /home/compute1/public_html/queenstone/admin/inc/basic.php on line 891
Warning: opendir(../data/uploads/honden/Baron%20Bruce) [function.opendir]: failed to open dir: No such file or directory in /home/compute1/public_html/queenstone/admin/inc/basic.php on line 913
now it seems that directories that I created thru the backend (FTP) like "Baron Bruce" are being rewritten to "baron-bruce" when you create those directories from the front. Now I find myself wondering?
1. Do I have to "respect" the urlfriendly "baron-bruce" naming when uploading content with FTP
2. Is there a way to keep "Baron Bruce" etc. map naming without giving me this annoying error?
When reverting back to 3.1.2 the warning message is gone.
Please help.
