flangefrog

Not sure what country you're in but I find local domains cost 3 - 4 times as much at most international registrars. You may want to check the latency to the registrar's API, my latency for US registrars is > 300ms and so Blesta doesn't feel very snappy. It's not a big deal though so you can just go with the one that has the best range and prices.

Even if you put it in the Blesta .htaccess it is still going to be running the regex on the full url so ^/admin won't work as ^ denotes the start of the string. Yes it is, however my priorities have changed so you won't see it within the next few months. I also haven't had a good look at how Blesta handles merchant gateways that only store a token instead of the actual card details. It may not be possible yet without core changes.

Is your url something like yourdomain.com/blesta/admin? If so you would need to change ^/admin to ^/blesta/admin

AND is correct, I just mentioned that in case you wanted to use any other conditions. The IP range looks alright to me

Yes, by default Apache will add an AND between each condition. You can add [OR] at the end of the condition if you want OR instead. This is regex so you could also add an IP range or whatever you want.

Try something like the below in your main .htaccess file. RewriteCond %{REQUEST_URI} ^/admin RewriteCond %{REMOTE_ADDR} !^127\.0\.0\.1 RewriteRule .* - [F]

Yes, that's correct. not sure what I was thinking there. Try using a combination of vQmod for adding the img-responsive class and use the CSS & JavaScript toolbox for the CSS.

What's the use of this? Why would you not want a record of credit that has been added?

Oh right, I completly forgot about that method. I've just got the validation data in Module::addService

If they are test charges then you can manually remove them from the database.

Do you mean a transaction? You can un-apply a transaction under Billing > Transactions > Edit > Unapply

The Module::arrayToModuleFields() method uses the attribute array to set the HTML attributes directly, so for a tooltip you would need to set the HTML title attribute http://www.w3.org/html/wg/drafts/html/master/dom.html#the-title-attribute

Works for me as title...

You can show a tooltip or placeholder. 'OtherEntityType' => array( 'label' => Language::_("OtherEntityType", true), 'type' => 'text', 'attributes' => array( 'title' => "Tooltip", 'placeholder' => "Placeholder" ) )

I tried this myself and the domain was also registered. I then looked up the API docs and found this: It seems the only purpose of the test URL is that it enables you to use a GET request for all your requests - even those that would usually require a POST request. This serves no purpose in Blesta so it should probably be removed from the module.

Doesn't look like this domain is registered. If this is not the actual domain you registered and you have confirmed the other domain really has been registered then it's almost definitely an issue with Logicboxes not Blesta as it is submitting to the correct sandbox URL.

Can you post the relevant module logs here? Obviously redacting any authentication data.

Here is my module for Web Drive. I've been using this for several months but just recently rebuilt parts of it to work around some Web Drive quirks. Unfortunately I can't really recommend using Web Drive with Blesta until they make some big changes to their API and reseller system. Presently there are lots of bugs and missing features in their system. This might help if you are already using Web Drive though. Domains, contacts etc will need to be moved to a subaccount for each client in with the username set as the client's ID i.e. 1500. The module is only built to work with New Zealand domains. Web Drive use a reseller (OpenSRS) for their gTLD domains and have some bugs with gTLD contacts so it is better to use a module that directly interfaces with a top level reseller for gTLDs. The module does have some features not present in other registrar modules including input validation and pre-filling WHOIS data but allowing changes to be made. It also allows you to select Add, Transfer or Register when adding a service via the admin panel. There are still some things to do (look in code for TODO) but I may not do any more work on this module as I will be switching to another registrar. module_webdrive_1.0.0.zip

I don't think there is supposed to be a template there by default.

Naja7host's plugin allows you to add CSS, JavaScript and PHP to any page, vQmod allows you to edit any file included by PHP which usually means PHP and PDT files. Both allow you to make changes without actually editing core files, so the changes are persistent across versions. For this particular change I think vQmod is better suited for the job as it will disable the Tax ID field rather than just hide it, but it's not very important and you can use either. You can look inside the vQmod XML file to find which files need to be changed with Naja7host's plugin.

I'll add some JavaScript later but it won't stop someone who knows what they're doing from inputting invalid data.

Yeah it's possible to encrypt it, passwords should never be there in the first place though. There are built in ways in MySQL to compress the data, that might be a good idea although depending which method is used it could prevent full text search.

You will be editing the wrong file. There are at four different files you need to change including the client edit page, registration page and signup pages for all three templates. See the vQmod in my signature.

It doesn't look like all those tags are available on the service creation template. On my installation it says these are the only available tags: {contact.first_name} {contact.last_name} {package.email_html} {package.email_text}. You probably want to use the package email template (welcome email) which can be found by editing the package.

You will need to make these changes in the following files. * is a wildcard. plugins/order/views/templates/*/signup.pdt, plugins/order/views/templates/standard/types/registration/signup.pdt After $this->Form->fieldHidden("action", "signup"); Add $this->Form->fieldHidden("username_type", "email"); And remove the following code: <div class="radio"> <label> <?php $this->Form->fieldRadio("username_type", "email", ($this->Html->ifSet($vars->username_type, "email") == "email"), array("id"=>"username_type_email")); $this->_("Signup.index.field_username_type_email"); ?> </label> </div> <div class="radio"> <label> <?php $this->Form->fieldRadio("username_type", "username", ($this->Html->ifSet($vars->username_type) == "username"), array("id"=>"username_type_username")); $this->_("Signup.index.field_username_type_username"); ?> </label> </div> <div class="form-group username"> <?php $this->Form->label($this->_("Signup.index.field_username", true), "signup_username"); $this->Form->fieldText("username", $this->Html->ifSet($vars->username), array("id"=>"signup_username", 'class' => "form-control", 'placeholder' => $this->_("Signup.index.field_username", true))); ?> </div> This won't completely prevent someone from using a custom username, to do that you could use the attached vQmod.username_type_email.xml