Jono
-
Posts
376 -
Joined
-
Last visited
-
Days Won
37
Posts posted by Jono
-
-
Just want to update this to note the 4.11 has been released and the affiliate system is live
-
Hmmm, did you happen to delete the invoice associated with this order?
-
Hey, thanks for the report! I've created https://dev.blesta.com/browse/CORE-3802 to handle it.
-
Thanks for the report! Strange thing to get missed in beta. I've created a task for it https://dev.blesta.com/browse/CORE-3800.
-
I'm able to complete the action on my system with no issue. Can you describe the bug? Did you receive any error messages? Did you experience unexpected functionality?
-
Are you referring to the "Payment Recieved" emails? Or perhaps the "Payment Approved" emails?
-
I know it sounds cliche, and you already said they were correct, but I'd suggest double checking the credentials again. The response you are seeing is the exact same one I see when my credentials are incorrect. Make sure you double check the port and whether it is using ssl or not. If you're absolutely sure they are correct then perhaps there is a firewall that is blocking the Blesta requests?
-
Hey there, good idea, thanks for the feedback
It sounds like https://dev.blesta.com/browse/CORE-2222 may be similar to what you're describing? In the meantime, if you are struggling with a cluttered client list, Blesta 4.10 introduces widget filters. In the top right of the client list widget there is a button that opens a filtering form. Here you can search by name, country, client group, etc.
-
I get the client_uri changes, but is there some reason behind changing the others from order/ to plugin/order/?
-
Which module is this for?
-
Which module are you using? Namesilo pulls in a list from the registrar. Namecheap has a list defined under components/modules/namecheap/config/namecheap.php
-
A bug was introduced in 4.9.0 that causes the autodebit cron job to ignore the autodebit setting on an individual client in favor of the client group or company setting. This only occurs when the client setting is false and one of the others is true. This issue can be resolved by modifying app/models/invoices.php Invoices::getClientSettingSubquery() and replacing:
$this->Record->select() ->from([ '((' . $sql1 . ') UNION (' . $sql2 . ') UNION (' . $sql3 . ') UNION (' . $sql4 . '))' => 'temp' ]);
With
$this->Record->select() ->from([ '((' . $sql1 . ') UNION (' . $sql2 . ') UNION (' . $sql3 . ') UNION (' . $sql4 . '))' => 'temp' ]) ->group('temp.client_id');
-
-
Must be running an old version, this was fixed back at the end of 2018. You can add this just before the trouble line:
if(!is_array($response->portfolios->name)) $response->portfolios->name = [$response->portfolios->name];
-
Well it requires some code tweaks or a custom plugin. You can upload the files to the app/views/client/default/javascript or app/views/admin/default/javascript dir and then add a reference in the appropriate structure.pdt file.
-
More clarity is needed. Are you saying you want upload new custom css and js files? "header footer file" are you referring to structure.pdt? " then blesta ask for upgrade?" ... ummm, no? Blesta never asks you to upgrade, though when you update your Blesta version you do visit yourblestaurl.com/admin/upgrade. Unless you are talking about upgrading a plugin. In that case you would need to update the version in order to add new actions or event tie-in.
Honestly I'm not sure what you're asking, but hopefully that was helpful X)
-
Short answer: Use $this->partial('client_main_myinfo', $vars, APPDIR);
Longer answer:
The portion in the example code:
// Override default view directory
$this->view->view = "default";
$this->structure->view = "default";That is what I'm speaking of.
Unfortunately there isn't really any documentation on these classes other than the code itself. $this->partial() is a method defined here https://github.com/phillipsdata/minphp-bridge/blob/master/src/Lib/Controller.php, or in the blesta code at vendors/minphp/bridge/src/Controller.php. That is also where $this->structure and $this->view are set. Both of those properties instantiate the View class https://github.com/phillipsdata/minphp-bridge/blob/master/src/Lib/View.php or in the blesta code at vendors/minphp/bridge/src/View.php.
The reason other plugins don't encounter this error is because they don't try to access view files from the app directory, only from their own view directory.
-
The error seems to indicate that you called $this->partial('client_main_myinfo', ...). So it is expected that it is looking for client_main_myinfo.pdt. You are asking why it looks in the plugin dir instead of the default app dir? Well likely your plugin has modified the view path in order to fetch your client_main.pdt file. That being said, $this->partial() has a 3rd parameter for the directory to search in which you can you to override the view path. You might try using APPDIR for that parameter
-
Those fields define where to send the data from each action. The "Response Contains" field defines what the the endpoint must respond with to indicate success for that action. See https://docs.blesta.com/display/user/Universal+Module#UniversalModule-Notifications
-
The other option here is to make a custom edit to your Blesta installation. Something like ServiceChanges::getLineItems() that makes the line items, similar to the controller method AdminClients::makeLineItems()?
This seems to be a total pain so I'm thinking about how we can make this work better for API user in the future.
-
The display of order forms is controlled simply by their ID. There isn't any great way to change this right now. Here are the options, inconvenient as they are:
- Manually update the database to change the ID of the order_forms table and the associated records
- Recreate the order forms through the interface in the order you want them to be displayed
-
I believe that is not possible through the interface
-
-
I can mess with that, but it still won't make the class functions callable through node.
Upgrading/Downgrading a service via API
in General
Posted
Unfortunately not. Our current priority is on the affiliate system (released in 4.11) and the domain manager (TBD) so some of the dev stuff is taking a bit of a back seat for now though I'd like to make a lot of dev improvements soon.