Abdy

Apparently this bug has already been reported in the CyberPanel GitHub repository as the problem occurs even in the official WHMCS module. https://github.com/usmannasir/cyberpanel/issues/47
I am surprised that they introduce non backward compatible changes to API in a minor update. Apparently they're not using semantic versioning.

A new GoCardless alpha non-merchant gateway is available.
To install, download the attached gocardless.zip and unzip the file. Upload the gocardless directory to ~/components/gateways/nonmerchant/ and go to Settings > Company > Payment gateways to install it.
Documentation is right here - https://docs.blesta.com/display/user/GoCardless
Any comments or suggestions, please post them below.  

Blesta version 4.3.0-b1 (BETA 1) is now available. You can download it from right here (Client Area Login Required). Read the blog post announcement at https://www.blesta.com/2018/06/15/blesta-4.3-beta-released/
This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT.
Please report any bugs you find in the v4.3 beta bug forum.
Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 4.3.0-b1.

For older releases see all Change Logs.

it would be better if Blesta make the logos (client/admin) side as a settings . that way we can upload our custom logos and change them when we want without touching the default template files. it will help also for users that use the default theme to re-upload their logos every time they upgrade in a major release .
if no custom logos is uploaded or set them show the default one

Everyone who requested a refund received it within 24 hours.
I'm really sorry about what happened and promise to reward the people involved as an apology. Everyone who received a refund, will still receive the license (perk) they originally purchased when the module gets released for free.
I don't want to make the same mistake again, so this time I'd rather not give a release date. I take responsibility for the mistake I made and I hope to be able to amend my mistake soon and make my best effort to never repeat it again. I don't want to use this as an excuse, I take full responsibility for the mistake I made, but I think I owe everyone an explanation. 
The development of the module started in the last week of November 2017, but because I had several projects and tasks to do for other clients, I had no more time available in my schedule to develop the module on my own. So I decided to hire a full-time PHP developer in the first week of December to take over the development of the module. However, for reasons unknown to me, the last week of December my developer quit, causing development to stop.  I personally like to make code that not only works, but is also visually beautiful, trying my best to follow the development standards and follow good coding practices. 
However, I couldn't find another developer that met my criteria, because very few developers are familiar with Blesta. Because of this I started working on the module on my own during the weekends to prevent development from stopping completely, but it still ended up being delayed considerably. Having already finished some of the biggest projects I had, last week I resumed the development of the module again, at half time. Also, last week I got a new developer who will be able to help me in the development.
During this time I decided to make some changes. The final release of the module will not be called cPanel Extended, as I try to avoid confusion with the ModulesGarden module. In addition, the module will not be released under the CyanDark brand, as I am working on a new site specifically dedicated to sell only Blesta related products. With a development team independent of the CyanDark's team to avoid problems.
This is one of the most popular modules that I have, and I promise you that I will not let the module die, soon I will publish more news about the progress of development, but I prefer not to give an ETA at the moment, to avoid problems.
Anyway, I give you my sincere apologies and I hope you can pardon me for my mistake.

Everyone who requested a refund received it within 24 hours.
I'm really sorry about what happened and promise to reward the people involved as an apology. Everyone who received a refund, will still receive the license (perk) they originally purchased when the module gets released for free.
I don't want to make the same mistake again, so this time I'd rather not give a release date. I take responsibility for the mistake I made and I hope to be able to amend my mistake soon and make my best effort to never repeat it again. I don't want to use this as an excuse, I take full responsibility for the mistake I made, but I think I owe everyone an explanation. 
The development of the module started in the last week of November 2017, but because I had several projects and tasks to do for other clients, I had no more time available in my schedule to develop the module on my own. So I decided to hire a full-time PHP developer in the first week of December to take over the development of the module. However, for reasons unknown to me, the last week of December my developer quit, causing development to stop.  I personally like to make code that not only works, but is also visually beautiful, trying my best to follow the development standards and follow good coding practices. 
However, I couldn't find another developer that met my criteria, because very few developers are familiar with Blesta. Because of this I started working on the module on my own during the weekends to prevent development from stopping completely, but it still ended up being delayed considerably. Having already finished some of the biggest projects I had, last week I resumed the development of the module again, at half time. Also, last week I got a new developer who will be able to help me in the development.
During this time I decided to make some changes. The final release of the module will not be called cPanel Extended, as I try to avoid confusion with the ModulesGarden module. In addition, the module will not be released under the CyanDark brand, as I am working on a new site specifically dedicated to sell only Blesta related products. With a development team independent of the CyanDark's team to avoid problems.
This is one of the most popular modules that I have, and I promise you that I will not let the module die, soon I will publish more news about the progress of development, but I prefer not to give an ETA at the moment, to avoid problems.
Anyway, I give you my sincere apologies and I hope you can pardon me for my mistake.

