Happy Anniversary to this thread!

My guess is that some legal issue associated with this delay.
Are you JW guys diverging ideas about company future after K2v3 out?
Perhaps a problem with some (copyright) code involved in K2v3?

Nothing is slower than lawsuits ...

Hello Krikor. We're right here.

Maybe I did not use the best words. When I say support, it is not about supporting the K2 version. K2 it was always perfect.

My question is "what is the impact on templates and structure to update a K2v2 version K2v3?".

I say this because in large projects structured on K2, we make several customizations and use plugins (which work very well). Depending on the launch period of the new version, and depending on the impact that this will cause the codes, you may need to work several hours and change many things to continue functioning as before. Note that the customer will not want to pay for it from here 1 month. The risk (and cost) in this case would be mine.

For this reason, I am afraid to continue working with K2 and take this risk. I preferred to look forward to the new version.

I hope that has now become easier to understand my question.

I'm not criticizing you, just presenting a doubt for the businesses of my company.

I get you.
In terms of compatibility with 3rd party extensions, I cannot say much. It really comes down to the devs of each extension.

My advice as a professional to a professional would be for the time being, until the launch of v3, use 2.7 for production sites which require a lot of 3rd party extensions.

Do not forget that v2 will NOT be abandoned. The 2.7 series will still continue to exist and it will be supported and actively developed.
You will not have to spend countless hours updating all your sites.

This will ensure BC compatibility for users who have sites with 3rd party extensions and will allow new sites to be developed with v3.

In this thread there are several mentions of K2 v2.7. On the download page the most recent version is 2.6.9. Where can we find v2.7 and what are the differences with 2.6.9?

2.7 is the DEV version of K2 and the last major release of the 2.x series.
You can find the repo here: github.com/getk2/k2
You can download it here: getk2.org/assets/get/

The major differences (among others) include a major revamp in the UI, sh404sef integration will be moved into a plugin, introduction of batch operations (like v3), performance enhancements and many more.

Hello Krikor,

Can you explain me please, what is DEV version? DEV version is a development version, that is still unstable. It is so? About the version K2 2.7 in this thread is writes over a year...

Can I DEV version use on a live site?
When will the stable version 2.7?
The latest stable version K2 2.6.9. is for Joomla 1.5(!!), 2.5 and 3.x. In version 2.7 will be removed support for extremely old version of Joomla 1.5 and 2.5?

Best regards,
Jan

The 2.7 can be used for production sites. To be 101% sure you should backup. I personally use it in production sites as well.

The 2.x series will continue to support older versions of Joomla! while 3.x will only support the latest version.

This means that if you are stuck on an older version and cannot upgrade/ migrate to Joomla! 3.x you will still be able to use K2 v2.x.

Thank you for the quick reply. I'm not a programmer, but if will not removed support for Joomla 1.5 and 2.5, is not worse performance?

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.