3.11.00 STABLE announcement discussion thread

[Ryan Lederman]

Originally Posted by mopa

In the Downloads - under manage category I am not able to delete a category as when I press the delete link - nothing happens due to an "error on page":
Line 281
Char: 58
Error: Unterminated string constant
Code: 0
Url: index.php?_=downloads?_a=managecategories

Is there any way to fix this?

This is due to a typo while updating the en-us locale. Open up /locale/en-us/downloads.php and look for the alert text. There will be two newlines "\n\n" -- if you remove those, you won't have this problem any more. You may want to grep and remove all the occurances of "\n\n" in the /locale/en-us/ folder.

We are aware of this problem and it wasn't known until it was too late. We will be releasing a patch within the next few days that addresses this issue.

[Ryan Lederman]

Originally Posted by NC Software

This is why software companies should "eat your own dog food" (use your own software) PRIOR to release. The fact Kayako uses an old version of SupportSuite themselves is a huge failure in that they won't be aware of issues as they don't even use what they sell. Once again, Kayako is lucky, they have the ultimate role model - vBulletin. You'll see a new version of vBulletin running before it is released, they use it themselves BEFORE they push it out for production. They show their confidence, they can test the quality, they simply do it right. Kayako simply does it wrong time after time after time, they simply do NOT LISTEN! They have no commitment to quality, security, or customer satisfaction!

This is totally unfair, Neal. The fact of the matter is that you don't know what happens behind the scenes here, and you are making blanket statements just because you don't see the help desk upgraded.

I have personally been trying to get Varun to upgrade the help desk since last week.

We do listen to our customers and take their opinions very seriously. We do have commitment to quality, security and customer satisfaction. To say otherwise is just unfair, and a flame as far as I'm concerned. Some of us are working EXTREMELY hard to make the products the very best they can be. Keep that in mind.

[craigbrass]

I totally agree with you Ryan. Some people here just bash Kayako constantly for no reason. It really does annoy me.

[Ryan Lederman]

Hey everyone!

Just an FYI: 3.11.01 STABLE is up and ready for your consumption. Please see our recent announcement http://forums.kayako.com/f3/new-build-3-11-01-stable-13114/#post58927

This build addresses several of the issues discussed in this thread.

[ziaka]

Originally Posted by Ryan Lederman

Hey everyone!

Just an FYI: 3.11.01 STABLE is up and ready for your consumption. Please see our recent announcement http://forums.kayako.com/showthread.php?p=58927

This build addresses several of the issues discussed in this thread.

Is there any way to get the changed files only? I have a ton of language changes that I just made from the last upgrade and would hate to have to do them all again.

Thanks

[NC Software]

What are the fixes/change log for 3.11.01 as your change log in the members are isn't showing changes for a long time. I want to know if I can turn GZip back on as it corrupts the sub-menus with an "undefined" label.

[Jamie Edwards]

Originally Posted by NC Software

What are the fixes/change log for 3.11.01 as your change log in the members are isn't showing changes for a long time. I want to know if I can turn GZip back on as it corrupts the sub-menus with an "undefined" label.

Hi Neal, gzip does not always do this for all people, and it may well be a system dependant thing (seen as though gzip is not a SupportSuite feature but a system feature), so I would simply try it yourself and see what your results are.

The changes in this build are a fix for the cookie problem for client users and a JavaScript fix for some "Are you sure?" confirmations.

[Brent]

Ok I am confussed: a few days ago a version was released as stable..

Now 3.11.01 STABLE - in not so many days - does this now make 3.11.00 unstable?

As much as I love developer jargon - how many more stable upgrades will come out before a real stable version is released... I really hate potentially paying to have things updated within days of one another... and with a ton of custom templates this is a major issue...

[caitlyntw]

Originally Posted by craigbrass

Jamie explained this in another thread. Because of the fact that a check needs to be done to make sure the user has an active support contract, this modification has to be implemeneted EVERY time they upgrade. Because of this they don't often upgrade.

But what does that have to do with Kayako upgrading their own installation of SupportSuite? It has nothing to do with user licenses as the upgrade takes place on their own server and won't allow users to access the actual file.

Most companies run their own development versions to test out the software.

So I don't see anything wrong with NC Software's suggestion for Kayako to update to 3.11 or whatever the newest version is before a public release. (I'm sure they do this on some scale already, but using their own latest stable release and having to go through the upgrade, might motivate the employees to do more thorough pre-release testing. )

[Giray]

Originally Posted by Giray

Upgraded to 3.11.00 stable.
Does anyone else have 'status change' issues. Upon staff reply, our status now falls back to default. Note that my personal option is set to "Unspecified" so that's not the issue.

Upgraded to 3.11.01 and I still get the same result. A staff reply forces a status back to default (new ticket in my case).

[craigbrass]

Originally Posted by brentwic

Ok I am confussed: a few days ago a version was released as stable..

Now 3.11.01 STABLE - in not so many days - does this now make 3.11.00 unstable?

A bug that was fixed late caused these problems and was only picked up after it was released. This update was released quickly to fix the issues.

[Jamie Edwards]

Originally Posted by craigbrass

A bug that was fixed late caused these problems and was only picked up after it was released. This update was released quickly to fix the issues.

Craig is correct.

[Brent]

Well do not take this wrong but then it was not stable upon initial release... I will not get into a discussion about software testing etc.... but to most, well at least me when I see the words stable it means it was tested in BETA then released - not Released as Stable then needing bug fixes...

Is there anykind of protocal for what consitiutes a STABLE, BETA or ALPHA release...

As from what I can tell (and trust me I do not know how your ssytem works) but should these releases not be BETA tested then released as STABLE.... if not then you will have the bad rep of releasing non stable STABLE releases...

[craigbrass]

Maybe the version that is about to be marked as stable should be given to the testers. That version, if working correctly, should not be changed if released as stable. This would make sure things like this do not happen.

[Brent]

bingo.....