Everyone who requested a refund received it within 24 hours.
I'm really sorry about what happened and promise to reward the people involved as an apology. Everyone who received a refund, will still receive the license (perk) they originally purchased when the module gets released for free.
I don't want to make the same mistake again, so this time I'd rather not give a release date. I take responsibility for the mistake I made and I hope to be able to amend my mistake soon and make my best effort to never repeat it again. I don't want to use this as an excuse, I take full responsibility for the mistake I made, but I think I owe everyone an explanation. 
The development of the module started in the last week of November 2017, but because I had several projects and tasks to do for other clients, I had no more time available in my schedule to develop the module on my own. So I decided to hire a full-time PHP developer in the first week of December to take over the development of the module. However, for reasons unknown to me, the last week of December my developer quit, causing development to stop.  I personally like to make code that not only works, but is also visually beautiful, trying my best to follow the development standards and follow good coding practices. 
However, I couldn't find another developer that met my criteria, because very few developers are familiar with Blesta. Because of this I started working on the module on my own during the weekends to prevent development from stopping completely, but it still ended up being delayed considerably. Having already finished some of the biggest projects I had, last week I resumed the development of the module again, at half time. Also, last week I got a new developer who will be able to help me in the development.
During this time I decided to make some changes. The final release of the module will not be called cPanel Extended, as I try to avoid confusion with the ModulesGarden module. In addition, the module will not be released under the CyanDark brand, as I am working on a new site specifically dedicated to sell only Blesta related products. With a development team independent of the CyanDark's team to avoid problems.
This is one of the most popular modules that I have, and I promise you that I will not let the module die, soon I will publish more news about the progress of development, but I prefer not to give an ETA at the moment, to avoid problems.
Anyway, I give you my sincere apologies and I hope you can pardon me for my mistake.

Everyone who requested a refund received it within 24 hours.
I'm really sorry about what happened and promise to reward the people involved as an apology. Everyone who received a refund, will still receive the license (perk) they originally purchased when the module gets released for free.
I don't want to make the same mistake again, so this time I'd rather not give a release date. I take responsibility for the mistake I made and I hope to be able to amend my mistake soon and make my best effort to never repeat it again. I don't want to use this as an excuse, I take full responsibility for the mistake I made, but I think I owe everyone an explanation. 
The development of the module started in the last week of November 2017, but because I had several projects and tasks to do for other clients, I had no more time available in my schedule to develop the module on my own. So I decided to hire a full-time PHP developer in the first week of December to take over the development of the module. However, for reasons unknown to me, the last week of December my developer quit, causing development to stop.  I personally like to make code that not only works, but is also visually beautiful, trying my best to follow the development standards and follow good coding practices. 
However, I couldn't find another developer that met my criteria, because very few developers are familiar with Blesta. Because of this I started working on the module on my own during the weekends to prevent development from stopping completely, but it still ended up being delayed considerably. Having already finished some of the biggest projects I had, last week I resumed the development of the module again, at half time. Also, last week I got a new developer who will be able to help me in the development.
During this time I decided to make some changes. The final release of the module will not be called cPanel Extended, as I try to avoid confusion with the ModulesGarden module. In addition, the module will not be released under the CyanDark brand, as I am working on a new site specifically dedicated to sell only Blesta related products. With a development team independent of the CyanDark's team to avoid problems.
This is one of the most popular modules that I have, and I promise you that I will not let the module die, soon I will publish more news about the progress of development, but I prefer not to give an ETA at the moment, to avoid problems.
Anyway, I give you my sincere apologies and I hope you can pardon me for my mistake.

