Leaderboard

Hello, I'm trying the following: One service costs $ 5.00 incl. tax, that's $4.20 excluding tax. This service is created via package (using Universal Module). Now I want to offer a coupon for the whole $5.00 amount. But when the coupon is now applied to the service, it's calculated down to $4.20 - so the client has an invoice about $0.80 instead of free. (Per order form / api) I also tried setting the coupon to $5.95 - this would be $5.00 + tax. But this one is also calculated down to the $4.20 of the line item. Request: A. Allow coupons to be taxable. Maybe a checkbox when creating the coupon. This should be applied automatically. B. (Much better): Apply the coupon to the line item before it is taxed. This would make more sense to me, because nobody has to tax $0.00 - right? Thanks!

After reading the excellent Site integration tutorial - I quickly came to realize that we can modify almost all aspects of the Site. WARNING WARNING WARNING - ALWAYS MAKE A BACKUP BEFORE MODIFYING ANY FILES There are a LOT of *pdt files within a blesta install, and the one you want to modify is usually pretty easy to find. From the doc root of your Blesta install, simply do the following # find . -name "*pdt" This will give you a list of ALL the PDT files used for the presentation of the site. Now, say you have a little specific mod you want to do (and yes) I did. The Mod I wanted to make was really quite simple - it is on the Support page. (Portal -> Support) We are setting up several Support departments - we only have a single Support department listed where you can raise a request without being logged in, all other departments you need to be logged in. As it is not obvious, we wanted to add a little bit of extra text to the page. First, look at the URL of the Page you are going to: https://yoursite/client/plugin/support_manager/client_tickets/departments/ next list ALL the pdt files so we can identify what we want to modify, we went looking thru the list for a file that was a close match to the page path. ./plugins/support_manager/views/default/client_tickets_departments.pdt looked to be a likely candidate for what we were trying to achieve. First thing, we make a backup of the original file, just in case we mess it up and can easily revert to the original # cp client_tickets_departments.pdt client_tickets_departments.pdt_orig Then with your favorite editor, modify the file. We wanted to add a very simple message to the page <div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div> Well, we took a moment, looked over the code and found what appeared to be the place where we wanted to add the text to the page. <div class="heading first"> <h5><?php $this->_("ClientTickets.departments.heading_details");?></h5> </div> <div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div> <div id="departments" class="pad"> Now, when you go to Portal -> Support you will see what we added (see the attached Image) - In this case, it was pretty east to see where within the pdt file we needed to make the addition. Pretty Simple! The Final Step - remember, if you do an update or install a newer version that your mods may be removed. You should also be keeping a document somewhere of what files you modify and exactly what you changed, so in the event that an upgrade replaces the file you modified, you can easily put your changes back in place - and of course, making a copy of the files you modified as well is probably a good idea as well. Looking forward to seeing some of the other customization's that everyone does.

I think that some method by which to automatically sort clients into specific client groups would be good to have, so it's a good idea. Before we would consider such a feature, we would probably want to see some different use cases so that it could be designed in a way that is broad in scope.

Resellers are able to offer v3 licenses, however it's taking some time for some of them to get up and running. v3 is based on an entirely new licensing system. All resellers currently have the ability to add v3 licenses in our interface, but we are still working on the API so they can issue v3 licenses automatically in their systems.

I might be able to help if nobody else can. I have a dormant setup which you could use in case you don't have access to a dev setup.

Yay! This is a much needed upgrade to a good program!

Hi Paul, Yes this file works.

We are aware of this issue, though it appeared to be more limited in scope. It's suppose to be fixed in 3.0.2, would you mind testing the attached file? 1. Backup everything 2. Overwrite /app/models/services.php with the one attached. Let me know if it solves it. services.php

SolusVM deserves some praise for taking security seriously. You could argue that they should have been more security conscious earlier, but this was a good move.

1. Haven't thought much about that, but it's something we can certainly do. 2. Yes, we are planning to offer a verification badge. It will not be free, because we will need to audit the code to make sure it's safe. Those that want to purchase the service, and who pass our verification process will get the badge. 3. Good idea

Thanks Nearly getting there with the whole system.

Thanks but already done it

Also +1 for the domain needing to be checked if it is already in the client system.

Within no longer than a couple of hours, beta version will be ready. Afterwards we will thoroughly test it and eliminate bugs. If everything will go according to the plan. It will be released at the end of this week. In the worst case on Monday.

Running it manually will still run only those tasks that are ready to be run, which is why it did not run that task. To test it, just after the cron automatically runs, you can change the task to run every 10 minutes, then wait for 5 minutes to pass and change it back to run every 5 minutes. This effectively skips the cron from running it in the last 5 minutes, so that the task will now be ready to run. And running the cron manually at this point should run the task.

We are looking at ways to make it public, and may do so in the future. For now, we try to post the task # in the forums for bug reports and feature requests to indicate it's in our system. The same number is included in the changelog for releases as they are implemented.

CORE-696 and CORE-722 (allowing coupons when not enabled) are fixed for 3.0.2.