Paul

Themes will eventually (hopefully in 3.3) have the ability to set CSS overrides. This would allow you to fix the shadow colors if they are not added to the theme as a color option, while at the same time, keeping it part of the theme.

You can have different emails go to different departments with different default priorities. You can also have multiple email addresses forward to the same department email, but they cannot affect the priority. Simply put, the default priority for the department is the priority that is used when an email comes into the department. It sounds like there are possibly 2 separate feature requests here. If so, please open a new thread for one of them. 1. Set priority in content of email 2. Set priority by email address, allowing multiple email addresses to pipe into the same department.

Well done! Can't really even tell it's Blesta.

This is part of CORE-1225. Closing this thread as it's a duplicate. Please continue any discussion at http://www.blesta.com/forums/index.php?/topic/2440-client-profile-sticky-notes/

3.4 should be out this year.

We appreciate the feedback. Right now it's not possible to remove the hash in the subject without breaking it. Doing so would create a new ticket on reply. I would suggest starting a new feature request thread for this specifically. It will require more thought and discussion, but a workaround might be possible.

Target for the final release is mid-week, so, within a few days.

This is not currently possible, would you like me to move this to the feature request forum? It's something that could certainly be done. The practicality of the feature is something I'm not as sure about -- most customers are not going to know that they can do this. And it may need to be a setting, as staff may not want customers to set the priority via email. Often times customers will select the highest priority not on the basis of their request being urgent but because they would like a reply sooner.

This sounds like a usability related feature request. If there is only 1 option during checkout for payment, select that option by default. ??

Yubikey is supported for TOTP tokens, see http://docs.blesta.com/display/user/Logging+In#LoggingIn-ForYubiKey This may not be what you mean by "native" support though.

Looks really nice!

No. It sounds like you're doing it exactly right. What he means is that you can't sell something that contains our code. For example, if you take a module we wrote, tweak it a little and sell it then you're effectively selling our code.

That sounds unrelated to the import process.

You should try doing an import from 5.3, it may work. I did recently see a thread where someone had trouble importing from 5.3, but it may have had more to do with the way they had things set up than 5.3 specifically. The only way to know if it will work is to give it a shot. If you get any errors or have missing data, etc let us know. The docs are here - http://docs.blesta.com/display/user/Migrating+to+Blesta

One thing of note in this release is the Export/Import theme feature. Now you can share themes! Settings > Company > Look and Feel > Themes. Final release soon.

Congrats on the very first publicly shared theme!

It looks sexy. Could be a problem if you have a lot of feeds though.

I've added CORE-1221 to address this. Expired coupons would appear under an Expired section while active coupons under the default Active section.

The time between beta's is usually about a week, but it can vary. For a minor release, ie 3.x there are usually 2-3 betas. We will be releasing 3.2.0-b3 next, and after that it will likely be final release. The point of the beta's is to eliminate bugs though, and that's our goal. Our focus will always be on quality rather than meeting a predefined timeline.. so, things can change.

Yes, the "Name" that you enter for the fields are passed in the POST request. Label is the name that is displayed, like "Domain Name" and Name is the field name, which could be something like "domain_name". I believe this is a multi-dimensional array however, so you should capture it in your API file using something like. $response = print_r($_POST, true); file_put_contents("/path/to/file.txt", $response); My PHP is rusty, but I think that would work. Make sure file.txt exists and is writable, and after the POST request is made, open the file and see what the array looks like and you'll know where to pull your data from.

You monitor email sent to MAILER-DAEMON@ your domain? I'm guessing that your mail server bounced a message to the support system and this email is the result

I wonder if this is something Mike (Licensecart) can do.

We are looking into this. It should be corrected if it hasn't already been corrected in 3.2. I'm assuming you're running 3.1?

Adding this for future reference.. This error appears to occur when a transfer is in progress but is not complete. When the transfer has completed, this error should no longer occur. See https://support.logicboxes.com/helpdesk/index.php?/Knowledgebase/Article/View/41/0/seeing-the-error-t3-error-website-doesnt-exist-for-order-id-when-searching-for-a-domain

Currently the Universal Module can currently only do POST requests to an external URL. We have plans to make this more robust in the future.