Everyone who requested a refund received it within 24 hours.
I'm really sorry about what happened and promise to reward the people involved as an apology. Everyone who received a refund, will still receive the license (perk) they originally purchased when the module gets released for free.
I don't want to make the same mistake again, so this time I'd rather not give a release date. I take responsibility for the mistake I made and I hope to be able to amend my mistake soon and make my best effort to never repeat it again. I don't want to use this as an excuse, I take full responsibility for the mistake I made, but I think I owe everyone an explanation. 
The development of the module started in the last week of November 2017, but because I had several projects and tasks to do for other clients, I had no more time available in my schedule to develop the module on my own. So I decided to hire a full-time PHP developer in the first week of December to take over the development of the module. However, for reasons unknown to me, the last week of December my developer quit, causing development to stop.  I personally like to make code that not only works, but is also visually beautiful, trying my best to follow the development standards and follow good coding practices. 
However, I couldn't find another developer that met my criteria, because very few developers are familiar with Blesta. Because of this I started working on the module on my own during the weekends to prevent development from stopping completely, but it still ended up being delayed considerably. Having already finished some of the biggest projects I had, last week I resumed the development of the module again, at half time. Also, last week I got a new developer who will be able to help me in the development.
During this time I decided to make some changes. The final release of the module will not be called cPanel Extended, as I try to avoid confusion with the ModulesGarden module. In addition, the module will not be released under the CyanDark brand, as I am working on a new site specifically dedicated to sell only Blesta related products. With a development team independent of the CyanDark's team to avoid problems.
This is one of the most popular modules that I have, and I promise you that I will not let the module die, soon I will publish more news about the progress of development, but I prefer not to give an ETA at the moment, to avoid problems.
Anyway, I give you my sincere apologies and I hope you can pardon me for my mistake.

Recently got an API key for VeriSign's Name Studio, and thought it'd be a decent opportunity to get my hands dirty with a Blesta integration. I've probably broken all kinds of rules and best-practices in implementing it, but not too far from a workable release.
Early WIP, but there are a few screenshots below.
Curious if anyone would find this useful.


EDIT: FWIW if y'all apply for a name studio account now I should have something out by the time they approve your account. It's free, though does have some generous rate-limiting in place (in which case the plugin will just not show any suggestions at this stage).
It's a janky process and took a few days - they called me a few days after applying and spelled the account's default password out character by character ?
Another edit: Feel free to follow along at home/fork and make fantastic - https://github.com/nahanil/blesta-namestudio-plugin

I just tried in my Blesta installation and got the same (weird) result. I think the solution you're proposing is pretty good, I did some testing even using Punnycode domains and it seems to work perfectly.

Referring to the method getSld() in <Blesta 4.2.2>/plugins/order/lib/order_types/domain/order_type_domain.php
This method doesn't handle domain searches as gracefully as it could.
Search: www.something.com (.com checkbox selected)
something.com somethingwww..com Search: www.something (.com checkbox selected)
www.com Search: something.com (.com checkbox selected)
something.com Search: something (.com checkbox selected)
something.com  
I'm not sure how this could be rectified by changing the existing regex, but I've found something like the following to handle all the above inputs to return something sensible
function getSld($domain) { $parts = explode(".", $domain); if (count($parts) == 1) { return $parts[0]; } return $parts[0] == "www" ? $parts[1] : $parts[0]; } // Mentioned test cases foreach ([ 'www.something.com', 'www.something', 'something.com', 'something'] as $search) { echo "$search: ", getSld($search), "<br>"; } /* Output www.something.com: something www.something: something something.com: something something: something */  

In order to understand recursion, one must first understand recursion.

https://invisioncommunity.com/contact-us

Just because Twitter made a mistake with their logging, doesn't mean that they don't know what they are doing. Twitter has some of the brightest engineers in the world on their team, many of which I'm sure, would disagree with you. Still, how IPBoard operates is outside our control and you should always assume an attacker has your username.

This was a change that IPBoard made.. after upgrading one day, users were forced to login with display name. Not aware of any account compromises, if you have a decent password, you should be fine, and we block brute force attacks.

