Hello Peter,

I'm sorry for the late reply. It seems not possible because to be listed in the Shared Media, the image should been processed by Easyblog Media Manager. It won't work if directly upload to the shared folder.

Ok, I understand.

And, would be some way to trigger this processing in the background like with a CRON or something?

Hey Peter,

Unfortunately that wouldn't be possible right now However, in EasyBlog 5.1, we plan to scrap this multi image variant's altogether and just stick to 1 single size keeping things much more simple and efficient

Hi Guys, Hi Mark

Just curious:

in EasyBlog 5.1, we plan to scrap this multi image variant's altogether and just stick to 1 single size keeping things much more simple and efficient

What would this one single size be?

I am curious as I am about to resize 47 images.
And there will be more to come...

thanks

Paul

Hey Paul,

To simplify things, we plan to just use the exact image that you uploaded and if you have configured a "maximum" width / height in the settings of EasyBlog, it will then resize the image that you uploaded. As simple as that, versus having to resize a single image to multiple sizes (Which I believe some of the users are complaining about disk usage)

Hey Mark

Got it thanks.
Makes sense to me

have a good weekend

Paul

No problem Paul

Hold on, if I read this right, you are only going to store 1 version of an image to be used in all points. This means images will be resized on the page. For people using full width post images and nickel with blog modules, this will be a page load weight nightmare. I have to strongly disagree with this move.

Your old media manager used to scan a folder when loaded and generate the thumbs, why does the new one not do that? Also having the default image source to be post only and adding yet another layer of complication to the folder structure and still no way to turn those folders on and off just adds to the problem.

I truly hope you reconsider image sizing in 5.1 having just one image served is a really bad move - say I have a blog module with 5 blog posts and I'm using an image width of 1170px in my post - the page weight created by this would be massive.

Please take this into consideration.

Rowan

I believe they plan to make thumbs on demand for each size like many other components do. Is all about simplifying user experience, not overcharging the whole internet.

Anyhow, after such a big reaction my post has driven I would like to insist in letting the media manager receive pictures through FTP and then putting them available to all bloggers, private blogger, etc depending on the deploy folder.

This is a "MUST" for pros. I enjoy this feature with HikaShop and makes implementation to corporate clients much easier and satisfactory to them.

Thanks for reconsidering.

Hey guys,

This idea is not enforced yet and we're still discussing the possibilities. The idea is to only use a single copy of the image at a specified (maximum width / maximum height) at the back end.

With EasyBlog right now, we are generating 4 different image sizes and we have received huge amount of complaints about disk usage

We're still weighing in several different options right now but feedbacks are always appreciated

The way you used to handle it through the template was perfect. It allowed us to set-up the sizes we needed and remove the ones we didn't.

I have been asking for an age for something similar to the OP's request, which is a switch to default media to shared only. All of my clients use the shared folder only and the hoops they have to jump through to do it are off-putting.

As far as ftp upload is concerned, can you not trigger your image creation script on folder view in the media manager? That way when there's items that haven't been processed, they are done then and there?

Thanks

Rowan

Hey Rowan,

Thanks for getting back to me on this! By the way, I am hoping that I could get myself over to Joomla day UK this February and meet up with you guys again!

We actually did try that option where media manager would scan folder for changes but it often times out because let's be frank, if you are going to use FTP to upload files you are definitely going to upload a huge bunch of files When that happens, all hells breaks loose and media manager would fail to render altogether because it's trying to process / recompile so many image files at one go.

All these "processing" needs to happen at the background and this is actually why most operating systems has a meta file that stores all these information