Leaderboard

so it attempt to send all the emails in the one shoot .... i really prefer if a setting that we edit to set how many email is sent via every job , like 50 email per job , so we will send 600 email per hour . this is can be limited to the emails fetched from the request in cronjob . from my case, more than 5000 contacts i can't email or try to do it in one shoot . also google, msn, yahoo, they have filter to block ip that use abusive send .

Basically, Show all the TLD prices in a table in the order form.

when i get time i will rewrite my used API for my module that i have used to integrate your system with my licensing digital product . but i can't promise in the near future as i have to rewrite some other module/plugins than need to be ready when v4 is out .

you can use my admin tools plugins , is open source, in github , it has this feature .you and any other on,e can review the code and sent a pull request or report any bug in iy .

The GitHub repository deliberately doesn't have a vendor/ directory, so that it can be used with Composer to install the module, and this allows the package to be listed on Packagist. If you want a "pre-packaged" version with a vendor directory already setup, you can download via the marketplace or through enverido itself. The reason I ended up doubling up the try/catch statements was that i was finding that adding the if(...) statement underneath each command didn't always trigger the Blesta view with an error, even if the setErrors(..) command had just been executed, and instead the code ended up throwing an exception where certain variables were "null". That's why the try/catches sometimes appear in both files (this and to allow a central "point" to log the API requests, rather than to manually log the request every place it's made in the module. I'll definitely look into refactoring it in the near-future, but it's a working solution so it's not a top priority right now. Feel free to make a pull request, but by no means feel obligated to - I agree that a cleaner method is certainly a possibility, and I'm going to look into reimplementing the API in the Blesta module, using the PHP library.

What software are you used to make the flow chart?

Domain manager coming soon with new order system.

the github doesn't have the vendor directory , so who will just download and install will not work for them . as i see you have add a try catch to all calls in the api file, and the same in the module file , i se this is like a double work . in my opinion , is better to let the api file check the response if valid or error, then log it and return the error input if error occur , in the module just make the call and under every command add if ($this->Input->errors()) return; that will easier and easy for tracking , and simple logic to go with it .

Are the support department SMTP details still correct? It sounds like since you changed DNS that the server can no longer communicate to fetch tickets, or has otherwise caused another error. You can disable the "Download Tickets" automation task so that it is not run by cron automatically. Update your configuration file to enable error reporting. Then wait a little while (5 to 10 minutes) and try to run the cron manually from Settings > System > Automation. Are there any errors displayed? If so, what are they?

i will add my own soon , now is time to re-make all plugins for v4

I think it is unique