NameSilo Domain Module
This module is a complete solution for domain registrations and transfers through NameSilo.  This module builds upon and continues the work by @NETLINK.  He and I will be jointly contributing to this project and we welcome any other contributions on GitHub.
An old thread related to this plugin was at https://www.blesta.com/forums/index.php?/topic/3399-namesilo-plugin
Features
Domain registrations Domain transfers Supports all NameSilo-supported TLDs by dynamically listing the available ones to package creation Proper .us/.ca support with necessary fields on order forms NameSilo audits Sync service's renewal date with domain expiration date Register/manage nameservers/hosts Set/change nameservers Update WHOIS details Lock/unlock domain Retrieve EPP code DNSSEC management Check email validation & resend validation email if needed Toggle WHOIS privacy Manually extend registration Transfer status tracking Screenshots
Coming soon
Installation
https://github.com/knownhost/Blesta-Namesilo/blob/master/README.md
Upgrading
Nothing special is required except when updating from <1.8.0.  In this case see the "Other" section below.
Known Issues
A domain transfer can be ordered for more than 1 year.  NameSilo's API does not allow a transfer to extend more than one year so the extra years would be lost if not manually corrected.  I'm unsure of how we'll solve this at this point. Future Plans
Update for Blesta's new domain management system when release.  This will be the v2.0 milestone and will likely be mostly a rewrite of the module. Clean code and remove unnecessary code. Manually extending as an admin should support invoicing/queuing to post-payment.  We should be able to do this with the proration logic. DNSSEC management Implemented! Source
This module is fully open source and can be found on GitHub.  Two repos are kept fully updated with releases currently being built on the second:
https://github.com/knownhost/Blesta-Namesilo
https://github.com/NETLINK/Blesta-Namesilo
Download
I will make every effort to maintain the listing in the marketplace at https://marketplace.blesta.com/#/extensions/80-NameSilo Module
GitHub will always definitely be up-to-date: https://github.com/NETLINK/Blesta-Namesilo/releases
Other
The version 1.8.0 release is a major update building upon @NETLINK's work.  The new auditing features will not work properly until you "manage" and save your NameSilo account settings.  Everything else should be fully backwards-compatible.

Hey All,
Coming from a background in developing with Symfony, I've used Twig a lot. Also used templating engines such as smarty and mustache/handlebars - but I believe Twig to be the better of the bunch.
I've seen there was a little discussion about Twig in late 2016 and mid 2017. However, I thought it might be a nice idea to have a constructive discussion about Twig and Blesta?
Even if the end decision was not to use Twig, the discussion might help improve the templating system. Most notably for new-comers to Blesta from competitors or a background like mine (Symfony/Twig or Laravel/Blade).
I'll start off with a few points:
Conciseness
Personally, I believe Twig to be more easy to read and follow the logic, given it's brevity.
Also, since it uses braces ({}) and not angled brackets (<>), it helps give a contrast between template code and the actual HTML. All this helps readability, which can speed up development and maintainability.
Arguably, the same could be achieved in PHP via short tags like <? ?> and <?=$var?> - but I believe you may need to enable them in PHP, which is probably why Blesta isn't using them already (given the self-hosted nature). <div class="row<?php echo (!$this->Html->ifSet($show_header, true) ? ' login' : '');?>"> <?php if (!empty($active_nav['secondary'])) { ?> <div class="col-md-3"> <div class="list-group"> <?php foreach ($active_nav['secondary'] as $link => $value) { ?> <a href="<?php $this->Html->_($link);?>" class="list-group-item borderless left-nav <?php echo ($value['active'] ? 'active' : '');?>"> <i class="<?php $this->Html->_($value['icon']);?>"></i> <?php $this->Html->_($value['name']); ?> </a> <?php } ?> </div> </div> <div class="col-md-9"> <div class="row"> <?php echo $content;?> </div> </div> <?php } else { echo $content; } ?> </div>
versus...
 
