Jump to content

nikos

Senior Member
  • Content count

    116
  • Joined

  • Last visited

Community Reputation

0 Neutral

About nikos

  • Rank
    Member
  1. Hello, how can we set a 2nd level tax to be applied only in specific products? Thanks in advance for any help!
  2. Hello Cavallo, in windows servers, server load isnt provided. Kind regards, Nikos
  3. Hello, the product has been updated for Whmcs 6x.
  4. Hello Hostxido, seems like we are almost done. I believe tommorow it will be published with compatibility with 6.x. I ll report here on this thread when it will be published. Thank you for your patience, Nikos
  5. Hello, no, the product has not been updated to whmcs 6x yet, due to very low interesting on this product by the whmcs community. So we focused our development on other whmcs products like abuse center e.t.c. Anyway, since I do understand that it is absolutely necessary to update it, I guarantee that our dev team will make it whmcs 6x compatible, during the next 5-7 business days. Thanks for your message, Nikos
  6. An update has been released today. The update fixes a few minor issues. New feature added: Email notifications for admins when any port on any server doesnt respond. New Product Page: Advanced Server Status
  7. Hello, sorry I didnt check earlier this thread. The addon is not yet updated for Whmcs 6.0 We are these days in the process of updating all our addons to latest version. I ll post back as soon as it is ready for 6.x Best regards, Nikos
  8. Hello, here is the link: http://www.multihosting.com/other-services/web-applications/whmcs-advanced-server-status.html - - - Updated - - - Hello Crescent, no, the product has not been updated for Whmcs V6, yet. I believe it will be tested and updated during next week. I ll post back here in this thread when the update is completed.
  9. Abuse Center is an addon that is necessary for any web hosting company that wants to have a well organised system for client's abuses. There are 2 versions of the addon: Basic & Plus (example of plus version is screenshot: abuse-center-6). Basic Version. The admin creates unlimited abuse types, for example, phising site, hacked site, server abuse e.t.c. The admin creates the abuse issue for the client, manually. The statuses of the abuse issue are: open issue, resolved, unresolved. The admin decides when creating an abuse issue, if he will notify via email the client about it. There are various strategies here: for example, a web hosting company wants only to have a very organized list of abuses, so the system is used only for internal use between the admins. The admins will be able to search for abuses via inteligence search, or see in a client product all active abuses of this spesific client or also have a short or full list of all abuses in all clients. The second strategy is to apply the "abuce center" in the frontend client area. This way, the client, after notified by email, will be able to go in his client area and check active abuses and abuses history. NOTE: This is not a ticket system, so the client is not able to answer in the abuse system. Our research while developing the addon showed us that if we let the client answer in the abuse system, then this would make it confusing for the client with the default ticket system. It would be like there are 2 ticket systems, which is defenetily not the point of this addon. Also: the admin is able to define which email account will be used for each abuse type. For example, content abuse issues, could be sent via: abuse@mywebhosting.com and server resources abuse issues could be sent via: server-monitoring@mywebhosting.com All email templates, for each abuse type you create, can be predefined and ready for future use. When the client take spesific actions to solve the issue, he informes the admins. Then the admins can update the issue and/or close the issue as resolved. Further than the mannual abuse types and issues, we have also added, for Cpanel Server only, a MySql size abuse type. This works 100% automaticly. The admin chooses the servers to be monitored and also for each hosting product, the spesific limit of mysql size. When an account of a clients, hits the limits, the abuse issue is opened automaticly, the report is sent to client. With the use of a cron job, if client takes actions to lower the Mysql size, then the abuse issue, is closed automaticly (Resolved) without the need of an admin manual action. Abuse Center Plus Version. This version was made for the needs of our company, but we decided to take it publicly. The important point here is that this version uses the 1h.com HIVE product, for server monitoring and optimization. In other words, think of this version, ONLY if you use 1h hive. What this version does is that it monitors the CPU executions of each website of each client. The admins can put limits of cpu executions for each product and server. If the client catches the limit, then automaticly, the system creates a "CPU EXECUTIONS ABUSE" issue for this website. This system, looks for the total executions of last 30 days. So, lets say you have shared hosting and put a limit of 500.000 executions / 30 days. If a client has 490.000 executions, then the system (via cron job) opens a "Warning abuse issue". If next day, this limit goes higher than 500.000, then the "warning abuse' becomes "Open Issue'. In case client takes actions to lower the cpu executions, next day cron job, automaticly, closes the issue as "resolved". This is very usefull if you sell different hosting level packages. For example, you can set for shared hosting an execution limit at: 500.000 / 30 days. The email template that will be sent to the abuse, may notify him that if he doesnt solve the issue in certain period of time, then he should consider to upgrade to a higher level of hosting, for example "semi-dedicated hosting". In semi-dedicated hosting, the admin should put a limit for: 1.000.000 executions / 30 days, then have a different email template for abusers of this limit e.t.c. e.tc. Sorry for my poor english. Let me know if you have any questions or feature requests about the addon.
  10. The addon improves the functionality of contacts by giving the ability to the admin to enter custom fields to contacts. This could be useful for various reasons. For example, at our company, we use Advanced-Contacts addon in order to enter billing-invoicing info at the contacts, which by default, its not possible. Furtermore, you can assign products and domains to contacts in order to have a better organized info, which is very useful especially with clients that have a lot of contacts. Optionaly, you can give your clients the ability to edit their contacts and associate products and domains to them. Note: the addon doesnt affect the invoicing, meaning that the invoice is still created for main client. Mainly, this addon was created by our development team, for the needs of our company's accounts department but at the end, we decided to take it publicly and any feature requests are more than welcome, so as the addon becomes more and more... advanced! More info and purchase: multihosting.com
  11. Thank you John for the link. I hadnt noticed that.
  12. I d like to ask the below: is there a way that we set the automated system of suspension to be different for each product? For example, we d like to have a policy of shared hosting suspension in 7 days overdue and suspension on vps in 1 day-overdue. Thanks in advance for any help
  13. Hello, I d like to ask the below: 1. is there a way to have custom fields in contacts and not only on the main profile of the client? 2. in the order process, we can create a contact for the domain owner. After the order, where/how can we check in whmcs admin area, which contact is the owner of the domain? 3. How can we handle the scenario, where our client, orders a product on behalf of a third person? How can we have in this scenario, the "third person" to be invoiced directly? Thanks in advance for any help.
  14. Hello, a minor update (V1.2) has been released today. This update fixes a bug in cron job, where in some scenarios, the logs were not deleted.
  15. Today we released a new update, which fixes a minor bug in Uptime cron job. Also added: 1. Checkbox in admin panel so as the admin can choose if the Server Status will be visible public or only for clients. 2. Ability for the admin to choose the time (in seconds) that the script will timeout, when checking the servers ports for uptime/downtime. We hope you enjoy the new additions and fixes! PS. Any feedback or feature requests will be very welcome since there is an active and continuous development of the addon.
×

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated