Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 12/17/2013 in all areas

  1. Paul

    Fraud Record

    CORE-935, thanks for the suggestion! No ETA at the moment, but it's in our system.
    2 points
  2. Michael

    Fraud Record

    Fraud Record, for Blesta would be amazing in my opinion, it checks a database for unwanted customers, it's a bit like a neighbourhood watch team, but for webhosting. Any fraud gets submitted to the database, and you can check to ensure you don't get the same unwanted customers. Stop Fraud Clients, Report Abusive Customers. Combine your efforts to fight misbehaving clients. I used to use it on the last billing system I used and it helped much better than Maxmind, because bad clients are bad clients. http://www.fraudrecord.com/ API: http://www.fraudrecord.com/developers.php
    1 point
  3. On a clients page their is an option to disable auto suspension for that client. This does not work. I disabled auto suspension on a client with an overdue invoice last night and it still suspended the clients service. 3.0.4 CentOs 6.3 Php 5.3.26
    1 point
  4. There is already a task, CORE-547 to hide optional fields from the client area and order pages. It is tentatively scheduled for 3.2, but may be pushed back. I'm not sure if this is exactly what you're asking for though.. this would allow you to set, from optional fields, which ones not to display at all. Are you wanting the fields rather to be displayed only as read-only? Feature requests aren't always answered right away, sometimes we purposely let them run on to gauge support. As we plan future releases, we also revisit the feature request threads on the forums.
    1 point
  5. 1 point
  6. Paul

    Version 3.1 Eta

    The plan is for a 3.1 beta starting at the end of this week. Betas are open to all direct customers.
    1 point
  7. Reported bugs are confirmed and then added to our issue tracker where they are resolved. Members are encouraged to confirm reported bugs by other members, provide feedback, and additional details. Once we add a bug to our issue tracker, we will typically confirm it in the thread it was reported and lock the thread. Before reporting a bug, please search the Dev Tracker to see if the bug has already been reported. To report a bug, please start a new thread for each bug and include all relevant information about the bug. Here's a basic list of information we may need. Whatever you can provide so that we can quickly understand and replicate the issue is much appreciated. Describe the issue you're experiencing. Provide detailed steps necessary to reproduce the issue. List any generated errors. (The "Oh Noes" error pages are very helpful.) Include the URL the error occurred on, relative to the installation path, ie "/admin/login". Attach screenshots. Include your configuration settings, i.e. OS, version of Blesta, version of module/gateway/plugin if applicable, version of PHP & MySQL.
    1 point
×
×
  • Create New...