What is your server details: CPU and RAM? VPS, Shared or Dedicated?Could you please keep an eye on your community and server during next 1-2 days and update us if it's Free version that causing problems?
We'll try to investigate on that shortly.The only problem I see here, is Zend Guard loader, but previously we didn't have such issues mentioned.
What is your server details: CPU and RAM? VPS, Shared or Dedicated?Could you please keep an eye on your community and server during next 1-2 days and update us if it's Free version that causing problems?
We'll try to investigate on that shortly.The only problem I see here, is Zend Guard loader, but previously we didn't have such issues mentioned.
As I told you in the other response, the "known" label sounds wrong. For example, this response: with this label, people think it is a "known" problem by you guys... And if I change it in the translation, there will be no more option to "confirmed" or "known"... so, from "new" it will go to "in progress". But sometimes there is no progress in the issue and we only want to show the user that we know about the problem and it is really a problem and soon we will start handling it.
Cheers!
As I told you in the other response, the "known" label sounds wrong. For example, this response: with this label, people think it is a "known" problem by you guys... And if I change it in the translation, there will be no more option to "confirmed" or "known"... so, from "new" it will go to "in progress". But sometimes there is no progress in the issue and we only want to show the user that we know about the problem and it is really a problem and soon we will start handling it.
As I told you in the other response, the "known" label sounds wrong. For example, this response: with this label, people think it is a "known" problem by you guys... And if I change it in the translation, there will be no more option to "confirmed" or "known"... so, from "new" it will go to "in progress". But sometimes there is no progress in the issue and we only want to show the user that we know about the problem and it is really a problem and soon we will start handling it.
Cheers!
In your case, following actions should be done:
Add as many statuses as you'd like in database to any type of response;
Change default status in database to whatever you'd like;
Rename any statuses with Web Translation tool under Administration->Languages
And you'll have system like you want in workflow.
Chris Rolf wrote:
As I told you in the other response, the "known" label sounds wrong. For example, this response: with this label, people think it is a "known" problem by you guys... And if I change it in the translation, there will be no more option to "confirmed" or "known"... so, from "new" it will go to "in progress". But sometimes there is no progress in the issue and we only want to show the user that we know about the problem and it is really a problem and soon we will start handling it.
Cheers!
In your case, following actions should be done:
Add as many statuses as you'd like in database to any type of response;
Change default status in database to whatever you'd like;
Rename any statuses with Web Translation tool under Administration->Languages
And you'll have system like you want in workflow.
Leave a Comment
Login
/ Register
Loading...
Replies have been locked on this page!
No connection
Real-time notifications may not work
What is your server details: CPU and RAM? VPS, Shared or Dedicated?Could you please keep an eye on your community and server during next 1-2 days and update us if it's Free version that causing problems?
We'll try to investigate on that shortly.The only problem I see here, is Zend Guard loader, but previously we didn't have such issues mentioned.
What is your server details: CPU and RAM? VPS, Shared or Dedicated?Could you please keep an eye on your community and server during next 1-2 days and update us if it's Free version that causing problems?
We'll try to investigate on that shortly.The only problem I see here, is Zend Guard loader, but previously we didn't have such issues mentioned.
As I told you in the other response, the "known" label sounds wrong. For example, this response: with this label, people think it is a "known" problem by you guys... And if I change it in the translation, there will be no more option to "confirmed" or "known"... so, from "new" it will go to "in progress". But sometimes there is no progress in the issue and we only want to show the user that we know about the problem and it is really a problem and soon we will start handling it.
Cheers!
As I told you in the other response, the "known" label sounds wrong. For example, this response: with this label, people think it is a "known" problem by you guys... And if I change it in the translation, there will be no more option to "confirmed" or "known"... so, from "new" it will go to "in progress". But sometimes there is no progress in the issue and we only want to show the user that we know about the problem and it is really a problem and soon we will start handling it.
Cheers!
It's seems OK now. Maybe was just coincidence. The server log was not generated soon enough, so it has no data from the exact high load time.
Thanks.
It's seems OK now. Maybe was just coincidence. The server log was not generated soon enough, so it has no data from the exact high load time.
Thanks.
And you'll have system like you want in workflow.
And you'll have system like you want in workflow.
Replies have been locked on this page!