Ok, that's great.

K2 for me was the best Joomla extension. K2 is the basis of Joomla. I'm glad you're back :)

I look forward to the new version. Good luck! :-)

Best regards,

Jan

+1

Maybe we should move the discussion about K2 v2.7 to a new topic. (I've installed in on a test site and have some comments)

If you can find a bug or you have an enhancement proposal feel free to report it at Github github.com/getk2/k2/issues

For regular support issues, just open a new thread.

Together with Lefteris Kavadas (backend guru) and Krikor Boghossian (frontend guru), K2 v3 development has re-ignited and is on a steady track for a realistic release date by late April 2016...Within a month's time, we'll make every effort to finalize all remaining issues and release K2 v3 :)

getk2.org/blog/2549-k2-v270-released

Great news. I am glad to hear that! Success!

We update some sites K2.7.0 and the interface is amazing. Fantastic new features.

I wonder what is to come in K2v3

Have a site that imports feeds as k2 content daily and site size is growing very fast which impacts our server storage capacity.

Would love to take advantage of S3 integration and upgrade to v3.
- Is this feature of v3 stable at this time?

On more general note...
How far from production use is the current dev version?
Or better yet which features of dev v3 are not finished?

This list would save a ton of hours on verification of things working properly.

Appreciate the help.

Correct me if I am wrong, but you are concerned about the disk size the images occupy?

With v3 you can reduce the image sizes being used (some template changes might be in order)

You would still need to delete any image sizes not being used.

If disk space is your main concern you need to do the following
a) Backup, I cannot stretch this enough.
b) Empty the contents of the /media/k2/items/src/ folder but keep the index.html file.

This folder stores all the original unresized images which are not used by default in your site (but backup first in case they are needed).

Hi @DSPI try using the ImageRecycle extension.

You can configure it to process images of specified folder(s).

www.imagerecycle.com/cms/joomla

The extension replaces your images with optimized images automatically (time intervals or on save)

I personally use it to optimize my images before uploading to K2 (tip: save your images at 100% quality and let ImageReady do the optimization, for smallest size/highest quality images)

Krikor wrote: Correct me if I am wrong, but you are concerned about the disk size the images occupy?

With v3 you can reduce the image sizes being used (some template changes might be in order)

You would still need to delete any image sizes not being used.

If disk space is your main concern you need to do the following
a) Backup, I cannot stretch this enough.
b) Empty the contents of the /media/k2/items/src/ folder but keep the index.html file.

This folder stores all the original unresized images which are not used by default in your site (but backup first in case they are needed).

Hi Krikor, yes we're concerned about storage. Currently hosted on Amazon EC2 and the instance is "growing" like crazy - mostly due to the cache folder size. We are planning to add features to the site and I'm not sure what will be needed in the future, so I'd like to keep all files on the site as they are normally stored (structure wise) but would like to reduce the size of the EC2 instance.

K2 v3 has Amazon S3 listed as a storage option and that sounds like a perfect solution for the site. I just didn't want to jump into upgrading to v3 blind.
To test all k2 features would be very difficult and even if those we currently use may be working correctly. I'd like to know which features of v3 are stable currently and which ones are being worked on to determine if we can jump to v3 before the stable release is put out.

Joe Campbell wrote: Hi @DSPI try using the ImageRecycle extension.

You can configure it to process images of specified folder(s).

www.imagerecycle.com/cms/joomla

The extension replaces your images with optimized images automatically (time intervals or on save)

I personally use it to optimize my images before uploading to K2 (tip: save your images at 100% quality and let ImageReady do the optimization, for smallest size/highest quality images)

Thanks for sharing the link Joe, I will take a look at this - seems promising on first glance.

In this case, we are getting images/articles imported directly from a news agency just as they are released so I do not get a chance to optimize them before upload.

@DSPE then you would configure the extension to process that specific folder.

The extension developer was very responsive answering my questions. I would recommend contacting them for further details.

Joe Campbell wrote: @DSPE then you would configure the extension to process that specific folder.

The extension developer was very responsive answering my questions. I would recommend contacting them for further details.

I also use this plugin/component and can confirm that it is both excellent and does the job at a relatively low cost.

David

@DSPE The front-end is not finalised, the core functionality is all there but I cannot guarantee it will play along nicely with extensions built specifically for older versions of K2.

I would not recommend using it in a production environment but if you want to give it a try you should use it in a staging server first before updating your site.

Should you run into any issues, feedback is really valuable to us.
Please report them at github.com/getk2/k2-v3-dev-build

Ho hum.

Well I thought I'd give it at least a few days into May before saying anything...

K2 v3 development has re-ignited and is on a steady track for a realistic release date by late April 2016, especially now that K2 v2.7.0 is also released (a requirement to upgrade to K2 v3.0.0).

Yes, you read correctly. Within a month's time, we'll make every effort to finalize all remaining issues and release K2 v3 :)

That was written on March 18, referring to the realistic release in late April. Now here we are again with a missed date and still 48 listed issues on Git.

So what is the new date?

Anything new about it?

It would be nice if we could get some specifications and news on (new) features, so we all can prepare ourselves for the next release. What do we need to take into account, are there issues that we will run into, what upgrade path is there, etc.

Another month delay after promising release dates. Worst is lack of information...

Yep - so another month later, I go and look at the Github and I see we have gone from 48 to 52 fixes need to be done and 48 of those are the same ones that were there last month. So, it looks like that initial steam has given way to nothing getting changed in a month again.

sigh...

The release for K2v3 has been announced for late April. Now were are in the middle of june and I'm waiting nearly 11 months for the global permissions of user groups ( look here ).

Why is it taking so long again? I understand that Fotis has a small amount of time for the K2 development, but after the delayed release of K2 v2.7 I've expected a better estimation for the K2v3 release date. Can we expect a release until autumn?