Integrating TinyBrowser
| Project: | Wysiwyg |
| Version: | 6.x-2.0 |
| Component: | Editor - TinyMCE |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Now TinyMCE module is replaced by wysiwyg API.
So I'm trying to integrate Tinybrowser (one of the best image uploader for me) in this new module.
Tinybrowser readme tells us:
1) Copy the tinybrowser folder and contents to your TinyMCE plugins directory.
=> I've copied tinybrower folder into modules\wysiwyg\plugins
2) Place the following javascript link after the link to TinyMCE (tiny_mce.js):
<script type="text/javascript" src="/tiny_mce/plugins/tinybrowser/tb_tinymce.js.php"></script>
=> I've created a new file "tinybrowser.inc" in my folder modules\wysiwyg\plugins
=> in this file :
function wysiwyg_tinybrowser_plugin() {
$plugins['tinybrowser'] = array(
'title' => t('Tinybrowser'),
'js file' => 'tb_tinymce.js.php',
'settings' => array()
);
return $plugins;
}=> in my drupal: Administer > Site configuration > Wysiwyg > Full HTML (configure) > Buttons and plugins -> check Tinybrowser at the bottom of the list
=> I checked source code, this step 2 is ok
3) Add this line to your TinyMCE init: file_browser_callback : "tinyBrowser"
=> [todo]
Anybody could complete this third step?
Maybe is there a better way to do step 2 ?
Hope it'll help...

#1
So, it seems step 2 isn't valid...
#2
What is TinyBrowser?
#3
Tinybrowser is a very userfriendly image uploader. You should try.
I suggest you to use Tiny tiny MCE module instead Wysiwyg module if you want to use Tinybrowser.
Step 2 is processed in tinytinymce.module file and step 3 in drupal backend (tinytinymce configuration). Very easy to install.
#4
Great, go with that. Case closed.
#5
Probably not ideal but you can just update function wysiwyg_tinymce_settings (about line 140) in the sites/all/modules/wysiwyg/editors/tinymce.inc and add to the settings variable with this line 'file_browser_callback' => 'tinyBrowser',. Also there still require some tweaky in term of how is being display probably relative path issue for the css or image of the tiny browser interface.