Jump to content

dnwklin

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by dnwklin

  1. Ok. The problem is wired enough. Previous, I use MySQL database hosted on cleardb.com and receive above error. Now, I use local mysql and problem solved. Not sure why
  2. I downloaded but still seeing SQLSTATE[HY000]: General error: 1364 Field 'name' doesn't have a default value on line 124 in /var/www/******/customer/lib/model.php Not sure if it is related.
  3. Did you update the link? I download it and seems are the same file as before
  4. Ok. Now I know why it does not create ticket. I try to manually create a ticket as a client, and this is the error message I received. SQLSTATE[HY000]: General error: 1364 Field 'name' doesn't have a default value on line 124 in /var/www/******/customer/lib/model.php So, what's this problem? First time seeing this.
  5. No, uncheck that box didn't solve the problem. The email was marked as read but no ticket created.
  6. opps. I need to uncheck that box. However, the email was send from an account that associated with a user
  7. I figure out that default IMAP port is 143 but it was defaulted to 110 in Support Manager Pro(as well as non-pro).OK. Now I upgrade to the newest version and configure it correctly. I could see those new email being marked as "READ". So no dout that support manager pro retrived the email. But no ticket was created
  8. I know. Previously I was manager to get it work. But after re-install, I forgot how did I manage to get it working in IMAP. So, I hope there would be an error message so that easier to find out where is the problem
  9. I try to configure IMAP email processing. It did not work and didn't give me any error message. I hope they could show error somewhere so I know what's the problem
  10. No in Tools->Logs->Modules it says success. But I guess, it could be because I run the blesta under suexec and other security measure piss it off. But now, I cannot click "activate" button again because the domain is already registed. The product stuck in pending status and I can't do anything about it.
  11. I did add departments and add staff to it. But I still don't see it
  12. dnwklin

    Release 3.2.0

    Ok. It's my bad. Somehow FileZilla was set to use ASCII mode.
  13. dnwklin

    Release 3.2.0

    Yes. I did run /upgrade/ Everything else works fine, so I think I upload it to correct folder.
  14. After install "support manager pro", I find out that when client login and click "support pro", they did not see any option to create a new ticket.
  15. dnwklin

    Release 3.2.0

    When I upgrade my system, interesting things happen. All icon disappered. I use firebug to check and seems the path to vendor folder isn't correct. There is one extra "../" Don't know how to fix it
  16. How do you force it to be active? I found no way to do that
  17. Does it mean I can use it on V3 only untill Aug 2014, or I can use whatever v3 version release before that date?
  18. I try to manually activate a domain for a client. When I click "activate" in staff portal, the module give me a red banner at the top. However, the domain is successfully registred. But in Blesta, it still show up as pending. How do I force the status of this domain to be activate?
  19. CORE-924 does not exist in project issue?
  20. I am still hope if there could be a integrated console.
  21. My server that host Blesta has both IPv4 and IPv6 address. My home Internet has IPv6, so I install the blesta in IPv6 environment. But when I visit the site on a network that only support IPv4, it gives me an error says license not valid. What should I do about it? Thanks
  22. I tried the plugin on my instance. And it appear to me that 1.) did not show .com as a domain extension 2.) sometimes have difficult to check availablility on the domain
  23. I am test the Proxmox module with blesta. It works pretty well untill I found this problem. After a user purchase a VM, in their account there is a link to console. However, when I click on that "console" link, it did not give any console but instead it display my VPS Node username(root) and an encrypted password for my root user. Why is that?
×
×
  • Create New...