Leaderboard

Hello ALL . today , i will release freely a plugin that a must have for every blesta developer , is The Debugger. this plugin will let you debug any error with the Wonderful libraries Tracy and Kint . i suggest using Tracy. if you enable Kint you will get more debug info and trace, BUT YOU CANT disable it or Access the blesta website until you disable the trace from the file /vendors/kint_autoload.php . DO NOT USE THIS PLUGIN OR INSTALL IT IN ANY PRODUCTION ENVIRONMENT , OR USE IT AT YOUR OWN RISK . the plugin is hosted in open source , so any bug fix or pull request are welcome . http://blesta-addons.com/plugin/store/main/item/16/ Debugging with Tracy : Trace bar Debugging with Kint : Enjoy the life and Coding .

For me not OK . taking other code,and making some tweaks ,and release it in PAID mode !!! it was a generosity from you to release it free . also if i remember Paul has promise to send you 50$ for the fix ... can you tell me what feature have you added to the module?

I was a little surprised to find that this was missing from minPHP as well. Great solution @naja7host We will have to implement something natively sooner or later, will take a look at Tracy. Looking forward to the Github link when it's up, nice work.

To reiterate, most modules support remote API access to support automated functionality, such as service creation, suspension, etc. If you plan to manage services manually, the Universal Module will do, as it integrates with no third-party API.

but in the end, the two request is nice, and 1+ for gateway discount and +1 for gateway fees .

Waaaaaaaaw .. if you add this , you are a rock ... i already requested this .

now the template side, add a jquery request to fetch the numbers and add the response to a div class that has the id count_ticket . <div id="count_ticket">0</div> <?php $this->Javascript->setInline(' $(document).ready(function() { fetchCountTickets(); }); function fetchCountTickets() { $(this).blestaRequest("GET", "' . $this->Html->safe($this->base_uri . "plugin/count_tickets/main") . '", null, function(data) { if (data) $("#count_ticket").html(data); }, null, {dataType:"json"}); } '); ?>

