The whole confusion started with the failed blog post. People thought that it was just days away from the release but apparently we have some time before that. It's law that when you announce dates, rarely you can achieve them, not Joomlaworks but nearly everyone out there. Keep up the good work!

Sorry guys but Its becoming ridiculous.
14 days before it was said "in 10 to 15 days".
Now nothing again!

I understand that you want to be sure that everything works but since the first beta 14(!) months have passed.
That is unacceptable for professionals . How should the comercial offer succeed if in 14 months your communication is horrible?

I do not think that we need k2 anymore. I am watching K2 evolution in order to confirm my believe...

Working with Joomla directly is lighter and Joomlart, for example, produced Teline V without K2 and it is working like a charm!

Sorry to hear about that RGRA.

I was actually excited again to see the new version come out. And now again disappointed.

When you announced in July 2014 that it was coming "soon", then soon again in December, then eminent in December, then all quiet for months and treatment of users like they were disrespectful for asking, then announcement that it would be announced and then would be available after the Brazil thing, then "give us time to get home", then a week, then 10 days, then 14 days, then the impression that you believe that your users don't understand the concept of time as if to say "did we say days? Oh - silly English, we meant months, wait, no, seconds, er...give us time to have dinner and then it will be ready before you can say "K2". ;-)

Well - now it's September 26. It is a full 20 days after the end of the Brazil weekend.

It's not that I need the new version right now to move forward with anything - in fact we moved over to Zoo for our Blogs a while back due to some other issues we had with K2 and for the simplicity of Zoo config/setup, especially when just for Blogs. But there are a few things I like better about K2 and would like to use it again, but I'm reluctant with the support promise so poor here, and don't really want to load 2.x version when supposedly it will be replaced so soon.

It's just horrible practice - even for a free component.

Oh well, I'm sure I won't be the last one to complain about the delays. Disappointing. :(

I totally agree with Scott. I have kept silent on this issue over the past year however this last false launch date is just taking things too far. It's not actually the problem that its not ready yet, its the treatment of the K2 user base. I have used every major Joomla component over the past 10 years, both free and paid however I have never seen treatment like this. It really is quite appalling not to keep your users in the loop.To worsen things, K2 is a major Joomla component and this type of management makes the overall Joomla community appear amateur - something that Joomla has been accused of for some time by Wordpress users.

K2 Pro - No chance with this level of support. Alike many, I would gladly pay for K2 but I worry that this wont change things.

Joomlaworks moving to Wordpress - Good luck with that. I wish you all the best.

K2 is a great component that has been provided for free and I fully appreciate the work Joomlaworks have done however that does not entitle them to treat their users in any way they seem fit.

Regards,

Dave

I think we are missing the point here.
Joomlaworks is very a small company for such a huge project.
I think that passing it on to the community would be the wise thing to do, since they can still develop components for K2 that would be great.
Its a classic case, where the product becomes bigger than the product owner...

As I can see @ guithub the default answer to all bug reports is because the component options and the frontend are not ready yet, 3 from 4 open bugs was reported since 10 (our less) days ago. Looks like there is a new work to do, I hope I'm wrong.

Keep waiting.

I agree with Scott & Dave. By making lots of false promises and then not communicating when the dates are missed, Joomlaworks are treating their user-base with disdain. It is a very bad look and not at all good for instilling confidence in the company for the future.

Version 2 hasn't had a major update since about early 2014. There are an ever increasing range of problems using it. It is a pity but I am now seriously considering abandoning K2 as the only way forward. I am sure I am not alone.

Regards
Peter

Its understandable y'all are going through rebranding with the launch of v3 and a lot goes into that so the process takes time.

Right now I am feeling very disappointed with delays as I keep pushing my projects back (something I probably should be doing) in order to take advantage of the new k2 (i just feel its going to be worth waiting).... & most likely I am not the only one doing this.

V3 was presented in Joomla Day Brazil... How about just posting a V3 download link?... it would make a lot of us happy!

I think it would be fair to at least provide us with a link to k2 v3 standard (even if marked as RC), so we can get going on our projects with that version...


.

Hello Petar,

The beta version has been available for quite some time actually:
github.com/joomlaworks/k2-v3-dev-build

I am going to say something positive. I think the really big deal here will be the pro version. I doubt the 3.0, for I did use the beta, is going to change your life. I am really curious what extras will be with pro. Some nice category modules would be cool.

I'm just as keen to get my hands on the final of v3 as anyone, but you could all consider grabbing the beta that's been publicly available for quite a while and start working with that.

It's quite stable, although it does have some minor issues.

But the really important thing is you could be contributing to getting the final out the door by submitting issues.

At this stage, apart from Lefteris and Krikor, there's only about five or six of us actively submitting issues.

Krikor,
No offence intended, but this kind of response

The beta version has been available for quite some time actually:
github.com/joomlaworks/k2-v3-dev-build

is exactly the sort of thing I'm talking about. It says that you take no responsibility for still not having a release version available for download. It says quite clearly on that GitHub page not to use it for production and recently, you (joomlaworks) have said things like "the front end needs work". Well, the front end is the part users see, it's the part we work on to make templates, and if the back end is done but the front end is not, that is not terribly useful.

Again - this is about expectation setting, not just about having the newest version. I really don't want to build a new site with K2 v 2.x when v3 is supposed to be done "any time now". If I spend a bunch of time building out templates for K2 stuff and then v3 comes out with a template system that is different and causes me to have to redo them, I might rather use a different component than K2 to just avoid this problem.

This really shouldn't be that hard to understand, especially when it has been so long coming and so many times missed.

If I missed deadlines like this on websites for my clients (paying or otherwise), I'd have a huge reputation problem! I know I'm not the only one who feels this way.

Is it a lot to ask for an ACTUAL release date?

I don't disagree they could be better at communicating - it's definitely frustrating. I'm using K2v3 for a project at the moment after being told it'd be released at JoomlaDay Brasil and it's not looking like the release is going to make my deadline for delivering the project.

But it was my decision to proceed with v3 rather than 2.6 and I accept that. It just means that when it is released I'm almost certainly going to have to do a bit of extra work to get it up to scratch.

That said - it's worth trying that beta. Almost everything from existing K2 front-end templates work exactly as they always have. Krikor can supply the new WIP front-end templates if you want additional functionality and there's a couple of bits and pieces that fix the few minor problems you'll encounter with current templates. I think there's only one issue I have that I've had to resolve with custom code.

I hope this is not too dumb of a question but how do I install the beta on a test site. I certainly would like to play with it. :-)

