Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/10/2016 in all areas

  1. Kurogane

    Missing Nav Bar

    I'm not sure if is intentionally but when you go to Billing --> report --> Customize the nav bar is missing.
    2 points
  2. Hello All Again . i'm Alive BLESTA Connect is a single centralised interface to administer and manage all of your servers. Provides a single sign-on solution based on the Cpanel SSO . Utilising Single Sign-On Technology, BLESTA Connect allows you and your staff to access the control panels of all the servers configured in your BLESTA installation that support Single Sign-On with one click , no need to share root or resellers password with your staff . the plugin support permissions, so you can set the permissions for staff groups . Supported Modules : Cpanel (Blesta core) Cpanel Extended (you should setup it with access key) LogicBoxes LogicBoxes Extended More modules will be added if the panel support the SSO . this plugin requiere a the Pro (Silver) subscription . Order Link Plugin page Screen Shoot . LogicBoxes Complete list of released addons
    1 point
  3. Paul

    Missing Nav Bar

    This is undesirable but it's not technically a bug. Because the Customize tab is a different controller and because it's not registered into the nav under a new section (Like Billing > Customize Reports) or something, it doesn't know that it should be under Billing > Reports. This is how any other plugin would work as well, using a different controller, without registering its own subnav item. This makes a "fix" more difficult. Cody tells me that it may be able to be corrected using a route, but that's probably not ideal. It may require a more complex solution. Good catch though, I can't believe I didn't notice that myself.
    1 point
  4. Michael

    Missing Nav Bar

    Interesting never spotted that before and I've used it a few times, maybe I need to go to specsavers haha nice find.
    1 point
  5. No new events yet. I don't think any methods are being removed for this version, but that could change. Any methods with the @deprecated annotation are on the chopping block.
    1 point
  6. This issue is resolved in CORE-1879 for v4.0.0 of Blesta.
    1 point
  7. This issue is resolved with CORE-1877 in v4.0.0 of Blesta.
    1 point
  8. in v4 . is their any new events will be released with first version ? is their any known function in blesta v3 will be dropped in v4 ?
    1 point
  9. Tyson

    Add Client Via Api Tax Bug

    This issue is fixed in CORE-1942 for v4.0.0 of Blesta. You can run the following query to fix the issue in the interim if you encounter it after adding a new company: UPDATE `company_settings` SET `inherit` = 0 WHERE `key` = 'tax_id';
    1 point
  10. Updated ... 1.0.1 now with full screen option . and fixed the title windows . just re-download the plugin again .
    1 point
  11. Tyson

    Add Client Via Api Tax Bug

    Thanks for listing the data. No, that's not necessary. I believe you. The problem is that company 6 is set to allow inheritance of the tax_id field. Once that is disabled, clients without a tax ID will no longer inherit the company tax ID. mysql> SELECT * FROM `company_settings` WHERE `key` = 'tax_id'; +--------+------------+-----------+-----------+---------+ | key | company_id | value | encrypted | inherit | +--------+------------+-----------+-----------+---------+ | tax_id | 1 | | 0 | 0 | | tax_id | 2 | | 0 | 1 | | tax_id | 3 | | 0 | 1 | | tax_id | 4 | | 0 | 1 | | tax_id | 5 | | 0 | 1 | | tax_id | 6 | 123456789| 0 | 1 | <--- should be 0 +--------+------------+-----------+-----------+---------+ 6 rows in set (0.00 sec) The issue should be resolved once you run this query: UPDATE `company_settings` SET `inherit` = 0 WHERE `company_id` = 6 AND `key` = 'tax_id'; The inheritance may not be set correctly when you create a new company by cloning the settings of another, and that's something we can look into and resolve for the next release as apart of CORE-1942.
    1 point
  12. Thanks for the report. This is assigned CORE-1879. The error is meant to say that the action failed because the category contains articles that do not belong to any other categories. Each article must belong to a category, or you need to set the article to a category of "-- None --" instead.
    1 point
  13. I believe the ticket is not shown because no reply was created. Either tickets with no replies should be displayed, or a sort of "No content" reply should be created if no content exists. CORE-1877
    1 point
×
×
  • Create New...