Quote from: anablepo at Jan 26, 2008, 02:32 AM
Is there a way to insert internal links into pages the way that TinyMCE does (via dropdown with a list of pages perhaps?)
Not yet there isn’t. Reason is that the internal links dropdown in TinyMCE is making use of a built-in function of the Links plugin. I think there was a plugin for FCKEditor that someone wrote but not much came out of it. It’s a good idea though and one that will likely be explored in the near future. In the interim, you can use the traditional means of inserting an internal link by using the document ID of a page. For instance, if the document ID of a page is 38 then you could insert the following into the URL/HREF contents of FCKEditor:
[~38~]
MODx will see it and will change it to the real URL of the page when it is parsed. Granted, not as slick as the internal links thing in TinyMCE but it gets the job done.
Quote from: sunchess at Feb 16, 2008, 07:27 PM
Now, there is an ajaxfilemanager in FCKeditor an it work great. In manager. But how to show browse button in front-end? I cant upload images, only paste a url.
Maybe i should modify strings in fckconfig.js? Now i got this:
FCKConfig.ImageUpload = true ;
FCKConfig.ImageUploadURL = FCKConfig.BasePath + 'filemanager/connectors/' + _QuickUploadLanguage + '/upload.' + _QuickUploadExtension + '?Type=Image' ;
Is this path right?
My php connector actually here (\manager\media\browser\mcpuk\connectors\php\connector.php)
If you’re using the new Ajax File Manager beta (which, consequently, is in dire need of an update), the resource browser path is controlled by the FCKEditor plugin. Right now though the plugin is configured to only allow the use of the resource browser when a user is within the manager itself. This is for security reasons. Anyone who uses the resource browser will be able to see and do anything with the stuff in the resource browser. If you were to allow for the use of the resource browser on the front-end then you run the risk of allowing those users to delete or modify something that a manager user does. Unless you trust your users and they are all being authenticated on the front-end as web users, this isn’t a very good solution. A better solution would be to have a browse button and allow them to upload a file into a very specific directory of your choosing. A snippet instance or a custom template variable widget would be a good solution for this. But simply giving users freewill to browse and manipulate a whole directory with the resource browser has some pretty serious security implications. If you really want to do this, I can give you the modifications to the code...but I honestly can’t support it.
I’m aware that some users really want this. As such, I’ll be exploring the concept of user-assigned directories. Problem is that a custom resource browser has to be written to support this. I’m currently exploring different avenues and hope to get the initial development started soon. Don’t have a time table set yet. Hopefully soon.