controllers/main.php <?php /** */ class Main extends CountTicketsController { /** * Pre-action */ public function preAction() { parent::preAction(); $this->uses(["CountTickets.CountTicketsModel")); $this->client_id = $this->Session->read("blesta_client_id"); } /** * Portal Newe index */ public function index() { if ($this->isAjax()) { $response = $this->CountTicketsModel ->getCountTickets($this->client_id, "open"); // JSON encode the AJAX response $this->outputAsJson($response); return false; } return false; } }

models/count_tickets_model.php <?php class CountTicketsModel extends AppModel { /** * Constructor */ public function __construct() { parent::__construct(); // You Can Load Language here } /** * Retrieves ticket count * * @return string */ public function getCountTickets( $client_ticket_id, $status_opened ) { $ticket_numbers = $this->Record->select()-> from("support_tickets")-> where('client_id', $client_ticket_id)-> where('status', $status_opened)-> fetch(); return count($ticket_numbers); } }

count_tickets_controller.php <?php class MyTestController extends AppController { public function preAction() { $this->structure->setDefaultView(APPDIR); parent::preAction(); // Override default view directory $this->view->view = "default"; $this->orig_structure_view = $this->structure->view; $this->structure->view = "default"; } } count_tickets_model.php <?php class CountTicketsModel extends AppModel { } Next is coming

@Licensecart relax, take a pen and paper . cup of coffee ... i will teach you in 5 min !!!!!. create the fallowing directory files structure . count_tickets Lــــــــــ count_tickets_controller.php Lــــــــــ count_tickets_model.php Lــــــــــ controllers Lــــــــــ main.php Lــــــــــ models Lــــــــــ count_tickets.php next step is the content of each file .

What are you trying to do exactly Mike? Show like ticket stats on the portal or someplace for public view? I'd like to update the ticket system to show stats in the admin UI, and also have an optional javascript feed to embed on your website.

If you want help in coding it i'm ready ....

No, if i get time i will test it in morre .

The simple way is to create a simple plugin that fetch the request and show the result as json, then in your template just add a blestarequest ajax to fetch the data and show it in DIV . something like the balance credit of client in his profile .

The current beta is almost an alpha given that it's a major release. We're working on beta 2, but I don't know when a final release will be made. The more feedback we get the better, it'll all depends on when we feel v4 is stable enough for a release.

In my opinion, Is possible to sell a open source module if the license allow it to sell and if have heavy and important changes, changes that the community accept pay. But only take a free module, apply only a fix, and charge $100 one time. ....

Tyson, I don't remember 100% - isn't there a feature / core-# that lets us set which email addresses receive auto responses, which don't? Or is that only the ban functionality? if that feature request doesn't exist, can you add it to your list? Some customers have their own helpdesks, and the emails just loop over and over and over. It doesn't look very professional when we can't control our own helpdesk and what it does.

That's not an excuse. If you submit a pull request that does not work, it's your fault. You should test everything you submit, otherwise you make it difficult for someone else.

Is it a fork of the open source DO module? MIT license allows you to modify and sell, if you want, but the community might not be too happy about it. Also, standards are important. You didn't do any testing before submitting a pull request, and we spent a lot of time we weren't planning to resolving issues. "I didn't want to conform to PSR-2 standards, so I forked the module and coded it how I wanted, and offered it for sale" isn't going to instill much confidence in people.

Glad you figured it out! PHP7 can still cause some issues in the v4 beta.

You'd have to ask @Cody that.

minphp v1.0 no longer supports debug mode, which is why you receive no stack trace.

The Support Manager will stop sending auto-responses if it has sent 5 in the last 5 minutes to the same address. If the other system responds less frequently than that, you could still have a loop (e.g. they auto-respond once every 1.5 minutes).

Can you provide a simple before/after example to illustrate your date issue? e.g. Current behavior: Start: 2016-09-30 End: 2017-09-31 What should happen: Start: 2016-09-30 End: 2017-09-30

Is the web server running php 7? If so, the installation will fail. The first change to the database would be to add a new theme to the `themes` table named "FOUR".

It's more setting the structure of the TLDs via HTML to make it easier for you to set CSS styles to obtain your desired look. The only coding necessary is to display the TLDs.

Merged. Thanks for the pull request.

i have sent a pull request to add patch command to the API file .

That ID is another story for the Dates Episodes

Thanks! Looks like this is going to work with the Universal.

or maybe it was gateway fees rather than gateway discount !!!!

+1 I thought there was a feature request for this somewhere but I can't find it.

The Real debugger for blesta has born

I hope you understand where he's coming from. I hope the same thing he does, i'm sure we all do I don't want a faulty billing system, at the same time, there isn't a huge list of bugs. Some of them only need a few lines of code changed, while some others will take more time. I definitely hope it doesn't take more than 1-2 months to get through the final betas. Blesta isn't an operating system edit : I'm hoping Blesta does smaller beta releases, and doesn't try to fix every bug right away. There's this supposed new feature in beta 2, they should try to rush that out, and while people are digging into it, go back and fix all the quick bugs, release the bug fix beta, and so on. It should be a concurrent process. This way, if some people are affected by the small quick fixes, it takes the heat off blesta to quickly fix everything in beta each iteration. Some people might only be affected by the small bugs, so you take care of those, release, fix 1-2 big bugs, release, rinse and repeat

i have write a plugin for debugging , the plugin is designed to use tracy or kint debugging tool (more in next version) . a sample screenshoot when error is detected i will publish it to github when i get time .

Thanks Next week I will initiate the mass update eheh Regards, PV

Hi, Thank you so much for your reply. Everything seems ok. Codes are safe to run I'm going with Blesta as always. Sincerely, Atikul, a blesta lover

Thank you. I will try to do that.