Another odd question. How can I add a photo to the icons that display with my messages here in this forum?

Just go to the github repository here:

github.com/joomlaworks/k2-v3-dev-build

Click the 'download .zip' button and install via the Joomla installer.

Hi,

I've been dropping into the Joomlaworks website occasionally for months hoping for some update on K2 version 3.0. I've never used K2 before, but was considering moving articles on our site from Easyblog to K2 for content (blogs+other uses), and didn't want to do that while V3 was imminent. I can see now that there is little certainty about when V3 will be ready for release, but I'm wondering more about what it will contain/look like when it is released.

• Is it so different to K2 version 2.0+ ? Is there any information about what;s included in the V3.0 release, and demo videos etc.
• Does anybody know if there are slides form the Joomladay conference - was it actually presented there, and if so, are the slides available anywhere in English ?
• What are the reports from beta users ... is K2 V3.0 going to be worth the wait - are there serious problems contributing to the delays. I'm wondering if there are technical or other problems we are unaware of, and if there is a possibility that K2 v3 may never gain traction as a result ? If so, even V2 would seem like a wrong move?

best regards & thanks.
Aidan

I've been testing the beta extensively - I've been using it in the development of a large project because I didn't want to be locked into v2 for the duration of this site's life.

For most users v3 won't be a revolution.

But if you work with template overrides and extraFields, it's definitely worth the switch.

Just the ability to have multiple extrafield groups assigned per category, or to scope the extrafields to items, categories, etc, is extremely welcome.

The old squeezebox modals are gone, thank jeebus.

The new data layer makes for some super interesting possibilities in terms of serious customisation.

The ability to create your own extraField types? Mindblowing - absolutely 100% worth the price of entry if this was the only thing that was different in v3.

It feels faster on the frontend.

The backend looks better and there's some nice new features in there, but I actually think the usability has gone backwards on that front.

So mostly a positive experience. The beta is stable enough that it's usable right now - although you'll need to fix a few problems yourself (limiting character counts on introtext for search/tags/authors isn't in place yet so you'll have to do it in the code).

I too am feeling the frustration of the delays, particularly at this last hurdle, but I'm optimistic that the release is going to be fantastic, when it arrives.

Kelsey Brookes wrote: I've been testing the beta extensively - I've been using it in the development of a large project because I didn't want to be locked into v2 for the duration of this site's life.

For most users v3 won't be a revolution.

But if you work with template overrides and extraFields, it's definitely worth the switch.

Just the ability to have multiple extrafield groups assigned per category, or to scope the extrafields to items, categories, etc, is extremely welcome.

The old squeezebox modals are gone, thank jeebus.

The new data layer makes for some super interesting possibilities in terms of serious customisation.

The ability to create your own extraField types? Mindblowing - absolutely 100% worth the price of entry if this was the only thing that was different in v3.

It feels faster on the frontend.

The backend looks better and there's some nice new features in there, but I actually think the usability has gone backwards on that front.

So mostly a positive experience. The beta is stable enough that it's usable right now - although you'll need to fix a few problems yourself (limiting character counts on introtext for search/tags/authors isn't in place yet so you'll have to do it in the code).

I too am feeling the frustration of the delays, particularly at this last hurdle, but I'm optimistic that the release is going to be fantastic, when it arrives.

Hello, ty for your input. Do you have any experience of ZOO? If you can compare v3.0 and Zoo will be awesome, i am thinking if i will wait for v3.0 for a Movies Site i am preparing or go for ZOO. Ty in advance!