Leaderboard

wait my new release of "Admin tools" plugin , you can add/remove custom primary/secondary staff links , primary client links .

I will be showing you a new theme I am working on, I hope this time I can finish it and deliver it to the community.

1. Check that your staff account has been added under Support > Staff, and has access to all departments. If you don't have access to all departments, it's possible the tickets were imported and you just don't have access to them. 2. WHMCS allows you to create credits out of "thin air", and Blesta creates a transaction for the total amount of credit a client has in an effort to balance their account. 3. What's broken with the transaction list? 4. Revenue reports are based entirely on transactions. Since you're importing from WHMCS, if Blesta has to create transactions in place of manually entered "thin air" credits that existed in WHMCS, then this will skew revenue reports. Filter out transactions of type "In house credit" to get a more accurate picture. The error: Integrity constraint violation: 1048 Column 'option_pricing_id' cannot be null on line 124 sounds like there was a missing price in the data being imported. Cody or Tyson may be able to provide more information on how to identify any such records in WHMCS and correct them prior to performing a new, fresh import.

the plugins link names in "plugin_actions" are not multilanguage in Table: plugin_actions . for example , if we install the support manager or client documents or any other plugin that add action , the action name is added to database with the language that has been installed with it . if the plugin installed in admin side in english , and the client has spanish or frensh language set , the link will be shown in english . this is not a bug , as the name set in the table plugin_actions already . what we need is improvement to how to get the action name . 1 - make action name inserted in array for every installed language. array( 'en_us' => "english name", 'fr_fr' => "french name", 'ar_sa' => "arabic name" ) the only probleme here is if we install new language in the system , it wil not have any entry for it . 2 - load the name from the language file if exist . make client or admin interface has mixed word in two different languages has no sense for me and for my clients .

i have tough for a easy solution , what i have arrived , as we have already the plugin_id in this table , we can easy get the plugin directory . we should add a new language to the plugins , let say plugin_name.php . then load the file plugin/".$plugin_name."/language/".$client_languege."/plugin_name.php . the file plugin_name.php should only have the plugin name , description , and widget/actions names .

the ETA this week will be released with some HOT feature , block admin area by ip , block acces to uninstalled plugins via , add/edit/delete custom links in client/admin side . now i'm making a full rewrite to this plugin . if you want to add custom link , you should add it to the Table: plugin_actions . nav_primary_client = client side . nav_primary_staff = admin side .

module for ovh domain .. great idea. go with it . EDIT : i will donate to you when you release it .

We are working on a module for Websitepanel, shall be released soon.

3.3 has certain hooks and things.

Just FYI, this field can be disabled in the next release, 3.4 per CORE-547 and CORE-1443

I use the module Internet.bs ,but Internet.bs has a query limit and it sucks so much work for nothing. Ok I'll do module for OVH

That's right. With gateways that support tokenization, Blesta stores the last 4 encrypted and the expiry date. The last 4 are stored so the client can identify the card in the payment account, and the expiry so that the client can be notified when their card is expiring and needs to be updated. CVV data is NEVER stored in Blesta. If we implement token storage for eWay, it will then support both local and tokenized storage of card numbers. Some people prefer local storage, because it means they are not "locked" into using a particular gateway. Of course, tokens are much more secure and we recommend using token storage whenever possible.