thynan

Allright, thanks for the info!

Allright, thanks for the info!

Hi guys! 
Sorry for the delay. We were waiting for the new domain management of blesta to be finished, so the whole thing was put on ice. However, we now launched our blesta installation without domain management, and are using a workaround with universal module...
 
The module is used by us in production. However it is definitely not finished as a module that works out of the box for everyone. But maybe some of you can use it, or use it with some modifications, or even as a starting point for your own development.
 
I already wrote about the functions a bit a few posts back: http://www.blesta.com/forums/index.php?/topic/1210-ispconfig-module/?p=27826
 
Some Info, if you want to try the module:
In our company, we have a free domain for every customer who orders a hosting package. To replicate this in the blesta module, i added a "domain" field, which the user can fill out during the order. If the customer entered a valid domain, the module automatically creates a DNS-Zone in ISPConfig for the user, using the default dns template configured in ISPConfig. The domain is also shown in the blesta UI, so the customer sees it as "included domain" This is a workaround, because it would be better to manage this with a domain module, but as I mentioned above, we are still waiting for the new domain management before managing domains correctly in blesta.  This "domain functionality" can be rather easily "pulled out" of the module though. Just search for the word domain, and remove what you dont need. (there are some TODO notes reagarding the domain/zone-file functionality in the code - check those out too)
Reseller functions are not implemented at all.
Be aware that this module is a work in progress, and definitely test everything on a testserver before using it. 
I used the cpanel module which was implemented by the blesta devs themselves as a "guideline" for this module. And by "guideline" I mean that I copy pasted vigorously. The reason for that is, that many of the functions (managing Servers, Packages, Services etc) are very similar in all hosting-panel modules, so it made sense to work with the structure that the blesta developers provided in their modules. 
I did not really test the server-groups and the "use first non full server" option that blesta provides. That is one of the parts I copied from the cpanel module... It should work, but don't assume it before you tried.
Generally read the TODO notes in the ispconfig.php file - they may offer some insight..
 
Install instructions:
Install module as usual
Create a remote user in your ispconfig installation (system -> remote users)
You need to add some custom functions to the remoting.inc.php file of ispconfig. This is described in the remoting.inc.php file I included in the module.
Go to blesta -> system -> modules -> ispconfig -> manage -> add server
Server Label: any name
Hostname Master Server: the hostname of your server (or Master-Server if it is a multi-server setup)
Remote user name: the name of the remote user you created in ISPConfig
SOAP Location: Something like 'https://servername.domain.tld:8080/remote/index.php'
SOAP URI: something like 'https://servername.domain.tld:8080/remote/'

 
We usually use gitlab in our company, however for this project I set up a GitHub repo. This is my first GitHub repo - so bear with me.
I didn't create any issues or extensive readme yet - if some of you are interested in continuing development and organizing some collarboration, just let me know.
 
GitHub URL: https://github.com/thynan/blesta-ispconfig

Hi!
No, we don't have any updates yet. The module works for our (rather restricted) use at the moment, so we won't continue developing it until the new "domain management" is released with blesta core. When that happens, we plan to upgrade and extend this module. As far as I know, that will happen with Blesta 4.1 (fingers crossed).

Hi guys! 
Sorry for the delay. We were waiting for the new domain management of blesta to be finished, so the whole thing was put on ice. However, we now launched our blesta installation without domain management, and are using a workaround with universal module...
 
The module is used by us in production. However it is definitely not finished as a module that works out of the box for everyone. But maybe some of you can use it, or use it with some modifications, or even as a starting point for your own development.
 
I already wrote about the functions a bit a few posts back: http://www.blesta.com/forums/index.php?/topic/1210-ispconfig-module/?p=27826
 
