Leaderboard

You should also click the cog/gear icon on the Billing > Overview page for the Orders widget. You can subscribe to order emails so that you are notified for new orders. Each staff member who has access to this widget can access this and receive new order emails. While getting payment notices may be good, this is probably what you want.

What LukesUbuntu mentioned should suffice for fetching client data in case you want to omit or prepopulate field data. There is no difference between adding the service as an admin or a client, so an admin ID shouldn't be relevant.

The translator currently allows for contributors to fetch a Google translation before saving their own. In the future, we will likely start out each language completely translated by Google, and allow contributors to revise them. There are about a dozen contributors that have translated Hungarian at the moment, and we cannot simply delete all of their translations. However, as more contributors translate the definitions, the more accurate they will become. But if you notice improper translations, such as random text or profanity, then we can take a look at those individually.

Permissions are so dependent on the system using them, and since Blesta's API is so extensive, it would be cumbersom, both from a UI perspective, and from an implementation perspective to add permissions for all supported actions. You're best bet is a plugin. It gives you the control and isolation to ensure permissions are enforced as your business requirements dictate, and it doesn't requiring evaluating thousands of individual permission options to setup. Not only that, but Blesta's API is an every evoling thing. So it really isn't a good idea to allow third parties to use it directly. We use the plugin option for controlling access with our own internal and external integrations, and we really wouldn't want it any other way.

Thanks for your help on this @Max, glad this has been resolved. I have mentioned this in the documentation at http://docs.blesta.com/display/user/Installing+Blesta#InstallingBlesta-Errors as well. If you have any comments/suggestions on how this can be worded better, please let me know.

Attached is a test script you can execute on your server to help diagnose issues with setting include paths. To use, unzip test_include_path.zip, then run it once via your web server, and via CLI. You should have the same exact result for each, printing "SUCCESS!!" at the bottom. php test_include_path.php Expected output: php test_include_path.php Current include path: .:/usr/bin/pear Modifying include path to include: /var/www/html/include_path_test/includes Include path is now: .:/usr/bin/pear:/var/www/html/include_path_test/includes Success. Attempting to a include file. Should print "SUCCESS!!" below... SUCCESS!! If you don't receive a success, your php.ini file is configured improperly, or your user does not have permission to execute files. include_path_test.zip

You don't need to put in any directory, just double check the value can be overriden by code. If you're using nginx instead of Apache, check your php-fpm.conf. Same concept, php_admin_value cannot be overriden, php_value can.

Blesta attempts to add the phpseclib folder to the include_path by calling set_include_path(), but looking at the include_path in your stack trace failed to do so. For testing purposes, try modifying in app/models/license_manager.php // Set the include path to include this vendor library set_include_path(get_include_path() . PATH_SEPARATOR . $this->path_to_phpseclib); to: // Set the include path to include this vendor library if ( ! set_include_path(get_include_path() . PATH_SEPARATOR . $this->path_to_phpseclib) ) { die("Error! My webserver configuration prevents me from changing the include_path!"); } If it prints out that error, it conforms my theory. In that case, go through your Apache configuration files looking for a line starting with "php_admin_value include_path" and change it to "php_value include_path" "php_admin_value" means: set this configuration option, and as a security restriction prevent code from overriding it at runtime. "php_value" does allow code to change the value set.

Hello Paul, Was wondering if you guys thought about the possibility of switching it over to being able to purchasing without having to submit the details for the certificate right at checkout. Reason for this is most of the time the company who assigns people to purchase the "SSL" have no clue about what it is, but they just know it's tasked upon them to get an "SSL" renewed/ordered for the company. Later on however, once paid they'll alert the technical team about the purchase, and they'll often take over when they have time. The way above is better not only for the customer, but also the business as they're getting the money from a customer who might not know how to get an SSL, and will need guidance. Versus that of turning them away because they see another language on the checkout form. Overall just feel it'd be better to switch it over to asking for them to "Generate" the certificate after purchase, and if that could be implemented that'd be awesome Edit: Along with maybe having the order inputs when checking out pre-populated with an example of what is expected to be put in the order fields, would be another great idea. As for some people they're not aware they're supposed to use "US" instead of United States.

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