The "parser.lockfile" is blocking POP3/IMAP fetching

[FrightFactor]

Well thats my problem with Kayako as well. But i read the threads and we fixed the problem. But some Users shoudn't get so pushy. thats why i said, stop bitchin around. And i am a woman ), that has something to say *lol*

But i have to admit that TIME isn't one of Kayakos strength.

I own a Mailorder Company. We receiving over 400 emails daily. What we done in the past as we started to use Kayako. we shut down our phone service and started to just use the internet part. Which was and still is an effective way for my staff and the company. But when the software we're using, starts to shut down the whole business, we're pretty screwed. And in this times, you can't fail to answer your customers questions. They don't care if you have technical problems.

- side note: i just know someone who's working at a company where time isn't their strength as well. And a similar problem locked down the services at a mayor national bank. so their offices in germany, New York and Hongkong coudn't work as well. It got them days to fix it. What did the bank? The bank sued the company for damages and a German Court granted the damages. (and it isnt very easy (like in the states) to get a german court to grant something like that).

OK back to subject:

And thats something i missing at Kayako
if i see that more and more customers complaining over one Bug. Than you guys should stop working on all other versions you working on and start immediately hand out a hotfix for the software.

I guess, the users wouldn't mind to wait a bit longer for a new Version, if the very critical bugs would be resolved immediately and made available immediately. And not getting fixed after days and weeks and letting this thread filling up with complains.

There are still customers, who don't know much about FTP and Editing Files, and MySQL. And maybe got their Helpdesk installed by someone else. For this users a provided hot fix with instructions like download this cvs, open this file and edit this part of a file etc., isn't very helpful at all. Cause you can provide the best explanation how they solve the problem to these users, and still something goes wrong.

So it would be much better to say, HEY here's an ZIP File, open it and upload it to your server. Problem fixed. Thats a solution and everyone will appreciate it.

And the rest of the bugs can be fixed as usual.

Ok and now bitichin is over *lol*. The classic Fright Night is waiting on TV for me. Cyaaa

[NC Software]

Dear Ms. FrightFactor

This is not about one bug. I see your join date is recent, for those that have been around here for a while it's been constant delays. We've had to put up with nonsense long before John and Jamie ever came along. Waiting months on end for some "50-seat call center" which totally stopped development and then office space issues here and there, blah blah, we just want reliable software! We don't want nonsense, we need to operate our businesses and not lose tickets, have confused staff, and unhappy customers!

I have NEVER heard of anyone having a road map for BUG fixes! Seriously, that makes me laugh! How you can go from a STABLE to such an unstable so fast that you can't fix a critical issue (actually there are several) and republish a new STABLE in 24 hours! As a developer and owner of a software company, these practices concern me greatly. Especially when dealing with a company on the opposite side of the globe! On top of that, how does a product that has been out years all of the sudden have these critical issues?

I look forward to this nonsense ending and getting more frequent stable releases. It sounds to me like Kayako needs a change in management. Assuming there is any now, honestly!

[GoneShootin]

Will you really get the kind of results you need by having a **** slinging match over a public forum? I suggest that this **** be kept to a more one-to-one basis between you and whoever at Kayako handles this kind of customer relationship matter.

[John Haugeland]

Originally Posted by NC Software

Respectfully, this critical/show stopper is NOT fixed until it's available to customers via STABLE.

Wrong. Fixed means "this problem is fixed in CVS." And it is.

I am going to continue to work on the stable release, rather than to debate this, as the debate is not productive.

[NC Software]

I am going to continue to work on the stable release

Great idea - so your customers can actually receive the "fixes" and resume business operations without the lack of trust in their help desk software.

[John Haugeland]

There may be needed new updates to these instructions, as files in CVS are not static. More information soon. Apologies.