Some Info, if you want to try the module:
In our company, we have a free domain for every customer who orders a hosting package. To replicate this in the blesta module, i added a "domain" field, which the user can fill out during the order. If the customer entered a valid domain, the module automatically creates a DNS-Zone in ISPConfig for the user, using the default dns template configured in ISPConfig. The domain is also shown in the blesta UI, so the customer sees it as "included domain" This is a workaround, because it would be better to manage this with a domain module, but as I mentioned above, we are still waiting for the new domain management before managing domains correctly in blesta.  This "domain functionality" can be rather easily "pulled out" of the module though. Just search for the word domain, and remove what you dont need. (there are some TODO notes reagarding the domain/zone-file functionality in the code - check those out too)
Reseller functions are not implemented at all.
Be aware that this module is a work in progress, and definitely test everything on a testserver before using it. 
I used the cpanel module which was implemented by the blesta devs themselves as a "guideline" for this module. And by "guideline" I mean that I copy pasted vigorously. The reason for that is, that many of the functions (managing Servers, Packages, Services etc) are very similar in all hosting-panel modules, so it made sense to work with the structure that the blesta developers provided in their modules. 
I did not really test the server-groups and the "use first non full server" option that blesta provides. That is one of the parts I copied from the cpanel module... It should work, but don't assume it before you tried.
Generally read the TODO notes in the ispconfig.php file - they may offer some insight..
 
Install instructions:
Install module as usual
Create a remote user in your ispconfig installation (system -> remote users)
You need to add some custom functions to the remoting.inc.php file of ispconfig. This is described in the remoting.inc.php file I included in the module.
Go to blesta -> system -> modules -> ispconfig -> manage -> add server
Server Label: any name
Hostname Master Server: the hostname of your server (or Master-Server if it is a multi-server setup)
Remote user name: the name of the remote user you created in ISPConfig
SOAP Location: Something like 'https://servername.domain.tld:8080/remote/index.php'
SOAP URI: something like 'https://servername.domain.tld:8080/remote/'

 
We usually use gitlab in our company, however for this project I set up a GitHub repo. This is my first GitHub repo - so bear with me.
I didn't create any issues or extensive readme yet - if some of you are interested in continuing development and organizing some collarboration, just let me know.
 
GitHub URL: https://github.com/thynan/blesta-ispconfig

Hi Everyone,
 
I've just picked up a copy of Blesta yesterday and though it would be great to make vQmod available for everyone.  I haven't tested in depth at this time but it should be working to be able to conduct code alterations in any of the code, keep in mind that I haven't gone through much of the core code to tell for sure, but at this time I'm basically assuming that most contructs are mostly included/required within the '/lib' area.
 
What is vQmod?
"vQmod™" (aka Virtual Quick Mod) is an override system designed to avoid having to change core files. The concept is quite simple... Instead of making changes to the core files directly, the changes are created as xml search/replace script files. These script files are parsed during page load as each "source" core file is loaded with the "include" or "require" php functions. The source is then patched with the script file changes, and saved to a temp file. That temp file is then substituted for the original during execution. The original source file is never altered. This results in a "virtual" change to the core during execution without any actual modification to the core files.  Learn more at www.vqmod.com
 
What Makes vQmod Useful?
If you have any development experience with just about any platform, when attempting to 'make it your own', or write custom software plug-ins you'll almost always have the desire to make code changes outside of the templating system or what the original developer designed a plug-in system to be capable of.  vQmod allows you to make such code changes and equally distrobute them in extensions you create, and equally keep code alterations separate for easier upgrading / patching of core files in the future.
 
How To Install
Copy the 'vqmod' folder to the root of your blesta installation, ensure that the main index.php has write permission and run www.yourdomain.com/vqmod/install. (adjust run path as needed).
 
 
If anyone has any feedback/questions, please post a reply here and I'll do my best to answer...
vqmod-2.4.1-blesta.zip

A contact needs to have a name, even if it's blank, so I don't see any issue with having a blank name. You just won't see it where it is used and might end up with areas where it may say something like "Hello ,". The system will prevent the entry of a blank name, though, so you would need to work around that.

CORE-818 and CORE-819 address the domain management plugin (These Epics are currently private). We are working out the details internally, and considering everything everyone has had to say regarding domains. It's likely that we will open these tasks up and start a discussion in the near future.
 
These features will be dependent on 4.0 however, which we want to get out relatively quickly. There are a lot of major benefits to developers in 4.0, in part because of the PHP dependency change to PHP 5.4, namespaces, and more. Domain management won't be in 4.0, but we are continuing to make progress in designing the feature, and implementing some other core changes so that it will be easier to implement. (For example, plugins will be able to control package pricing. This allows for the domain plugin to set pricing for domains (Think pricing grid for new/renew/transfer, 1-10 years). It's a powerful feature that could be used by other plugins for a variety of purposes.)

