TinyBrowser (3) Troubleshooting

pict-drupal-module.png This page explains about the troubleshooting of TinyBrowser module.

Since TinyBrowser uses JavaScript, cookie, session, etc., there are some places we want to you to check first before reporting problems/bugs. So please try do the following steps when you have problem of using TinyBrowser.

Troubleshooting

  1. Check issues for the TinyBrowser project page and check if you can find similar/same issues you have there.
    http://drupal.org/project/issues/tinybrowser

  2. Make sure that you installed TinyBrowser, WYSIWYG editor module and WYSIWYG editor to the proper directory.

    TinyBrowser module should be installed to the (drupal-root)/sites/all/modules directory, as well as WYSIWYG editor modules. Directory for installing WYSIWYG editor depends on the WYSIWYG editor module you use.

  3. Check any problem at TinyBrowser module settings page.
    Go to Administer > Site configuration > TinyBrowser page and check if the WYSIWYG editor section has any error messages or not. Make sure that the correct WYSIWYG editor is selected there. If the selected editor does not match the actual WYSIWYG editor you are using, you can still open up the TinyBrowser popup window but the image selected will not be inserted back to the editor.

  4. Check and make sure that $cookie_domain is defined in the settings.php file for your site.
    If you do not define the $cookie_domain, you will end up with a blank TinyBrowser window.

  5. Check and make sure that the PHP safe_mode is OFF
    If you can create a small PHP script and run at the server, you will see all the PHP settings of your server.
    1. <?php
    2.  phpinfo();
    3. ?>
    Search the safe_mode under PHP core configuration section in the result.

  6. Check and make sure no Javascript aggregator/optimizer
    TinyBrowser work neighter Javascript Aggregator module nor Optimize Javascript file setting ON at Administer > Site Configuration > Performance page. If you switch from ON to OFF, be sure to clear Drupal cache and web browser's cache.

  7. If you are using either FCKeditor with FCKeditor module or CKEditor with CKEditor module, go to the module settings page and check if the TinyBrowser is selected at the File browser settings section.

  8. If you are using FCKeditor, CKEditor or TinyMCE with Wysiwyg module, check if the TinyBrowser plugin checkbox is checked at Buttons and Plugins section of the Wysiwyg modules settings.

  9. Be sure that you have added proper toolbar icons for image/media/file browsing. You do not have to enable all types, just enable the button for only the types you want to use.

  10. Clear the Drupal cache
    Go to Administer > Site Configuration > Performance page and then click the button Clear cached data.

  11. Clear the Web browser's cache on your local PC

  12. Restart the Web browser on your local PC

  13. Open error console or use any other method to collect Javascript errors and try to start TinyBrowser. If you see a Javascript error related with TinyBrowser, note the detail error and report it to us.

  14. Check the watchdog log
    Go to Administer > Reports > Recent log entries page and check if you can see any error that seems to be related with TinyBrowser. If you find any, report them to us. or if you see any log whose type is TinyBrowser, report that to us too.

  15. If you have access to the Drupal data base table 'variable' (or with some prefix such as 'my_variable', please issue the following SQL command and report the out to us.
    1. SELECT * FROM variable WHERE name LIKE '%tinybrowser%';
    You can find your database tabel prefix in the settings.php file for your site. ($db_prefix)

  16. Enable inline plain textarea mode and check if it works or not.
    Go to Administer > Site configuration > TinyBrowser page and General settings section. Then, enter edit-body to the text field of 'Enable inline image/file insertion into plain textareas'.
    Then go to create contents page (any content type) and you should see the 'insert image or link' small text right below the content Body's textarea.
    First disable the WYSIWYG editor and then click on the 'image' or 'link' button. This will invoke the TinyBrowser with standalone mode. Please check if this works perfectly or fails just like the TinyBrowser invoked from inside the WYSIWYG editor.

Please collect as much information as possible using the procedures above, and report to us at Issues for TinyBrowser forum at drupal.org.

We are now collecting any many troubleshooting information as possible to make this troubleshooting page better.

Thanks,

 

Your rating: None Average: 3 (1 vote)