Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/28/2013 in Posts

  1. Modules can define what appears here. CORE-710 is a task that will add a section to enter custom HTML with tag replacement for a Universal Module product to control what appears in the expandable area.
    2 points
  2. The user_id is a unique field per client. You can call Clients::getByUserId() to fetch the client. Something like the below may be what you're looking for: <?php ... $user = $api->get("users", "getByUsername", array('username' => $_GET['username']))->response(); if ($user) { $password_matches = $api->get("users", "checkPassword", array('password' => $_GET['password'], 'stored_hash' => $user->password))->response(); $client = $api->get("clients", "getByUserId", array('user_id' => $user->id))->response(); if ($password_matches && $client) { $api->post("clients", "setCustomField", array('field_id' => 5, 'client_id' => $client->id, 'value' => "my_new_value")); } } ... ?>
    2 points
  3. Disable ONLY_FULL_GROUP_BY.
    1 point
  4. What do you mean by add maintenance database? The backups are intended to be a full system backup. Exporting other details, like clients to a CSV would be best suited for the Billing > Reports section. If that sounds alright, let's open it up for discussion. Should we add a "Clients" report type to Reports for CVS export?
    1 point
  5. Paul

    Merge Clients

    It didn't make it in, unfortunately.. then we expanded the intended purpose of the feature to make it more robust, by allowing finer grain control over what is migrated.
    1 point
  6. We added several modules during the beta, as well as additional features and improvements to existing features. Still, adding new features to a beta isn't ideal because those features that are released towards the end of a beta don't go through as much testing before final release. With 3.0 out now, and known bugs being few, we're able to start transitioning to development for 3.1 and beyond. We are still less than 2 weeks after a major, full-rewrite, all new release and while there is a lot we want to do, and will be doing, stability is more important.
    1 point
  7. I would vote that the client can re-open a ticket at any time, unless he can easily link to old tickets from within the "compose" window. Ticket history can be very important for some problems. In any case, it's very frustrating when you want to add to a ticket and you can't because it's been closed.
    1 point
×
×
  • Create New...