Hi!
 
In the clients "payment selection "view (...client/pay/method/) and the "payment confirmation" view (...client/pay/confirm/) the name of the "Offline Payment" method ist not translated. 
 
Other payment methods are translated correctly - only offline payment is not:
 
example:

 
my language file for the offline payment gateway (offline.php) looks like this:
<?php $lang['Offline.name'] = "Vorauskasse"; $lang['Offline.instructions'] = "Anleitung"; // Errors $lang['Offline.!error.instructions.valid'] = "Sie müssen Anweisungen angeben"; ?> What could be the problem here? 

I also just made a little donation.  You and naja7 are making Blesta work for me.
 
The order process of the OpenSRS modue still has some weird behaviour for me however.  I'll be back tomorrow with more questions - time to go to bed now... Hope you don't get tired of me yet..

I also just made a little donation.  You and naja7 are making Blesta work for me.
 
The order process of the OpenSRS modue still has some weird behaviour for me however.  I'll be back tomorrow with more questions - time to go to bed now... Hope you don't get tired of me yet..

Wow, that is a nice workaround! Thanks again Naja7. I guess it's time for a little donation.
 
One question: what does the "Enable EU Invoicing" setting do exactly? 

Could very well be.
 
But I have been told that tax inspectors exist outside the EU as well.
Not all countries may have exact rules about what needs to be on an invoice, and what administration you must keep, but they generally do appreciate it if the information you do have is accurate, and do require that you have sufficient information for your turnover to be calculated and taxed properly.
Things like back dated invoices, and dynamic address information -that suddenly may show a different state/country than originally, not matching the sales tax charged- are not going to earn you kudos anywhere.

