William White wrote:
This will not be a popular post.
I think that the problem lies with open source and "free" in general.
All "free" cms and extensions to them are "free" for us to use and change if we like. There are not guarantees for all environments and more especially no guarantees with mixtures of components.
When we rush to upgrade from stable, tested, and fixed versions of the cms or an extension, we become a part of the testing process in some ways. Sometimes components lag way behind the cms release cycle, especially when there is a short term cycle as in 3.0. I still have stable 1.5 with k2 2.4.1 sites running without errors and with addins that cause no problems along with 2.5 sites with k2 2.5.7.
If it doesnt work when i test it, I wait...and do not hack the core (except for testing and bug reporting) and when I as site owner have tested completely, i go live with upgraded software. This can be seen by the advice given by the official joomla site about who should upgrade to 3.0 and also on many of the different dev's sites answering the same question. Things are in a constant state of evolution.
I guess we as site owners are ultimately responsible
William,
Thank you for taking the time to reply. I agree with you completely on the points you make about open source, free cms and the fact that there are no guarantees with this 'free' method of building a website. My question though, was really trying to understand where I should look to for help in this situation? I've only just begun building my website, so everything that happens on the site now is a learning process and not mission critical. However, the Captify Content module was one of the main attractions of the template design which I decided to purchase for my website. After all, when money exchanges hands, it isn't free any more and the product must operate reasonably as described, no?
Naturally, I have the option to go to the template vendor and get a refund, since it was their product which I purchased and the product is no good to me without the intended compatibility of K2 and Captify Content. However, I don't really want to do this as I would much rather have the product work as described. Hence my earlier question on the K2 Forum, 'who is ultimately responsible?' If it was the K2 update that caused the compatibility issue, (which I assume was the case, since everything was working before the K2 2.6 update) then perhaps the K2 team could indicate the best solution, or even simple acknowledge it was a K2 issue. Failing this, then at least I can move on and find a new template that doesn't use K2, or Captify Content (whichever party is causing the issue).
So essentially I am looking for who might be able to help me, not who might I blame? Once again, I thank you kindly for your time.