flangefrog

I think that just as you redirect the client to a login url (or make a get request), you would do the same but use the logout url.

It doesn't look like this method is designed to be called via the API. You would need to instantiate a Session object and select the users session using their session ID, which will be stored in a cookie on the users computer. You could search through the session data on the DB for the client id but it would be messy.

VestaCP released a new feature voting system and the Blesta module lost all it's votes from the old bugtracker. You all might want to vote on the feature. New link is here: https://bugs.vestacp.com/responses/support-for-blesta-billing I'm not going to be using VestaCP, but I think it would be good for Blesta to be integrated with it.

From your other thread: The CSS files should let you override the background, in fact you should be able to override any other CSS on the page. If you are having trouble you may want to read this: http://css-tricks.com/specifics-on-css-specificity/ I haven't looked in depth into what you are doing in your above post but I think you're completely bypassing structure.pdt right? If you want to change the HTML in structure.pdt based on the order form template without completely bypassing it you can use similar code as above: <?php if (isset($order_form) && $order_form->template_style == "my_custom_style") { ?> <p>My custom HTML</p> <?php } ?> You might also want to check $order_form->template

It looks like the correct way to do this is to edit the plugins/order/views/templates/*/config.json and add a new template style. { "version": "1.1.0", "name": "AJAX Template Pack", "description": "AJAX order form template pack for the Order plugin.", "authors": [ { "name": "Phillips Data, Inc.", "url": "http://www.blesta.com" } ], "styles": { "slider": { "name": "AJAX Slider", "thumbnail": "images/thumb_slider.png", "screenshot": "images/full_slider.png" }, "boxes": { "name": "AJAX Boxes", "thumbnail": "images/thumb_boxes.png", "screenshot": "images/full_boxes.png" }, "my_custom_style": { "name": "My Custom Style", "thumbnail": "images/thumb_custom.png", "screenshot": "images/full_custom.png" } } } Then inside the .pdt files you can use <?php if ($order_form->template_style == "my_custom_style") { ?> <p>My custom HTML</p> <?php } ?> Here's the change you made as a vQmod. It's really easy to learn, best time to start is now custom_order_view.xml

Is your root web directory set correctly and is it an absolute URL? Is the order plugin upgraded under settings > plugins? Does the file /plugins/order/order_controller.php exist?

Clients can upgrade and downgrade services in the next version (now in beta) which is probably what you want. You would need to write a plugin if you want their roles to be changed automatically within OxWall. Blesta can do the other things you mentioned.

I meant it would set the $term to null, but wouldn't throw the custom term_error. Probably fine with most APIs but I had to use the custom error with the Web Drive module as their API is the most frustrating API I have ever worked with and won't even return a failure/success status for lots of methods.

That won't error on a 9 monthly term though, so how about this: foreach ($package->pricing as $pricing) { if ($pricing->id == $vars['pricing_id']) { if ($pricing->period == "month" && $pricing->term % 12) { $term = $pricing->term / 12; } elseif ($pricing->period == "year") { $term = $pricing->term; } else { $this->Input->setErrors($this->getCommonError("term_error")); return; } break; } } Or you could remove the setErrors() and let the API functions handle that as long as they give a descriptive error.

Well yes, the solution I currently use for my Web Drive module is below. Note that this registry supports monthly renewals. foreach ($package->pricing as $pricing) { if ($pricing->id == $vars['pricing_id']) { switch ($pricing->period) { case "month": $term = $pricing->term; break; case "year": $term = $pricing->term * 12; break; default: $this->Input->setErrors($this->getCommonError("term_error")); return; } break; } }

Yes, that could be it. I posted this under bugs a few days ago but was not aware the limit was 10 years.

Thanks, didn't think about getting the client_id from the URL. This only works on the admin side though, Maybe I can retrieve the client_id from the session on the client side.

PauloV, do you use the Logicboxes module yourself with no problems renewing? There is another thread today: http://www.blesta.com/forums/index.php?/topic/3330-domain-renewal-use-module/ which mentions Logicboxes not working. Also do you know the answer to this? Ok, how does this work with .com domains? When you renew a .com it will only renew it for a year from the renewal date not the expiry date. If a .com expires on 2014/01/07 but the invoice is paid on 2014/01/01 then next year the domain will expire on 2014/01/01. The expiry date in Blesta remains 2014/01/07 so the client doesn't have time to renew before it is cancelled.

+1

Both Logicboxes and Namecheap include code for automatic renewals, is it not working for you? Should happen on payment of invoice. Logicboxes will only go ahead with renewing if it will add any time to the expiry date.

As far as I know those files do change every time Blesta is upgraded - if only to update the version number.

The problem with having plugins change core features is that there can be overlaps or incompatibilities between extensions. Adding an occasional feature to the core (e.g. with vQmod) is fine as is writing a Blesta plugin that extends it. However you are right that there are a lot of feature requests that would be better as a plugin as they are not "core" features.

Look under plugins/order/language. If there is not a file for your language it will use en_us. Also check out this thread: http://www.blesta.com/forums/index.php?/topic/3055-multilanguage-site-bug/

I didn't fully understand your reason for wanting to bill monthly. As I understand it the pro rata feature is for billing on a specific date (e.g. 1st January etc) and if a client signs up half way through the year they will only be charged for 6 months. From the tooltip: As far as I know when pro rata is enabled you can give refunds automatically when they cancel part way through a period. This may be what you're looking for. Even without pro rata you can manually give a refund to a client. Mike from Licensecart may be able to help you as I know he uses pro rata. Blesta is specifically built for web hosts and the functionality you describe seems more like how a software product built for design/development agencies would behave (e.g. workflowmax). However Blesta code is 99.4% open so anything is possible, you just need to hire someone to create a plugin. Edit: Also, if a client pre pays the money will be added as credit to their account. This credit will be automatically applied to any invoices, or in Blesta 3.3 you or your clients can manually apply this to selected invoices.

I don't think this is possible exactly how you describe. Blesta does not support statements yet so if you set a hosting service to be billed monthly then an invoice will be created each month. What you could do is set the service to be billed yearly but mention the monthly price in the service name. This reminds me that I do want to build a statement plugin, but I can't commit to doing this anytime soon. Yes, it is possible to manually print and send invoices or have them sent automatically via InterFax or PostalMethods. Yes, you can create a "free support" service. If you do any other work you can manually create an invoice with the hours and rate or any other costs. You mentioned a web package. Blesta works by having "services" such as web hosting, domain name, support contract etc. Each service will automatically generate an invoice according to the term you set (monthly, yearly etc). If your web package includes web hosting, a domain name and a support contract, you could create three different services, and if they all renew on the same date then each service will show as a line item on a single invoice. The other way to do it would be to have a single service such as web hosting, then several add-ons for that service for a domain name and support contract. These should show as line items on the invoice.

Reposting my answer from another thread for the benefit of those reading this thread:

Personally I think if you are going to be sending a lot of mass mail and categorising it etc. then it would be much better to write a plugin to tightly integrate something like Mailchimp into Blesta which already has all these features and much more.

Changing the registrant nameholder field is not possible for some domains including .nz. The only way to change it is by providing a change of ownership form signed by both the current and new nameholders. This is important because it is the one field that defines the owner of the domain. One client may want to register several domains but have some registered under their personal name and some registered under one or more company names. They may even want to register domains on behalf of their own clients. I have added the fields and passed them to addService, but as you mention the problem is that I need to retype info that's already stored. If I had the client_id in the getAdminAddFields and getClientAddFields methods then I could pre-populate the fields with client data so that I can see what values are going to be used and change any that are necessary. I have explained above the reason why having a nameholder field is important, but as I said for a phone number my registrar only accepts three values (country code, area code, number) and it is not possible to reliably split phone numbers in the client info into three values. The other reason is that most WHOIS fields are required, but not all client fields are required (at least not though the admin panel) and I can't add in the missing info because I don't have it. I could make three fields for the clients phone number and make them required but I don't really like the idea of having these in addition to the existing phone number fields. The NZ registry doesn't require any other custom info like some other registries. I don't know if anything of this type if being done with the new domain manager but the best option would be the ability to chose contacts saved in the clients account or create a new contact when registering a domain. There is still the issue of formatting phone numbers but I think this is more an issue with my particular registrar as I'm pretty sure the NZ registry doesn't require the number to be separated into three. I am also aware that I can pass the client_id to the getAdminAddFields and getClientAddFields methods myself but this requires changes be made to core files and means the module is not stand-alone any more.

Does anyone have a good argument for supporting the older versions? Unless you're running it on the same server as lots of shared hosting clients you should be able to keep PHP updated easily. And if that is the case just put Blesta on it's own VM. I have a VM especially for Blesta/main site and I'm currently running 5.5, upgrading to 5.6 soon.

Yes, I can get them via the addService method, but I want to have all the WHOIS fields visible on the add service page and pre-filled but able to be modified. Not all my clients have all their details filled out and my registrar requires phone numbers in three separate fields so a lot of domain registrations would fail. I'm pretty sure that my registry requires the client to enter the nameholder/organisation/registrant each time when registering a domain as this is locked and not easily changed afterwards.