Leaderboard

As promised

Thank you both Scott Horsley, MemoryX2 and Paul for the support and help as I had a few mistakes. Please make sure you remember the link to your customer area for this. Please be careful, this step is very important go to /config/blesta.php find the following line just at the bottom of the page: Configure::set("Blesta.csrf_bypass", array()); and replace it with: Configure::set("Blesta.csrf_bypass", array('client_login::index')); The link below must be the link to your client area we've edited the link ourselves by editing the file (/config/routes.php): <form method="post" action="http://billing.licensecart.com/customers/login/"> Then after the custom code edits and the hard bit for a few people, simply copy the rest of the code below: sername: <input type="text" name="username" value="" id="login_username" /><br /> Password: <input type="password" name="password" value="" id="login_password" /><br /> <input type="submit" name="login" value="Login" class="btn" /> </form> You can use the "class=btn" if you are using the bootstrap framework on your website. So the final code should look something like: <form method="post" action="http://billing.licensecart.com/customers/login/"> Username: <input type="text" name="username" value="" id="login_username" /><br /> Password: <input type="password" name="password" value="" id="login_password" /><br /> <input type="submit" name="login" value="Login" class="btn hide_submit" hidefocus="true" /> </form> That will now allow users to log straight into your billing system. You can use target="_blank" on the form to open into a new tab. Using Bootstrap and wish to use the posh Modal just edit the code below: <!-- Button to trigger modal --> <li><a href="#login"role="button" data-toggle="modal">Login</a> <!-- Modal --> <div id="login" class="modal hide fade" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true"> <div class="modal-header"> <button type="button" class="close" data-dismiss="modal" aria-hidden="true"><i class="icon-remove text-error"></i></button> <h3 id="myModalLabel">Billing Area Login</h3> </div> <div class="modal-body"> <p><form method="post" action="http://billing.licensecart.com/customers/login/" target="_blank" style="width: 200px;margin: 0 auto 0 auto;"> Username: <input type="text" name="username" value="" id="login_username" /><br /> Password: <input type="password" name="password" value="" id="login_password" /><br /> <input type="submit" name="login" value="Login" class="btn hide_submit" hidefocus="true" /> </form></p> </div> <div class="modal-footer"> <button class="btn btn-danger" data-dismiss="modal" aria-hidden="true">Close</button> </div> </div> Good luck with your great layout and the best billing system.

The ability to change which client template to use has been added for v3.2 in CORE-961. You'll always want to keep backups of core template files you modify, and merge them into new releases accordingly. Even if you were using custom templates, you would still need to check them on new releases since data, structure, and language definitions can be added, changed, or removed that has the potential to break things in your templates. The beta releases would be a good time to update your custom templates with these kinds of changes.

Precisely. And I'm good with just that. :-)

I believe the tabs will come on the forum soon. I was talking to Paul ages ago about custom tabs.

I personally am just fine downloading a CSV and putting it through VerticalResponse. :-) I can definitely see the value in sending directly through Blesta, but there is a point where you can run into walls, like your upstream provider thinking you are spamming. I personally really like VerticalResponse because you can buy X number of credits and you have a whole year to use them.

One thing I'd like to see also, is a "test email" option where I can send a copy of the email to myself, perhaps randomly selecting a customer whos details will be used. This way, if I have a stupid error in the email I can correct it before sending it to everyone.

Paulov's suggestion of making it cron based would solve the issue of requiring the browser to be active while sending. Instead, the cron could send and log the message, and the browser would simply make ajax requests to Blesta to display that log dynamically. The downside is that you'd have to wait up to 5 minutes for the message to go out. Great suggestions