Tyson

There usually are updates to view files with upgrades. Only you know what modifications you've made, so you need to do file comparisons to check and merge any necessary changes. http://www.blesta.com/forums/index.php?/topic/3820-knowledgebase-not-shown-after-upgrade-from-33/?p=28110

All the symbols? What symbols? The non-alphanumeric ASCII 127 characters are removed.

This has been resolved. The issue affects clients that use a custom username rather than their email address.

Nevermind, I see this has already been resolved. CORE-1522

I believe you want to setup a custom payment page in PayPal.

Blank pages may be caused by an error. Enable error reporting in Blesta by updating the config file under /config/blesta.php and make sure error reporting is set to: Configure::errorReporting(-1); Then attempt another backup. When you receive the blank page again, there may be an error displayed that would give more insight into the problem.

I'm not able to duplicate this issue. Can you provide more information? Do you receive the error before/after a payment method is shown? Does it occur for new users that register during the order process, or after you login as an existing user? Anyone else experiencing this error?

This is more or less resolved. The use of UTF-8 characters are still allowed in URI titles, and their proper form is in octets. It is up to your browser to determine whether they are displayed encoded or not.

This has been resolved for v3.4.0-b2.

Odd that you would receive an error regarding an Unknown API method, and the SSL cert is still activated. However, that sounds like an issue with GoGetSSL rather than Blesta. GoGetSSL shouldn't generate an error and then perform the action successfully anyway. What version of GoGetSSL are you using? I'm not aware of any recent updates to their API, but it's possible something may have changed where they deprecated/removed functionality that our module is still using.

We discussed this before, but chose not to do it due to the amount of resource usage required to calculate it recursively. The count is actually the number of categories+articles that are direct descendants of the parent category.

Have you taken a look at the developer documentation on creating gateways for Blesta? It contains details on how to create a gateway along with a sample gateway to get you started.

CORE-1523

Not from Invoices::createFromServices. Delivery options are based on invoices, so there isn't a method by which to remove an option by service ID besides what I already mentioned above. The other way to go about it is to create the invoice from Invoices::add, but you would need to manually create your own line items.

Mine looks fine: ../where's-my-iworx.ini%3F/2/ The question mark would be encoded since it's a special character in URLs--same with others like & and =. Maybe we should just remove +, ?, %, =, #, % altogether. All your files get updated? Any old cached data? I know you had the KB before beta was released, so I wonder if that has anything to do with it.

Did you add it to the portal? Did you enable permissions for your staff group? {% if plugins.support_manager.enabled %}<div class="col-md-4 col-sm-6 portal-box"> <a href="{client_url}plugin/support_manager/client_tickets/add/"> <div class="well"> <i class="fa fa-ticket fa-4x"></i> <h4>Support</h4> <p>Looking for help? You can open a trouble ticket here.</p> </div> </a> </div> <div class="col-md-4 col-sm-6 portal-box"> <a href="{client_url}plugin/support_manager/knowledgebase/"> <div class="well"> <i class="fa fa-info fa-4x"></i> <h4>Knowledge Base</h4> <p>Have a question? Search the knowledge base for an answer.</p> </div> </a> </div>{% endif %}

Did you undo the regex change mentioned above? I don't see any reason why you wouldn't be able to update the username to 8+ characters if you made the other aforementioned changes. Module log info would be helpful.

Undo the regex change you made for the cPanel module -- it's invalid. What action did you perform, and what command is issued via the API that results in that error: "Unable to fetch the cPanel user ..."? You should see it at the top of the input/output module logs, and the input logs should show the username being requested. When adding new users without specifically setting your own username, it will still generate one 8 characters in length. If you still experience an issue with usernames 8 characters or less, then it may be the API that needs to be updated. I haven't tested this, but you could try finding and updating (/components/modules/cpanel/apis/cpanel_api.php): if ( ( $user != null ) && ( strlen( $user ) < 9 ) ) { to if ( ( $user != null ) && ( strlen( $user ) < 17 ) ) { There is no other limitation on username length within Blesta.

There are no predefined templates for the welcome email since that depends largely on the service you've setup. As for the service creation email template, where the welcome email can be injected, you can see an example of one in the screenshot from the documentation.

Welcome! Good to hear the migration went well.

$vars['configoptions'] shouldn't be keyed by an ID, but rather the Name value from your package option. You may want to take a look at how your config options are setup to see why it differs. Consider the Multicraft module. When Multicraft::addService is invoked, an array of $vars is provided, and in my example, $vars contains: Array ( [parent_service_id] => [package_group_id] => 5 [pricing_id] => 2 [module_row_id] => 5 [qty] => 1 [client_id] => 1 [status] => active [use_module] => true [multicraft_server_name] => Minecraft Server [multicraft_server_id] => [multicraft_user_id] => [multicraft_daemon_id] => [multicraft_ip] => [multicraft_port] => [multicraft_players] => 6 [multicraft_memory] => 768 [multicraft_jarfile] => [multicraft_jardir] => daemon [multicraft_user_jar] => 1 [multicraft_user_name] => 1 [multicraft_user_schedule] => 1 [multicraft_user_ftp] => 1 [multicraft_user_visibility] => 1 [multicraft_default_level] => 10 [multicraft_autostart] => 1 [multicraft_create_ftp] => 0 [multicraft_server_visibility] => 1 [configoptions] => Array ( [jarfile] => default [players] => 10 [daemon_id] => 4 [memory] => 256 ) [coupon_id] => [coupon_packages] => Array ( [0] => 2 ) [date_added] => 2014-12-10 17:25:48 [date_renews] => 2015-01-10 17:25:48 )

The thousands place comma, decimal, currency codes, etc. are just for formatting wherever they are displayed, and wouldn't affect the issue he's having attempting to remove some. I'll have to test this issue myself.

The method getFieldsFromInput is a helper method we typically use in our modules, but it is not required, so I would need to know how you're using it to determine whether the fields you're setting make sense in the context its used. You can take a look at the Multicraft module for an example of how config options are set.

Can you let us know what version of Blesta you're using? Could you take a screenshot of the package (specifically the pricing) before and after you receive the error? A list of currencies you have setup in Blesta would be useful too.

Blesta displays the two-character abbreviation code for states/provinces from the ISO 3166-2 standard, and the two or three-character abbreviation code for countries from the ISO 3166-1 standard. For Cyprus, the country is abbreviated as "CY" or "CYP", and the states/provinces are numbered 01-05. In your case it may be better to display the full name of the state/province rather than the ISO code, in which case the client interface and PDF would need to be updated. We have plans to improve international addressing at some point in the future. In the meantime, however, you could update the templates from your install to display the full names.