<div class="row{% if not show_header %} login{% endif %}"> {% if active_nav.secondary is not empty %} <div class="col-md-3"> <div class="list-group"> {% for link, value in active_nav.secondary %} <a href="{{ link|e }}" class="list-group-item borderless left-nav {% if value.active %}active{% endif %}"> <i class="{{ value.icon|e }}"></i> {{ value.name|e }} </a> {% endif %} </div> </div> <div class="col-md-9"> <div class="row"> {{ content }} </div> </div> {% else %} {{ content }} {% endif %} </div> (I didn't test this Twig code, just to confirm)
 
Control Structure Syntax
This kind of comes into conciseness, but is only really for PHP.
It might be beneficial to use the alternative syntaxes, instead of braces {} in the pdt templates. It would certainly help me get less confused when reading large chunks  
http://php.net/manual/en/control-structures.alternative-syntax.php
  IDEs
I use PHPStorm, and it has features for Twig, such as better highlighting, auto-completes, etc. With pdt templates being literally PHP, I had to just set them to plain-ol' PHP files - meaning no helpers from the IDE that can speed up development. 
  Inheritance, blocks
I think this is probably quite a big point, as blocks are more-or-less how the templating engine in Blesta works - except it's all in the core code.
Again, it helps readability - given that from just the template file, I know all of the templates that are gonna be executed.
As an example, it can also be useful if someone wanted to change other code on specific pages. In Twig, I'd be able to edit just the one template file - however, with the current system, I'd have to edit core files, which would end up being a pain with upgrades overwriting the files. {% extends "structure.html" %} {% block content %} <b>Content of the page...</b> {% endblock %} opposed to just having a file on it's own with the page content, and having to rely on the core code to define everything else: <b>Content of the page...</b> Extensibility
Obviously, PHP is PHP, and you can do what you like with creating functions etc (however, loading them into the template engine is probably another dicussion).
Twig is very versatile in the respect.
For example, phpBB made the switch from their own engine to Twig, and was able to code extensions to Twig to allow all their old templates to run under Twig.
https://www.phpbb.com/community/viewtopic.php?f=461&t=2424606
  Everything else over on the Twig homepage -https://twig.symfony.com/  
Obviously, it'll involve a bit of work to move over to Twig, but I feel it would be beneficial in the long run, help new-comers, and more importantly help grow the development of themes for Blesta.
Given Blesta has a template engine orchestrating everything, I might have a little play around with integrating it myself. ?

Hopefully we get a good discussion going on the topic?
 
sidenote - I noticed that templates for plugins can't get overwritten in the app/views/ directory? Thought this was a bit odd, given that most template files have a unique name. So, could we possibly check the app/views/ first before going back to the plugin default. Personally, I wanted to edit a template file in the support_manager plugin but keep all my theme files in one central location (with Git). Unfortunately, I think that I might have to end up with template files here there and everywhere? :S
 

The new version will include confirmation popovers on all irreversible action buttons, such as the "Delete" button.
There is not yet available.

The new version will include confirmation popovers on all irreversible action buttons, such as the "Delete" button.
There is not yet available.

LogicBoxes Extended
LogicBoxes Extended For Blesta is a module created specially for LogicBoxes API to enable you to automate the provisioning and management of domains in your Blesta system. With its help you will be able to set up your TLDs & gTLDs with just a few clicks to start reselling them to your customers right away!

Features:
Edit All The Contact Information (Whois) Change Name Servers Set Forwarder Set Child Name Servers Get Authorization Code Change Authorization Code Ability To Sell Private Whois (Using Options) Automatic Synchronization of Expire Date for Transfered Domains DNS Manager  Versions:
Update 1.0:
First Version Released. Update 1.1:
Optimized for Blesta 4.0. Update 1.2:
DNS Manager NOTE: If you want sell "Private Whois", you need add a Option like the following screenshoot.


Screenshots:




Download:
LogicBoxes Extended is available in the Blesta Marketplace for only $49.99 per year or $199.99 one time and you can order here https://marketplace.blesta.com/#/extensions/32-LogicBoxes Extended

The new version will include confirmation popovers on all irreversible action buttons, such as the "Delete" button.
There is not yet available.

Thanks, I will post an update daily. 

This is one of the small changes (but useful) that will be included in the next version of cPanel Extended.

This is one of the small changes (but useful) that will be included in the next version of cPanel Extended.