Jump to content

Paul

Blesta Developers
  • Posts

    6,683
  • Joined

  • Last visited

  • Days Won

    838

Everything posted by Paul

  1. +1 for this, iDev is fully featured and has more features than ours will have.
  2. Did you apply the php7-hotfix included with 4.1.0? Sounds like the fix for PHP 7 was not applied when you were upgrading.
  3. What version of Blesta are you using? There was a bug in, I believe, 4.0.0 that prevented that from loading if the servers were not in a server group. Even if you're not running 4.0.0, if your Interworx server is not in a group I would suggest adding it to a group and see if selecting the group will cause the Interworx Packages to load. If you are running 4.0.0, I'd suggest upgrading to 4.0.1 at minimum (4.1.0 preferably).
  4. I have marked it as planned. Also, CORE-1091. Domain manager is a higher priority, but this one is getting up there also.
  5. Try changing it to 0. The error message will be the same regardless of the minLength, but this is the only location within the directadmin module that sets a requirement of 5.. so this must be it. Otherwise, it's your DA server returning the error, but I doubt it. (You could confirm by checking the module log Tools > Logs > Module Log) When you edit the service, do you see the password asterisked out in the password field? ************ If this field is empty, it explains the error.
  6. Yes that's correct. Are these long passwords stored in Blesta, or only on DA's side? Blesta is checking the password length as it is stored locally.
  7. Paul

    WHMCS Migration errors

    That's probably why. The importer is intended to be used with a fresh install of Blesta.
  8. direct_admin.php defines a minLength of 5 for the direct_admin_password. Search ~/components/modules/direct_admin/direct_admin.php for "minLength", and you'll see a value of 5. You could try decreasing this temporarily to say 1 and see if that allows you to change the server. When finished, I'd suggest changing the value back.
  9. A new Square gateway (alpha) is available for testing. To install, download the attached , square.zip unzip and upload the "square" directory to ~/components/gateways/nonmerchant/ and visit Settings > Company > Payment Gateways to install and configure.
  10. Paul

    WHMCS Migration errors

    I ran the import without error, it went smoothly for me, so I'm not sure why you got the error.. unless it was an older version of the importer. The updates we made in 4.1.0 final seem to work pretty well, and I haven't come across an import I've attempted that has failed in that version yet.
  11. I think it's a good idea. +1
  12. The task is open., but yeah it's been in there for a while. Hasn't been a high priority.
  13. I mentioned this to @Jono and he was going to create a task and investigate.
  14. I'm glad we were able to help get the data imported!
  15. A lot of companies are "one-man shows", there's nothing wrong with that. It's probably not a good idea to pretend there are a lot of people if there isn't, it's a bit dishonest, but I understand why they do. People tend to look down on "one-man shows", and I think in most cases that's unjustified.
  16. Are you seeing this with another official module? Or is it happening with a custom module that has no module rows?
  17. If you can send the login to an SFTP server you operate that would be great. PM me either the user or pass, and email sales or support at blesta.com the rest of the info so it's split up. It's the end of the day here now, but we could do this in the morning around 9 or 10am pacific time so if it's available then, great.
  18. Invalid user ID? This should be resolved in 4.1.0 final. Are you certain that it's not one of the beta releases? If you would like, we can take a backup of your whmcs database and perform the export here, and send you the Blesta database that results securely via SFTP. If we run into any errors during the import, we'll correct them, and update the importer if necessary. And, of course, delete everything when we are done.
  19. Just re-save your staff group. Settings > System > Staff > Staff Groups. Edit and save without any changes
  20. Staff all use the default language. We do have a task for staff to be able to select their own independent language. Once this is added, then it would be possible to change the default language. See CORE-1750
  21. If you have Spanish installed (Settings > Company > General > Internationalization), clients will be able to select it when on the portal or checking out. As an admin, you will always see the default language (English unless you change it), even when "logging in as client". So it would appear Spanish to them, and English to you. I hope that helps
  22. Mike's Blesta installation is up and running, and BlestaCMS is their own creation.. I don't see any reason there would be license issues with it. Maybe it's unrelated.
  23. My opinion is that Mike needs to communicate. There hasn't been any public communication, and I think that's a mistake. People are generally pretty understanding if they aren't left in the dark.
  24. Is the path defined correctly under Settings > System > General: Root Web Directory? Should begin and end with a forward slash, and be the same as your document root. Also check the Temp Directory. The default is /tmp/ but some servers don't allow access to the system temp directory. I'd suggest creating a tmp directory within your users home directory, above the doc root, and setting it here. Also, are you running 4.1? There is new file-based logging, and you can check your "Log Directory" on this page also and take a look at the files in that location.
  25. What was the issue, in case it may be helpful to others? I was going to add to be sure to delete the files that were removed in 4.0 from 3.x.
×
×
  • Create New...