interfasys

[CORE-315] - DirectAdmin: Number of accounts on server does not change Still the case on b2

How do we import dozens or even hundreds of domains from a registrar? Per example, on Logicboxes, I can see all the domains assigned to various clients, but I'd like to get the same view inside Blesta.

Did that and got a new error importPackages: Undefined index: email on line 914 EDIT: That was because I had error reporting on. Now I have this which prevents the script from completing the task ( [email] => Array ( [format] => Please enter a valid email address. ) ) EDIT 2: Only 1 domain got imported as a service Transactions are not linked to invoices Directadmin module shows 0 accounts linked to the server

I think you've got it right. I assumed it was a form refresh problem because I always selected the same (empty) group when doing my tests.

OK, I've just done some tests. It was only happening if the server group was specified (as apposed to selecting "Any") and the reason was that the group was empty . There is still a bug though, because I was selecting a group without any servers in it and it was populating all the fields for me, giving me the impression that everything was properly configured. It's only when reloading the form that the dropdowns would end up being empty.

I'll get back to you with the requested info, but there is no problem with the API calls since everything gets properly populated when I select Directadmin from the list of modules. Things break when the form gets reloaded because of a form error, that's all.

So I gave it a go with 3.1-b2 importing 5.2.15 and it failed with importPackages: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'term' in 'field list' on line 124 I've checked and "pricings" has a "term" column in Blesta, so not sure why this fails...

This is a follow up to this bug http://www.blesta.com/forums/index.php?/topic/1584-directadmin-module-options-fields-can-be-reset-when-creating-a-package/#entry12461 I've just followed the steps described in the original report and experienced the exact same problem with 3.1-b2. Here are the steps again Create new package Select Directadmin module Select a server group Fill in the rest of the form Type "mucho" in Term, under pricing Hit "Create package" For step 5, it can be anything. The purpose is to get Blesta to reject the package because of missing information. The error message for step 5 as descrivbed above will be Expected result Despite the error, no information should be lost. The form should look the same as it was filled before the "Create Package" button was clicked Result The "Directadmin Package" dropdown, in Module Options, is empty and the user has to select another module and then go back to selecting the DA module again in order to try and create the package again.

On the custom fields page, in the admin area, you'll see the translation key instead of the translated text Steps Go to admin/settings/company/customfields/ Create a field, using a translation key for the name Tick the "Name is a language definition" box Add translation to _custom.php Save field At this stage, you'll see your translation key being displayed as the name of the custom field. There are no errors being logged or displayed. The method works fine for other translatable fields in the admin panel, so this is probably a problem with the code of this page only.

Got it, thx. For reference since there is nothing in the doc Packages Domains package -> Domain group Hosting package -> Hosting group Order forms Hosting plans form Type -> Domain and Other Domain Package Group -> Domain group Package Groups -> Hosting group

I want all our domains to be available on the first step offered when ordering, so I've added all domain packages to the standard hosting group. So far, so good. Customer picks a domain, configures it and reaches the hosting package selection page. He's presented with the few hosting plans and the 20 domain packages required to offer the domain selection on the first step. Surely this is a configuration problem and I'm missing something. If I don't assign the domain packages to the hosting group, then domains don't show up on the first page.

I've just noticed a bug related to the translation feature. On the custom fields page, the key is being displayed instead of the translated string for the name of the field. Works fine in contact and payment types.

I like the idea since it would remove the need to have a separate app. One thing I've noticed on the phone screenshot is how blurry the logo gets, which reminded me that it would be a good idea to have logo variations using different DPIs. Kind of like how android categorises its app icons. Would also be very useful for invoices. One company logo for the web invoice, one for the printable PDF.

Got it, thx. Those strings were missing from the French file.

OK, I've checked that page, but can't find how to identify which key to use. $lang['AdminSettings.company.general.contacttypes.1.name'] ?

I didn't read the "Use Language Definition" tooltip and it seems we have to mess with language files in order for the label to show up, but I have no idea what the key should look like in the language file. And I'm not sure why it's blank in the admin area since the default language is English. The steps are as simple as listed above, but I did forget to mention that I ticked the box. The environment is PHP 5.4. MariaDB 5.5 on FreeBSD 9.2. Using Blesta 3.1b2

It's not the first time I've seen this sort of bugs, but I can't recall where... In admin/settings/company/general/contacttypes/ Create a contact type and hit save. The message from the system is: Note the blank field. I think it has to do with the fact that our setup uses 2 languages, because if I edit the contact, then I see the name, so the data is not lost.

I see B2 in the download zone

Thank you. I've just sent the email.

Thank you very much Cody. Unfortunately, in order to get the files, you do need a license, so I'm left with waiting for your HostBill migrator or getting a monthly license of WHMCS. I suspect I'll go with the latter if I want to get something done in Q1.

Yeah, I'll try that on b1 if you don't release b2 by the end of the week and will report back in the beta forum.

Thank you both. I think I'll wait for b2. Does the WHMCS importer work with V4 data?

Is there an upgrade path from b1 to b2,.....rc,... gold release? Since 3.1 is the first version with an importer from competing solutions, I was thinking of starting with that and launching on 3.1 final.

Thank you

Is this the same module which is available in 3.1 beta?