Jono

I'm sorry, I still don't understand why the prefix is necessary. The client controllers can extend ClientController and have a name like client_main regardless of whether they are accessed with the client prefix. Fair question. I'm not sure we do need a Public and Client URI, perhaps we should consider removing them. Obviously we still would keep client vs public navigation though as we wouldn't display the same nav items to each.

I see now, the client ticket list page does this: $('#client_tickets a[rel]').blestaModalConfirm({ base_url: '<?php echo (isset($this->client_uri) ? $this->Html->safe($this->client_uri) : null);?>', submit: true, confirm_data: {id: $('input[name=\"id\"]', $(this)).val()} }); Instead of making you do the same, I will create a task to add a dialog.php controller so the /dialog will be a valid path instead of requiring /client/dialog. Is this sufficient to resolve the issue?

Have you debugged why this is the case? The support manager plugins use widgets with ticket lists and a close modal and all works fine with or without the client/ prefix.

Does this happen on a valid service? Or is it a fake test service?

Thanks for the report: https://dev.blesta.com/browse/CORE-4350. This will be resolved in the final release of 5.1

I'll try to think about this more today ?

Haha, no. The goal is ~2 month between beta releases. 5.1 took ~6 months because we had a lot in there (primarily the Domain Manager).

Love it, thanks for the input Can't guarantee it for 5.1 but I'll look at getting it in 5.2 or 5.3. https://dev.blesta.com/browse/CORE-4342

but in reality some plugin links need to be inside the client_uri not public_uri . Can you give an example?

This will be fixed in beta2

Good catch. Currently the behavior is to link all plugin links through the public_uri instead of the client_uri. This was to make the URLs a little cleaner. I believe the hover tooltip should be updated to remove the client/ portion for plugin links

Thanks for the report. I created CORE-4336 to deal with this. It appears the column had the wrong data type assigned.

You are saying you would like more function similar to getExpirationDate() which are standardized across registrars? I'd be interested in this. Any other suggestions besides the methods you mentioned?

To resolve, download the latest version of TheSSLStore https://github.com/blesta/module-thesslstore/tree/1.10.0 or NameSilo https://github.com/blesta/module-namesilo/tree/1.14.0

Added. Cheers

There is likely an erroneous call to Language::_() in your module. Argument 1 take a language key (e.g. 'AdminClients.add.name'), Argument 2 is boolean true to return the language and store it in a variable or false to output it to the webpage, argument 3+ are values submitted to sprintf (e.g. language is 'My name is %1$s' and the call is Language::_('AdminMain.myinfo.myname', true, $name)). Likely you've accidentally submitted an object in argument 3+

The transaction was made in GBP, but the USD credit is being displayed. It should appear if you look at the GBP credit

https://dev.blesta.com/browse/CORE-4168 will resolve this

Anything in the Blesta error log files?

You can set a logo url on the theme. When you change to a theme Blesta uses whatever logo is assigned to the theme (or the default if there is none).

I'd have to look more to see why removing breaks it. But for now you could add the 'hidden' class to the div containing them.

Nice! Looks great! Thanks for developing on Blesta, this is how we'll grow A couple notes. It looks like the Power Cycle button on the Rescue Mode could use a margin above it (or below the message). The Reinstall Os tab content doesn't appear to be taking the full width of the screen.

Yes and no. You are looking for the "clients_format" setting which is set to {num} by default. You would run a query something like UPDATE `company_settings` SET `value` = 'some-prefix-{num}' WHERE `key` = 'clients_format'; This will do ALMOST what you want, however the prefix is not dynamic. So instead of having IDs like 0001, 0010, and 0100. It would have to be 0001, 00010, and 000100. A couple things to note. First, this is only for the display ID, obviously not the internal ID. Second, when searching for a client you can use partial IDs. So a search for 0100 would match 0100 and 000100.

This is a known bug in v5.0.0 and v5.0.1 (https://dev.blesta.com/browse/CORE-4137). Please upgrade to 5.0.2 to have the issue resolved.

Looks like this is only a bug for the X Rates integration which is returning a response with an exchange rate of 0. I've created a task to resolve that here: https://dev.blesta.com/browse/CORE-4145. In the mean time any off the other processors should work.