Paul

The April Fools that keeps foolin. (Hint for others: Inspect the cloud image in the post, set background-color to black.. ie background-color: #000;)

Just a quick flashback to April 1, 2014. http://www.blesta.com/2014/03/31/parallel-payment-optimizer-video-free-plugin/

This is pretty cool. Are you thinking of having an option for a signature on the order form? I think this would be really good on a future quote system so clients can sign off on a quote.

Awesome, nice work! I want to see that on the marketplace when it goes live.

Does look better, do you have a diff you want to submit for review?

Agreed. If you don't mind, please create a new feature request. We've discussed this internally to some extent and want to get this right. I'm not sure if we have a task for it yet, but I'd like Cody to take a look and create the necessary task if not. A new thread would be perfect.

The largest concern people had was the display of the Tax ID field, and as Mike mentioned (thanks Mike!) that field can now be hidden. We want to add more control over more fields in the future, but if you just want to disable the Tax ID field, then you're good to go with 3.4.

Seems this went off topic. Everyone take a break and watch some BillingBRAWL. @ModulesBakery, feel free to open a new thread whenever you want to do a new poll. This one is 5 months old, and off track so I'm closing it.

Remind me once The Marketplace is live. I need to create some graphics for nice titles. I'd like to allow people to "link" their account with us to the forum, so maybe 2 different new titles: 1. Verified Customer 2.3rd Party Developer (Probably something better sounding, but you get the idea)

Not a problem at all. I sent you a PM.

Thanks for the post, and interesting thread over on WHT - http://www.webhostingtalk.com/showthread.php?t=1467936

Enable error reporting in Blesta To enable error reporting, edit /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1);

Yeah that was prior to A 3.0.0 beta release. We had 7 alpha releases, those that participated in that got that title. I would like to add a new title, and even a nice graphic like we have for 3rd party developers with listings on the marketplace, once that goes live. It would help bring attention to you on the forums. Thoughts on that?

I've also seen 500 server errors caused by extensions like Ioncube, re-installing Ioncube might be a good idea. If there are any other unusual extensions loaded, they might be suspect as well. As Jonathan mentioned, check your server error logs. Usually with 500 errors they aren't very specific, but could shed some light on it.

If you import products using WebsitePanel, they will be imported using the Universal Module, and will continue to be billed normally. Blesta just wouldn't be able to auto provision new orders, or provide any management features. You should do a test import. We're continually improving/adjusting/refining the importer, it works great for a lot of people, but some people have issues, it all depends on what your data looks like and how you are using it. Updating it to import KB articles probably wouldn't be terribly difficult, so if that's the only hang up then we're happy to work with you to add that functionality and you can help us test it. You found the thread on WebsitePanel, I wonder if ModulesBakery still has plans for it. WorldPay is part of CORE-149 (I just made it public), not a ton of requests for it, but we might be able to help get this one built.

Happy to take a look at the code if you want to post it, PM it, or email it. The SolusVM module is getting a lot of upgrades for 3.5, including configurable options and ability to order multiple IPs and remove specific IPs. Not sure about package change, Tyson wrote the SolusVM module and sort of maintains it.

Your domain and your hosting packages should be in different groups. There is a drop down when configuring the order form to select the domain package group, and a multi-select to add one or more other groups. If you separate them like this, then it should work

Can you link the API documentation? We'll need someone to take a look to ensure it's possible to support their new API. Doesn't seem to be many requests for it at the moment though.

Nope, and it's not been very highly requested. You may wish to start a feature request thread for this though, so we can gauge interest.

Awesome, thanks for the update!

Are you migrating from Blesta 2.5.4? If it's something less than 2.5.4 (ie 2.5.0-2.5.3) then it wouldn't work. The error seems to indicate an issue with the query, but I've never seen this reported before and it's hard to say without the full query. It appears to be fetching module row information. Are you importing to Blesta 3.4.2, using the Import Manager that ships with that version? MySQL 5.0.67 is fairly old, and it should work, but curious why MySQL is so much older than your PHP. Upgrading MySQL might be a good idea, but I'm not confident it would result in a better outcome.

If bounces are not rate-limited they should be. That may be the issue here, as Tyson mentions. Tyson, can you look into this further? Jonathan, this may not be the most ideal work-around, but you could disable the "Ticket Bounce" email template to prevent these emails from going out. The downside is that if someone sends in a legitimate request and it's not accepted, they won't get the notice.

Blesta gives PayPal a unique URL to post each IPN notification to so that the payment can be correctly applied. The URL contains the company ID, along with the internal client ID. This allows payments to be applied correctly even when the same person may have multiple client accounts, even across multiple companies. The issue is one we've discussed internally in the past, and I believe there were limitations to being able to make this work without re-creating the subscription. I suspect it may be possible by creating a file that acts like a proxy, taking the IPN request, and determining the internal Client ID and company to apply it to. Proxying the response back to PayPal. I'll bring it up again on Monday. If you have information about what URL PayPal notifies on whmcs installations, it may be helpful. I would really like this to work out of the box, as it removes an obstacle for migration.

Expose looks interesting. Even though it hasn't been updated in some time, PHP IDS does work pretty well. We have some tasks to improve it further, as it can result in false positives for staff in Blesta. For example, editing email templates. An option to disable PHP IDS checks for authenticated staff is pending. Eventually I'd like people to be able to use PHP IDS more, or whatever IDS system we ship with Blesta. It would be great too, if we were able to push down new rules to Blesta installs. If a security vulnerability were discovered, it would potentially allow us to push out a rule to block against it.

What data specifically are you concerned about? Blesta encrypts a lot of things by default, but modules can also control what they want to store encrypted so there is flexibility there. We don't use any secret proprietary encryption algorithms, it's all open so the data can be decrypted, with some effort. The database backups area in the settings should be restricted for staff groups that you don't want to have access. Under Settings > Staff > Staff Groups, edit the staff groups and remove permissions for those that should not have access. Without access, they will not be able to change the settings or generate a backup manually. The encryption key currently should not be changed, but a utility that would allow you to re-crunch all of your encrypted data with a new key would be a good idea, it just hasn't been a high priority yet. A passphrase can be set for batch credit card processing, and the passphrase can be changed or removed without affecting the encrypted data. Cheers!