Jump to content

Paul

Blesta Developers
  • Posts

    6,728
  • Joined

  • Last visited

  • Days Won

    841

Everything posted by Paul

  1. Take a look at the sample welcome email here http://docs.blesta.com/display/user/Multicraft#Multicraft-WelcomeEmail This section specifically will send the client their Multicraft URL, User, and Pass, which is different from their Blesta login.
  2. I have created task CORE-1453 to address passwords in the Account Registration email. We personally do not include passwords in our account registration email. It's generally a bad idea to do this, and it should not be included by default. This will affect new installations only. The separate issue about rotating the email log is open to further discussion. Personally, we prefer to keep an entire history of email with the customer. I personally check email logs often, especially if there is a dispute. But, we understand that the log could become quite large, so an option to truncate the log which is not enabled by default may be a good option.
  3. Why not just mark them as inactive? Unless you're browsing inactive clients, you'll never see them again.
  4. I've been using SplashID for a long time. They have the mobile app, and a Desktop app. They can sync over wifi. No browser tie-ins, I have to open it, enter my passphrase and find the record I want. More secure that way though.
  5. How did you sort it out?
  6. I'm not a fan of cloud storage of passwords. If the data is compromised, it could potentially be brute forced. It's also possible that a vulnerability in the encryption algorithm might be discovered in the future. I use a password manager, but the data is only stored on my devices. I could be robbed, but A. that's too much work for 1 set of passwords, and B. hackers prefer to work in the comfort of their parents basements.
  7. Paul

    Release 3.3.0

    Just FYI, I moved all the beta threads over.
  8. We have an internal roadmap, with certain basic features planned for each release. 3.4 is contact logins with ACL permissions, contact and client two-factor auth, and a Knowledge Base. (And maybe a mass mailer, depending on time) 3.5 is.. secret, for now
  9. That's the plan. If there is time we *may* work on it for 3.4, but not if it will delay the release.
  10. Oh hey, I see my name. Yeah the license is legit, the non-profit looks good. I'd buy it, but I have an "in" and get all the free Blesta licenses I need.
  11. It sounds like it's for making payments from iOS 8 apps only..?
  12. That's what it looks like, KB is in dev now.
  13. Nice work! Glad we could get those events in 3.3
  14. It's very basic, Company Name, Maintenance Mode.. then, your content. You can use markdown so you can make it as fancy as you feel like.
  15. Custom fields are specific to client groups, but every client must be in a group. If a field should exist in all groups, it will necessarily have to be added to each group. This task simply allows for a default option to be pre-selected.
  16. Glad that worked for you, but Blesta 3.3 does ship with an improved importer for whmcs. You'll need to install Blesta 3.3 in order to use the importer though and it's included. If you're happy with the import, then there's no reason to do this, but might be worth a shot otherwise.
  17. Did you follow the migration guide exactly from here? http://docs.blesta.com/display/user/Migrating+to+Blesta The error seems to indicate that some data may be missing that is expected. Enable error reporting in your v3 /config/blesta.php config file before trying a new import. Also, restore your database from after you did a fresh v3 install, or install again. v3 must have a fresh database before attempting an import. To enable error reporting, edit /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1); Then run the import again. If you get an error, there will probably be more in there, include it here.
  18. Ok, the latest version is available here - https://account.blesta.com/client/plugin/download_manager/client_main/index/5/ Make sure you're logged in. You want license_manager-2014-09-26.zip, make sure you back up everything first. Once you overwrite the license manager plugin and the license module, be sure to go to Settings > Company > Plugins and Modules and click to upgrade them.
  19. We'll be releasing an update to the license manager shortly. Probably Monday. Cody says this was resolved, though I can't find the task I am probably overlooking it. Update: Ah, CORE-1351 Does not ship with 3.3 because it's an extension. Will be in the download area once released.
  20. All patched up again today, after getting all patched up yesterday. If there's another patch to fix the previous patches I'm going to start drawing some parallels.
  21. Everyone *should* keep their software updated and a lot of hosting companies do make the effort. Still, there are many smaller hosting companies that don't. Much of the market consists of smaller hosting providers that have reseller accounts from larger hosting providers. Fortunately, the majority of them are now running PHP 5.3+, hence the pending minimum requirements bump.
  22. Anyone send you the decoded file? The ISP is telling me they are aware of the police investigation. I'm curious how it turns out, and wish you the best of luck.
  23. We sent a notice to the ISP
  24. Paul

    Release 3.3.0

    I may move some beta threads over before I close the forum. I'm in no hurry to close the forum right now as it's the typical post-release rush of tickets and am pretty busy. So... feature requests that have not been implemented, and bug fixes that have not been fixed?
  25. Paul

    Release 3.3.0

    We found an issue where in some cases you wouldn't be able to upgrade with a trial license. This may or may not have affected some monthly licenses. @flangefrog wasn't affected by this.. what you have going on is something very different, and I suspect may be related to your server. The data sent from your server is missing important information, and I don't know why. I can't duplicate in my testing. My suggestion is to try to roll back to 3.2 for now. You should only have to restore your files, as your database has not been upgraded.
×
×
  • Create New...