Blesta Addons

Tienes que descargar los archivos de blesta , y hacer los ajustes que quieres, después sube los ficheros por FTP .

is ok, for both is working , maybe is not the best solution , but is working : ) search if (!empty($post)) { $api->loadCommand("logicboxes_contacts"); $contacts = new LogicboxesContacts($api); foreach ($sections as $section) { $contact = array(); foreach ($post as $key => $value) { if (strpos($key, $section . "_") !== false && $value != "") $contact[str_replace($section . "_", "", $key)] = $value; } $response = $contacts->modify($contact); $this->processResponse($api, $response); if ($this->Input->errors()) break; } $vars = (object)$post; } change by if (!empty($post)) { $domain_info = $domains->details(['order-id' => $fields->{'order-id'}, 'options' => "OrderDetails"])->response(); $tld = $this->getTld($fields->{'domain-name'}, true); $contact_type = $this->getContactType($tld); foreach ($sections as $section) { $contact = []; foreach ($post as $key => $value) { if (strpos($key, $section . "_") !== false && $value != "") { $contact[str_replace($section . "_", "", $key)] = $value; } if (empty($contact["company"])) { $contact["company"] = "Not Applicable"; } if (empty($contact["zipcode"])) { $contact[$key] = "00000"; } $contact["customer-id"] = $domain_info->customerid; $contact["type"] = $contact_type ; } $contact_id = $this->createContact($package->module_row, $contact); $new_contact[$section] = $contact_id; } $customer_id = $this->getCustomerId($package->module_row, $client->email); $data = [ 'order-id' => $fields->{'order-id'}, 'reg-contact-id' => $new_contact["registrantcontact"], 'admin-contact-id' => $new_contact["admincontact"], 'tech-contact-id' => $new_contact["techcontact"], 'billing-contact-id' => $new_contact["billingcontact"] ]; // Request for Opt-Out of 60 day lock that is applied post Registrant Change $data['sixty-day-lock-optout'] = false; // Handle special assignment case for .AU $attr = []; $attr['skipIRTP'] = true; // Skip IRTP Process $data = array_merge($data, $this->createMap($attr)); $response = $domains->modifyContact($data); $this->processResponse($api, $response); $vars = (object)$post; }

Without the debugger no error is shown . the question why the the debugger (Tracy) catch this error !!

we have a fix for logicboxes module now .

But normally if the link was visited and password was change it should be removed and has no effect , thought no ?

only service with active status will be processed in the module .

some module will not support update contacts and whois information , and maybe also the transfert also . i have tested with logicbox module, and updating the whois is not working .

i use php 5.6, and only with the debugger plugin . after a small look i think the debugger has the right to show a error . the page title in edit invoice need two argument ($client->id_code, $invoice->id_code) . in the preAction the language set is only for 1 params , the the page title is overrided in line 4064. so i have made a simple correction , from $language = Language::_( 'AdminClients.' . Loader::fromCamelCase($this->action ? $this->action : 'index') . '.page_title', true, $client->id_code ); To $language = Language::_( 'AdminClients.' . Loader::fromCamelCase($this->action ? $this->action : 'index') . '.page_title', true, $client->id_code, null );

is the debugger plugin .... but i don't know why he is returning a fatal error when debugging is set to true ?

i never touch any core files, any way i will upload all the files of beta4 to test it .

i have re-run the upgrade again and it was fixed now .

we have in one installation that has 3.6.2 the billing widget is not showing for a while, today i have make a depth look and i find the error SQLSTATE[42S22]: Column not found: 1054 Unknown column &#039;transaction_types.type& #039; in &#039;on clause&#039; on line <strong>124</strong> in <strong>/home/xxxxx/public_html /lib/model.php</strong> this is related to uncomplete upgrade ? or something else ?

Thanks . What about the old services ? That is the work of the developer . maybe that should be exist . better than nothing . if the fact i'm talking from experiences and some concrete case , some people will been moved from * to blesta, and blesta will not have some module at the moment, they will have their package associated with universal module, then they need a blesta module after they got it, they can't use it !!! you think this client will change 1000 or less/more services manually ?!!!! the best option they have is to back again to the old software, for that reason i told is (-1) for blesta . new client that will begin from scratch they ill have not any issue. Finally, that has 0 importance for me, i advice only the team about what happen behind the scene.

i will add this to the next version of clean unpaid orders plugins .

Debate is a proofs and convincing others . not attack others with Dirty words . Next time please take care of your words , we are here to exchange ideas, not listen to a Obscene words . Next Time Respect The OTHER Please even if he has a wrong idea . this subject is not new , we have already talked about it here . Taking your example , let imagine the client take the decision to move from interwork to cPanel , or the reverse action , in that case he should do 2 solution : 1 - cancel all the existing service for the client and create another new one, and if he has 200 account , make the calculation how much time he need . 2 - change the package's module, and make a database query to convert the services fields to the new fields, of the course the value will be impact . what do you prefer if you was in this case ? My second argument, we are not inventing the wheel, as this feature already exist in others billing software.

i'm not talking about my self , as i didn't have any problem to do the task in my installation, but i'm talking about a general idea that was option and now is disappeared . is a (-1) for blesta , specially for users who are migrating from other billing software , after migration they found a lot of packages related to universal module, then when they create their own module , they will be stacked with this behavior, for me is a more money as is a separated task , but for blesta is less converting from trials to active license . Finally, from a technical view i can't see a separation between packages and services !!!!

But you can change the package module ? is the admin not the user , so if the admin KNOW and is responsible for the action he take , i think no problem . the debate here is not only preventing changing module, but preventing migrate a big data of services to a new package . if i change the module package and i break the services is my responsibility, and not a blesta fault, the problem for is that i can't change it if i know what I'm doing . at least make a option to enable/disable this in company setting. just to note not all the users will change the package module, let say i have a package related to module X , i have worked with it in several month, i have created a new module Y that has the same module metas and the same package metas , i can change all my services in one click shoot if the option is available, but if not , i need to cancel/recreate hundred of services !!! is totally crazy.

already talked ... check a previous thread i have posted from the first v4 beta 1. really a catastrophic strategy to prevent change module in packages .

Normally this is should be care by blesta itself , as the error is shown in the admin client's profile . so if the $invoice->id_code is missing is a blesta bug not mine .

Tax Support is coming ... probably we will do a pro version that has some more feature than the normal version .

every one has it own method of working . in my work , i try the most as i can to not touch any core files .

Send me a PM . we can do it .

almost all of my public and custom plugins/modules are working in v4 without any issues . we want to use namespacing and new buttons in admin area to be fully designed like v4 are now .

Copy the default folder to any name you want, then change all the classes é files that has default with your new name .

The second fix is a bit complicated ... and need a core file changes ...