Paul

4 days? well, still 5 days here, but yeah we are getting close. And I feel like we are almost ready finally. Still, working on Saturday. Oh, we got some languages exported from translate.blesta.com today, Blesta v3 looks pretty crazy in Chinese!

For building brands, I love names that have no inherent meaning. Fake words, but easily pronounceable. It reduces consumer confusion between your product and anything else, if they have heard of it, they have heard of your product. Also, stay away from acronyms, they are almost always a mouthful and often need explanation.

Custom fields are assigned to CORE-450, and they can be optionally stored encrypted. These fields will be by department, so you can have different fields for different departments, with whichever ones you want encrypted encrypted.

I'm certain more bugs will be found after release, and we'll do our best to squash 'em. It's the nature of software, unfortunately, pretty much all applications have bugs. So, find them! A bug found is a bug that can be fixed.

There are bound to be some we all missed, we'll take a look.

Click to manage the service, add the password and uncheck the use module checkbox.

Let's try to keep it clean, please. Hopefully you guys can come to an understanding outside of the forums. I think we can all agree, that well written, well functioning third party addons for Blesta v3 are good for the community. Let's try to foster that kind of environment.

I'm not sure if it will, it depends how they are storing the data. Also it looks like a final version of the whm** importer will not be out until after Aug 14th, however we will make it available in the download area as soon as it's ready.

1 week? Uh oh, we better get busy!

Very nice!

That was entertaining, lol

The module will have to support the functionality and views for those tabs, and check if the required plugin is installed before loading them. Cody or Tyson may be able to comment on how you check if a plugin is installed.

Thanks for the contribution! We do have CORE-611 open to add the "Order ID" field, but we'll take a look at your changes as well.

Centovacast is assigned to CORE-511 and tentatively scheduled for a 3.1 release. We are planning to implement their v3 API, which they recommended over v2. Are you planning to eventually upgrade your v2 installs to v3, or is this one of those things where v2 and v3 will be maintained separately by Centovacast?

I don't oppose either of these, and both are fairly popular. Anyone else use them?

No, it has nothing to do with licensing. It's just a common way to do caching. There's no need to make slower API calls for every page load when the data isn't changed frequently. This is more similar to what w3tc does for Wordpress.

I would cache it to disk. serialized array written to a file, read the data from the file instead.. then, randomly on page load make another API call and overwrite the file. 1% of page loads should be enough.

I think that's a good answer

I actually experienced a bug related to this yesterday because I have a cPanel license with buycpanel.com. They normally charge my credit card every month, but I strangely got a late notice. So, I login (to whmcs) and click the card on file, enter the CVV and go to pay, and it says there is an error. So I contacted them and asked if it was related to the whmcs patch, and they responded with..

Is it Aug 14th yet?

Here are a few.. CORE-604: Merge tickets CORE-605: Custom ticket statuses CORE-606: Staff signatures CORE-607: Split tickets Some of the others need more planning before I can assign a task to them, including the automatic actions, which we want to implement but it's pretty involved, at least how we want it to work.

Is it because of a KB you asked them for a quote on?

http://www.blesta.com/forums/showthread.php?t=1974 ModulesGarden wants some feedback on what modules they should build for Blesta v3. Please vote on this thread on the other forums. Thanks!

It may be MariaDB, do you happen to have a MySQL server available? dump the database and import it and update the config/blesta.php database details? That would be the most sure way to determine if it's contributing to the issue And if it is, I wonder if there is something we can do to fix it in MariaDB as well.

They are on their 4th build for the same patch now?