It's not possible to install OSSN 6.0 with TextareaSupport 6.3, because Textarea Support 6.3 is not included at OSSN6, you have to register and download it on another Website.

Good news, Balamurali:

Textarea Support 6.3 comes with the necessary interface included now to enable TinyMCE image uploads and pasting images from your clipboard. It needs Ossn 6.0, though.

So, please upgrade your site to Ossn 6.0 first, then install Textarea Support 6.3 and Blog 6.1

I just found something interesting...

https://www.tiny.cloud/drive/

Will explore this further and see if makes sense and would work.

Thanks Z-Man. Appreciate the help.

Creating my article is easy this way, but educating the users of the system to do this would be the challenge. Hope there is something with latest TinyMCE, that helps with this. Will research. It would be nice if this opens the camera or gallery interface in the mobile phones, so easy to upload images.

Thank You.

Thank you for the details, Balamurali.

TinyMCE would need an extra interface to store direct image uploads or clipboard content on a server. This is not available by default, and that makes sense because there's no standard which way to accomplish this task where these files should be stored.

In other words: As long as this interface has not been developed, you can only link to images which are already stored somewhere. This must not be a completely different server, you may use images of your Ossn photo albums, too.

So, my way of displaying an image inside a blog is

• store that image inside an album of my site, first
• view that image inside my album (MYSITE/photos/view/35 for example)
• right-click that image an choose "Copy image location" (resulting a link like MYSITE/album/getphoto/4/6ba0545e1677ba93497ca44dda78fb2e.png?size=view for example)
• use TinyMCE's toolbar button [Insert/edit image]
• and paste the formerly copied image url

Admittedly not a really comfortable method, but currently the only workaround.

You take a screenshot of some screen in your laptop. This copies the image in the clipboard. Then you go to the blog editor and paste it there.

The image is attached and seen on the edit blog screen also, but not visible in the Post or in the blog view.

Another issue: in the TinyMCE editor there is no option to pick a file of an image (*.jpg or *.png) from the computer or mobile. There is an option to only give a link, which means the user should have a place on the internet where they could store these images and then use these URLs.

Please guide me with a solution for both the issues. Thank You.

I have no idea from where you copied a link like that.
Please provide the detailed steps which way you did it.

At least it's not a valid image format. Image files should end like .jpg or .png

Important/Critical issue:

While adding a blog, when I copy-paste an image (from the clipboard), it shows fine in the TinyMCE editor, but after saving it doesn’t display the image in the article, and also doesn't display the image in the related post (of the blog).

While editing the Blog, I could see the image though.

When I check the Html code in the TinyMCE editor it shows like below... it is a blob and the blob is not loading in the Post and the Blog! Is this a known issue?

Code:
<p><img src="blob:https://<OSSNURL>/6fd118ac-1555-45fe-a25d-e5dde6d2c423" alt="" /></p>

Please help. Thank You.

Thank you for the effort of updating the component. Unfortunately I can not tell you if the update worked because I solved it before I saw you did.

I did a little digging and it seems that Tiny MCE and Chrome have had a love/hate relationshop dating as far back as 2016 causing this type of problem. The fix is simple, but why it works I don't understand.

If you get the blank field instead of the editor all you have to do is go to Chrome settings --> Advanced --Reset settings that fixes it. Afterwards you can simply activate all plugins and extentions you use in Chrome the editor keeps working. Don't ask me why.

In any case the problem is solved this way and I moved on to another issue I have but that is not for this page, because it is about another component. ;-)

Thank you very much for your helpful feedback, Everwijn.

Unfortunately, I don't own a Chromebook to verify why the editor is not? or too late? initialized, but I have changed the code a) to allow a little more initialization time, and b) if that still fails to pop up an alert box to let your members know that their device/browser is not compatible, and c) hide the input field afterwards in order to make editing impossible.

Please give it a try and

1. temporarely disable all components (Blog,Bio, About User) that depend on TextareaSupport
2. Delete TextareaSupport 2.9
3. Upload and enable TextareaSupport 2.10
4. Re-enable the candidates of step 1

I'm curious of the result.