New Extension: MX Tinybrowser (universal field for creating TinyMCE or/and MarkItUp textareas with TinyBrowser&LinkManager;support)

Just uploaded the new version. Thank you for adding the folder creation options. I’m running into a problem where the thumbnails are created but aren’t showing. The source code is showing this:

http:/my_site.com/uploads/photos/%Y_thumbs/_tb_step3.jpg

but the path should be http:/my_site.com/uploads/photos/2009/_thumbs/tb_step3.jpg

The rename function still has the “dot” as part of the name and not the extension. Is that a tinybrowser issue?

The permissions for the created thumbnails and images is 644 where nGen file was setting them as 777.

I upload the new version. Could you please check 😊

I upload the new version. Could you please check 😊

I see the year now in the path, but the slash after it is missing.

http://my_site.com/uploads/photos/2009tb_step2.jpg

ok. Now, I think, this issue is done.

by the way - you can try your test with missing .dot.

Would it be possible to pre-configure your Fieldtype so it automatically adds the

https://ellislab.com/asset/images/team-photo/

etc. to the images? That way if you have pagination you don’t need to add the absolute path setting in tinymce.

Would it be possible to pre-configure your Fieldtype so it automatically adds the

https://ellislab.com/asset/images/team-photo/

etc. to the images? That way if you have pagination you don’t need to add the absolute path setting in tinymce.

In theory, with some small modification - yes, is possible. But why you don’t like absolute path?

p.s. tiny.js configuration in current version setup by default for working with absolute patch.

It’s just how EE does it so I figure there must be a benefit if moving domains or something but yeah it’s not a huge deal if if you already have tinymce set up with absolute path.

ok. Now, I think, this issue is done. by the way - you can try your test with missing .dot.

Thumbnails are showing, the renaming works. Beautiful! Thanks. I have some more testing to do in the next couple of days, so I’ll let you know if I run into anything else. Nice work! 😊

It’s just how EE does it so I figure there must be a benefit if moving domains or something but yeah it’s not a huge deal if if you already have tinymce set up with absolute path.

How I say before, it’s possible to create. Just a 10-30 new lines of codes and additional checkbox in settings, but I think, usually do not transfer domains a couple times per year, and if transfer - is better to use Search&Replace;Tools in CP for replaced old domains in weblog record.

Hi Max, great extension.. well done!

However when I set “TinyMCE + TinyBrowser” as my custom field I get “No Upload Privilegies” (mind you the typo there) but “TinyBrowser Stand Alone” works fine. Any ideas?

Hello, Cem. Did you have this error in modal window? V. of EE? TinyMCE config file(tiny/office/article?)? For TinyMCE+TinyBrowser and TinyMCE StandAlone do you used the same Folder Settings (File Upload Preferences)?

Attached images will explain the situation better Max.

I am testing this on a clean install with the latest version of EE. Upload settings are correct. I’ve tried setting the custom field as “TinyMCE + TinyBrowser” by itself and within FF Matrix 1.3.0, both resulting with the same error.

Strange… I test it with different system and the same configuration - all was fine. If you used firebug - could you pls. send me a header request to TinyBrowser (I need to check a GET parameters)? And one more test - put the custom field with “TinyMCE + TinyBrowser” and the second (in the end) with TinyBrowser standalone. Is standalone still will be working?

Having both side by side producing the same error (see attached).

But diving into GET parameters gave the clue. I can confirm the It’s All Text! add-on for Firefox alters the field name for this extension when used in combined mode. Uninstalling the FF add-on fixed it. I hope there is a work around for this though, I really like that add-on 😊