For those that may be interested in doing this, here's the procedure I followed to insert a placeholder into the PDF invoice Terms field:
Duplicate the /components/invoice_templates/default_invoice folder and rename as appropriate (I'll refer to it as new_invoice in this example) Rename all files within this new_invoice folder from default_invoice to new_invoice Open /components/invoice_templates/new_invoice/new_invoice.php and replace all instances of default_invoice to new_invoice and also replace all instances of DefaultInvoice to NewInvoice (note that I had some problems with CamelCase here when I tired using more than Two Uppercase letters here such as BrandNewInvoice, etc.) Open /components/invoice_templates/new_invoice/new_invoice_pdf.php and replace all instances of DefaultInvoice to NewInvoice Open any language definition file file under /components/invoice_templates/new_invoice/language/ and replace all instances of DefaultInvoice to NewInvoice -- also be sure to give the invoice template a new name as assigned by variable $lang['NewInvoice.name'] Open /components/invoice_templates/new_invoice/new_invoice_pdf.php and add the following code to the top of the drawTerms() function: private function drawTerms(){ $cf_data = array(); if( property_exists( $this->invoice->client, "id" ) ){ Loader::loadModels( $this, array( "Clients" ) ); $field_id = 1; $values = $this->Clients->getCustomFieldValues( $this->invoice->client->id ); foreach( $values as $value ){ if( $value->id == $field_id ){ $cf_data = array( 'name' => $value->name . ":", 'space' => null, 'value' => $value->value ); break; } } unset( $values, $value ); } $data = array( array( Language::_("NewInvoice.terms_heading", true ) ), array( str_replace( "{crn}", $cf_data['value'], $this->meta['terms'] ) ) ); ... Some notes about the above code:
Replace the value assigned to $field_id with the appropriate ID number of the Custom Client Field Replace NewInvoice with the CamelCase name of the invoice as appropriate Replace {crn} at the end of the code with the placeholder of your choice (you could potentially use arrays to replace multiple placeholders, if required as well) Go to Settings > Company > Billing/Payment > Invoice Customization > Invoice Template and change as necessary This process can easily be adapted for placeholders in other parts of the invoice too.  Good luck, I hope this helps anyone else that wants to achieve something similar.

Feature request: It would also be awesome if Blesta showed the math that's going on in the Order Summary. Example:
 
12 x $3.99
Subtotal: $47.88
 
To recap, there should be a line above subtotal that shows the unit price as $3.99 (or whatever the monthly price is) and multiplies it by the length of the term.
 
The reason is that we offer our clients a discount for paying every 6 or 12 months and we want to clearly convey this information. The way it is right now lacks clarity.

a lot of us want to translate blesta to thier native language , but this are a obstacle , big obstacle , is the translator website , is not easy to manage translation and to correct some old translation .
the worth is in blesta upgrade , how you can know wich file has been added to it some new lang ?
so i have this issue for long time , and i have resolved with my own way , today i have dedcied to share the translator plugin with the community , my translator motor , check the native language 'en_us' with the existing languages , with this plugin you can know :
wich file are missing from your language directory .
wich phrases are missing from your language file .
translated the files within your blesta system , save it .
off course drink coffe with you playing with the translation . before i upload it , what you need tose in this translator plugin .
screenshot
http://host-image.net/v.php?id=69170admin_languages.png
waiting your's idea .

Hi, sorry for the late answer, I wasn't working on Blesta for a while..
 
At the moment there is no Git Hub location for the project. However, after checking back with my CEO we decided to make the module public. I will create a Git Hub project and check back here when i'm done. I will have to do some cleanup / documentation first, because atm it's still a bit too messy.  
 
It may take me a few days to get to it however, since I'm a bit swamped with work currently.

I have a little update: I am implementing an ISPConfig Module myself now. It is still a work under progress right now though, and there are some limitations.
 
What is implemented already
- Adding and connecting to ISPConfig servers (singleserver and multiserver)
- Create packages, and automatically getting the available client templates from the selected ISPConfig Server. If multiserver, you can also select the web, db, mail and ns server (also automatically fetched from the ISPConfig multiserver-master, and available in a dropdown). 
- Create services in blesta,(by admin, or by order) -> Client is created in ISPConfig with the selected client template from the package. Possible auto generation of username, password and client contact name. (if "use Module is checked - else service is only created in Blesta)
- Delete services in blesta -> Client is deleted in ISPConfig (if "use Module is checked)
- If you already have clients in ISPConfig, and want to add them to Blesta, you can add a service in Blesta, and don't check the "use module" checkbox. You can then manually enter a the clientID of the existing ISPConfig client. Then the Blesta service and the ISPConfig client are connected through the clientID.
- You can suspend and unsuspend a service, which locks/disables the client in ISPConfig. However, this is a new function in ISPConfig, and the remote API function for locking/disabling clients is not working correctly yet. So this will only really work as soon as the ISPConfig team fixes this function.
 
What is not implemented, but should be i guess...
- Reselling is not implemented at all. We don't need that, so I just ignored the reselling options of ISPConfig and Blesta
 
The error-handling is also very lacking atm, and the source code is lacking documentation. But like I said - work in progress.
 
Below is a little screenshot of package creation for a multiserver.

Hello,
 
@richwalker and @cleverhost; Any donation is apretiated, no amount minimum required
 
Im reciving again by PM, emails and this forum alot of requests to continue developping the OPENsrs module, so I will try to start update next week to add aditional features
 
Regards,
PV

Hello Blestars
 
Im back again (so many work in this last 3 months that I didnt have time to update and talk to you guys )
 
Cool 3.4 Now!
 
Its to bad that is still not included the new "Domain Managment"  
 
I have build a temporary solution, but dont have time to update all registrar modules to implement, also has to mess with one ore 2 core files, and I hate that
 
So, ++++++1 for Domain Managment on next release
 
I Think its a major priority the Domain Managment, higher than any outher extra like Mass Mail, Affiliate etc..
 
How can we sell Domains correctly, and manage them in full with "Mass Mail Plugin" or "Affiliate Plugin" ?
 
Just my 2 cents:P
 
Keepup the good work Paul/Tyson/Cody

Nice! Looking forward to testing it. +1 for the Domain Manager btw.

Nice! Looking forward to testing it. +1 for the Domain Manager btw.

Nice! Looking forward to testing it. +1 for the Domain Manager btw.

Nice! Looking forward to testing it. +1 for the Domain Manager btw.

Oh damn, I just completely overlooked the system tab - my bad. Thanks!