Leaderboard

This always shows that message, so as not to leak your usernames to a potential attacker. We may add an option to display an error if there is no match, but for security reasons we recommend leaving it this way.

You don't need a admin folder to restrict by path. For Apache servers you can use the location example as stated above to do it. More information can be found at https://httpd.apache.org/docs/current/mod/core.html#location For security you should probably rename your /admin area to something else. Change the following line in the route.php file. Configure::set("Route.admin", "admin"); to something like Configure::set("Route.admin", "ziggyzoo"); to change the path to /ziggyzoo. Hope that helps.

See what you get for fixing the bugs? Now they want to find more.

Fixed in CORE-858 for v3.0.6, which will be released soon. This issue can cause the cron to fail to finish creating invoices, so you may want to pre-patch yourself. Update /app/models/services.php and change: $service->package_pricing = $this->getPackagePricing(); to: $service->package_pricing = $this->getPackagePricing($service->pricing_id);

We wouldn't want them to get bored and run out of things to do

We met the Vision guys a couple years ago, really good people. http://www.flickr.com/photos/48176820@N04/6028837095/in/photolist-abKnea I look high in that picture, though.

Thanks for the link, interesting requirement. Works now.

Would be nice to see noVNC integrated for console access. http://kanaka.github.io/noVNC/

Lol, neither am I, it's just fun to make fun of Paul from time to time lol

Lol. I'm not complaining about it Loving Blesta so far!

I'd rather have vision support done first...and I've already spoken with them and they are currently trying to figure out where to prioritize it (they already have login integration).

We have not set a date for the beta, it'll be ready when it's ready! (Hopefully by the end of this month)

Added as CORE-858 so we can take a look into this issue.

Deleting a server/module row that references packages and services starts to get a little complicated, as you have to ask what will happen to those child packages/services. We have scheduled CORE-209 for v3.2 that will determine how what you described gets handled, but it's currently not designated a bug; instead, an improvement. Based on your example canceled service--even if you didn't have a service, you couldn't delete the server because it has a package associated with it. Uninstalling the module works (for now), but opens up problems with packages being undeletable. The solution we're leaning toward seems to be to unlink packages/services from a module upon uninstallation.