Quote from: ApoXX at Mar 23, 2007, 04:21 PMThe Safari issue may be due to the CSS used for displaying the file manager; the file manager functions fine in Firefox with the CSS removed (from fta.functions.php), however I don’t have a Mac with which to test. 
Thanks for the tip I’ll try to edit fta.functions.php as instructed and report if it solves it also for FF/Mac (no reason why it shouldn’t..)
Omniweb for Mac also suffer the overlay issue, even worse it does not display anything but the overlay mask... but like Safari it’s the WebCore engine that was to be expected. Opera doesn’t do better either... I’ll re-test all this once I dropped the inline CSS.
Quote from: ApoXX@davidm, I’ll have a look at the fileManager code, it was bundled with Flash TA and I was trying to make as few changes as possible for future upgrade-ability. The file manager seems to see the system path I enter (’diskPath’=>’/home/sites/mysite.com/assets/media/’) and restricts me to that directory, are you saying that it’s possible to get out of the restricted directory using relative paths or something?
I don’t know if it’s relative path that cause it but I am able to access my web server’s root (!!!) and navigate through it (though hard to read because of the overlay style issue I have so far). Note that I use a dedicated box, not a shared hosting. I didn’t have the chance to know wether I could only read files or also write/delete them (shudder).
I have checked the source code for the frame, and the script is initialized alright, with the right path to (I replaced it by "TheRightPathHere" for obvious security reasons) :
<script type="text/javascript"><!--
// Initialize flash textarea
document.getElementById("ta").className = "efx_flashtextarea";
if (typeof fTAR == 'object') { fTAR.FlashTextArea.setFilemanager('/assets/plugins/flashtextarea/deploy/fileManager.php');
fTAR.FlashTextArea.setServerURL('http://nodeo.net/');
fTAR.FlashTextArea.setBasePath('TheRightPathHere');
fTAR.FlashTextArea.setLngFile('/assets/plugins/flashtextarea/deploy/lang/en.xml');
fTAR.FlashTextArea.setup('/assets/plugins/flashtextarea/deploy/FlashTA.swf', '/assets/plugins/flashtextarea/deploy/FlashFB.swf');
}
--></script>
So it’s not FlashTA config which is at fault.
Maybe it’s my server config (but never had any issue with any script, and my server admin is a real pro with experience I doubt that he would leave any hole in there).
Quote from: Flece at Mar 23, 2007, 08:02 PM
works very well but only in the Backend. Is this a Bug or a feature ?
MODX - 0.9.5
FF 2.X
Thanks Flece
Look at fta.functions.php
if (!$frontend)
$output .= "\t\t\t\t\t\tfTAR.FlashTextArea.setFilemanager('$fta_url/deploy/fileManager.php');\n";
$output .= <<<SCRIPT
fTAR.FlashTextArea.setServerURL('$site_url');
fTAR.FlashTextArea.setBasePath('$base_url/assets/media');
fTAR.FlashTextArea.setLngFile('$fta_url/deploy/lang/$lang.xml');
fTAR.FlashTextArea.setup('$fta_url/deploy/FlashTA.swf', '$fta_url/deploy/FlashFB.swf');
}
--></script>
The plugin would seem to be initialized only for the backend...
Any reasons for that ?
Doesn’t work with QuickEdit for some reason ?
