wfitg

vQmod is useful for making custom changes to software without actually making changes to it. Blesta doesn't use vQmod, but the use of any third-party code, whether it be via vQmod, modules, plugins, etc., may contain code that disrupt's Blesta's security, as you put it.
 
 
 
Blesta has been around since 2007, but v3.0.0 has only been around since last year, which is what most people seem to be referring to.
 
 
 
I like keeping it simple and straight-forward. There will always be feature requests here, but that doesn't necessarily mean they will be added into the core of Blesta. Some of them have been supported in 3rd-party plugins already, or are better suited toward a plugin. I wouldn't worry too much about Blesta becoming bloatware--it won't.

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.

The OP's approach is more or less what we're already working toward. This is the reason we have extensions. For instance, the Order plugin is not apart of the core, although we currently ship it with Blesta by default. Likewise, gateways and modules are not apart of the core either.
 
However, there is still going to be a need for core features to some degree. Currently, there are several still pending, such as the ability to merge clients. Many other features, like a mass mailer, are better suited as plugins. We still need to expand on the event system in Blesta to allow for extensions to perform more actions.
 
There's always going to be some users that need custom feature X, or want feature Y to be changed slightly to work better for their business. But we don't intend to add or change core features that only 1% of users will use. Plugins are better suited in those cases. In the future, you will probably see a decrease in core features, and an increase in extensions.

Tyson responded while I was typing, so just to add to what he said --
 
We carefully consider every core feature, if it doesn't make sense to be part of the core then it's implemented as an extension. Take a look at the Order System and the Support Manager. Both very well used, often necessary major features.. but we understand that other developers may create something that people prefer to use instead.
 
Some future features -- KB, Mass Mailer, Affiliate System.. all of these will be plugins. (The KB will actually be part of the Support Manager plugin)
 
Some features just make sense to be part of the core and forcing them to be extensions when they shouldn't be would fragment the system and de-stabilize the most basic function of Blesta. 
 
I ask the following questions when considering a new feature -
 
1. How widely used will the feature be?
2. How likely is it 3rd party developers will want to roll their own?
3. How basic to billing and client management is the feature, regardless of how many people will use it?
 
Not that we go through a checklist, but this should give you an insight into our thought process. It's usually very apparent to us when something should be part of the core or not.

Ok, thanks.

Yes it needs to be applied to every version.

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.

I FOUND the probleme  , is NOT A BUG .......
 
the probelem is from the word typed
 
aghahdahdqq.com != Aghahdahdqq.com
 
aghahdahdqq.com is valid domain name
Aghahdahdqq.com is not a valid term to search
 
 
in the phone , they always return the first letter to uppercase .

hello Mike , see this thread http://www.blesta.com/forums/index.php?/topic/3097-convert-domain-searches-to-lowercase/

I've never heard of anyone confusing a Tax ID with a SSN, but I suppose anything's possible. Just another reason to have optional field support for you to set what you require.

If it is part of the portal I think there should be an option to disable the portal except for the navigation. Because in my case as I'm using Joomla as my CMS I want Blesta to go straight to the account overview/login page.

We are intending to extend the portal plugin into a more fully featured CMS. Adding additional links to the navigation, even if they link to external content (ie your existing website) would be best suited for this plugin most likely. You could create additional pages and enter the content in a WYSIWYG editor in Blesta, or link those pages to external content.

Thanks flangefrog! This is what I was looking for. I wanted the clients to see my website header when they are logging in, and replacing the first PHP code with the second worked! 
 
I may also try to edit some of the rest of the page too with everyone else's other comments. 
 
Thank you everyone!!!

You don't need 777 permissions. If Blesta already runs fine and you can upload files to it then you probably won't need to change anything. Depending on your server configuration file permissions of 644 or even 640 will be enough.

If you want to use a vQmod you have to install vQmod using the files here and the instructions here. Then you can copy the xml files from my links into the /vqmod/xml folder on your installation.

The structure.pdt will be overwritten sometimes when you upgrade Blesta. If you want the changes to be permanent you can copy the "bootstrap" template and rename it, but you will need to add any new changes to your template when upgrading. You could also write a vQmod with the modifications. 

Quick hack to remove the Tax ID/VATIN field from the client's "Edit My Information" page, registration page and ajax, standard and wizard templates. Use with vQmod
 
See:
http://dev.blesta.com/browse/CORE-547
http://www.blesta.com/forums/index.php?/topic/3258-add-option-to-disable-client-tax-id/
http://www.blesta.com/forums/index.php?/topic/476-ask-for-tax-id/
http://www.blesta.com/forums/index.php?/topic/1523-disallow-clients-to-edit-some-fields-from-the-client-area/
 
Version 1.1.0
remove_client_tax_id.xml

On the client's "Edit My Information" page there is a field marked Tax ID/VATIN. I have no idea what this is used for but in New Zealand and probably many other countries it is not applicable.

See link in my sig

+1, I can see this causing a lot of confusion for clients any may put some off. Would love to be able to disable it.

Bugfix to enable Blesta to work in PHP CLI mode (i.e. to enable cron jobs to run)
 
vqmod/install/index.php
Change line 65 from

require_once(\'./vqmod/vqmod.php\'); to
require_once(dirname(__FILE__) . \'/vqmod/vqmod.php\'); vqmod-2.4.1-blesta.zip

Hello Bleastars
 
Here is is a small preview for the new Blesta Bookmarks Plugin that is almost done
 
You will be able to add links to admin and client area
 
you can then add notes to the bookmarks that are visible wen accessing the bookmark.
 
Teaser 1:
 

 
Teaser 2:
 
 

 
 
For all you developers that are asking, "how we call a website to load the content" because "iframes" are now blocked in some cases, for exemple we cannot call blesta forums on a iframe or even facebook website, so we use curl to load the website after that if we click on any link or submit any form it will open a new windows to be able to continue navigating on the website without any problems.
 
 
Any sugestion please tell us to add before finish
 
 
Regards,
PV

Is something like this you want?  http://www.blesta.com/forums/index.php?/topic/3031-blesta-bookmarks-plugin-comming-really-soon-p/?hl=blesta+bookmarks
 
We have almost done, just waiting fot Blesta 3.3 to go stable to release it

Navigation Links , this should be in core function . the $show_header  should be dissapear from the code .