Textarea Support Download 2.10

This component/theme works with latest OSSN version.
German ~Z~ Man 2 years ago

Textarea Support

This is a helper component in first place working under the hood and taking care of proper WYSIWYG editor initialization.

Version 2.5 comes with multi-language support now. That is, if you surround your text like ...

<div class="textarea-language-en">
Your English text will be displayed here ...

<div class="textarea-language-de">
Dein deutscher Text w├╝rde hier erscheinen ...

... depending on the last two characters of textarea-language-XX using

XX = de (German) or XX = el (Greek) or XX = en (English) or XX = eo (Esperanto) or XX = es (Spanish) or XX = fr (French) or XX = he (Hebrew) or XX = it (Italian) or XX = id (Indonesian) or XX = ja (Japanese) or XX = nl (Dutsch) or XX = pt (Portugese) or XX = ro (Romanian) or XX = ru (Russian) or XX = tr (Turkish) or XX = zh (Chinese)

only that part of the texarea content will be displayed which complies to the currently chosen language of the logged-in member, while the other parts are hidden.

Note that Version 2.8 comes with a much stricter dependency check. That is: As long as TextareaSupport is in use by other active components (like Blogs, Bio, etc) it can neither be disabled nor deleted. Thus, in order to disable or delete TextareaSupport you have to deactivate all dependent components FIRST. The new layout of Ossn 5.3's component page will list these components like that now:

enter image description here


V 2.10

  • experimental but hopefully working fix for issues with Chrome on Chromebooks as reported on the Blog component page by Everwijn Overberg

V 2.9

  • requirements adapted to Ossn 5.4

V 2.8

  • added support for responsive images
  • enhanced set of allowed HTML tags like <span style="something....">YOUR CUSTOM STYLE</span>
  • compatibility with TinyMCE 5.x

V 2.7

  • allow embedding of Youtube and Vimeo videos

V 2.6

  • Indonesian language file added, license update

V 2.5

  • New setting "Javascript and SVG support". Since it has been shown that the SVG support added with version 2.2 brings the same dangers as the activation of Javascript, both options have been combined and can only be activated or deactivated together now.
  • added multilanguage support

V 2.4

  • included site's bootstrap css now to achieve better 1:1 results between editor preview and final view on site

V 2.3

  • fixed issue with disappearing input field labels

V 2.2

  • added SVG Support for Ossn WYSIWYG editor (any valid SVG may be entered via Tools -> Source code now)
  • added missing language files

V 2.1

  • handling of field label fixed

V 2.0

  • initial release

Developer's note:
Don't code any <textarea>....</textarea> elements anymore.
Instead, use the built-in plugin of this component like

echo ossn_plugin_view('input/textarea', array(
    'label' => 'LABEL_OF_TEXTAREA',
    'class' => 'ossn-editor',
    'name'  => 'NAME_OF_TEXTAREA',
    'value' => html_entity_decode(CONTENT_OF_TEXTAREA)

especially if you want to pass your field to TinyMCE.

As TextareaSupport takes care of proper TinyMCE loading and initialization, there's no more need of referencing the editor's javascript in your own component in any way.

German ~Z~ Man Replied 2 months ago

so in the end it turns out as already expected: There's a PHP file upload limit on your server.
Try to find and fix it - otherwise be prepared to run into similar issues with other larger components or themes sooner or later.

us Mark Watson Replied 2 months ago

That solution worked for me. Thank you!

German ~Z~ Man Replied 2 months ago

Try the following:

  • Unzip the archive locally
  • Move the vendors subdirectory outside of the archive (that's the large part)
  • Re-Zip the unzipped
  • Try uploading that archive
  • in case of success copy the vendors subdirectory via FTP or SCP to components/TextAreaSupport
  • Enable the component
us Mark Watson Replied 2 months ago

Limits are all 1G. Nothing is blocking it. I have uploaded videos that are way bigger. Also increased the OSSC limits in the .htaccess file and that didn't help. Is there a way I can manually upload it via FTP and sql query to install it?

German ~Z~ Man Replied 2 months ago

Thank you, Mark.

The url you sent is the general url of Ossn's component uploader used by any other component, too.
And as you wrote, other components are uploading fine.
So what's the difference?
TextAreaSupport is much larger than any other component I know.
Thus, a lot is pointing to upload limitations on your machine, and in fact I found an interesting link pointing to a similar issue ...

So please find out whether there are any special Apache modules installed or anything else is preventing larger uploads.

us Mark Watson Replied 2 months ago

Requested error url in the server log: /action/admin/com_install
Other components install just fine.
Log entry:
Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0

German ~Z~ Man Replied 2 months ago

This component is/will be stored on your regular webspace
And if this space isn't accessable it's a hosting issue in first place.

In order to get an idea, please check your server log file(s) and provide the exact url of the page which is returning the Forbidden (403) message.

us Mark Watson Replied 2 months ago

Why would you delete my comment? Until this component stops causing servers to throw the "Forbidden You don't have permission to access this resource." error when we try to install it, it is worthless. That renders all the components that depend on this package worthless as well. Instead of fixing it, you delete every comment discussing the error. WARNING - This component may not install on cpanel hosting servers.

gb SzSocial Media Replied 7 months ago

Thank you for your work much appreciated.


Developer: ~Z~
License ossnv4
Type: Tools
Minimum Requirement: 5.4
Latest Version: 2.10
Last Updated 1 month ago
Repository Url View Repository