Cody

Looks like the issue is with the controller that invokes that method, as the documented behavior of the Clients::create() method is to always send the welcome email unless 'send_registration_email' is explicitly != "true".

Copy the file, this fix will be available in 3.0.5.

Yes, that's correct.

Yes, replace those as well.

Bags of money always helps.

Change the 'clients_start' value in the company_settings table, or use the API Companies::setSetting() command.

You sure it's the same exact error? If so, then you've still got a few duplicates users in there. Also, are you sure you're starting with a fresh Blesta 3 database each time you run the import?

It looks like your installation is not able to receive a response from payflowpro. Have you checked your payflow transactions to see if payflow received the transaction? If so, you may have port 443 ingress blocked at a firewall. If not, your IP address may have changed and it may not be whitelisted for your account. No changes to payflowpro were made since 3.0.3.

copy and rename /components/invoice_templates/default_invoice/ to "custom_invoice" or whatever you want to call it, but here I'll assume "custom_invoice". Rename /components/invoice_templates/custom_invoice/default_invoice.php to custom_invoice.php. Rename /components/invoice_templates/custom_invoice/default_invoice_pdf.php to custom_invoice_pdf.php Rename /components/invoice_templates/custom_invoice/language/en_us/default_invoice.php to custom_invoice.php Open /components/invoice_templates/custom_invoice/custom_invoice.php and string replace "DefaultInvoice" with "CustomInvoice" Open /component/invoice_templates/custom_invoice/custom_invoice_pdf.php and string replace "DefaultInvoice" with "CustomInvoice" Open /components/invoice_templates/custom_invoice/language/en_us/custom_invoice.php and string replace "DefaultInvoice." with "CustomInvoice." Unfortunately documentation is not currently available for Invoice Templates. Basically what you'll want to do is focus on making changes in /components/invoice_templates/custom_invoice/custom_invoice_pdf.php. It should be pretty self-explanatory. Once you've copied/renamed as I've explained above Blesta will detect your custom invoice template. Yes, please let us know what questions you have as it will help in creating/improving the documentation on the topic.

So you uploaded files when 3.0.2 came out, then again for 3.0.3, but you never ran the upgrade? That's not good. You might have other issues, but for now what you can do is update /components/upgrades/tasks/upgrade3_0_2.php and change line 76: From: $this->Record->insert("settings", array('key' => "root_web_dir", 'value' => $public_root_web)); To: //$this->Record->insert("settings", array('key' => "root_web_dir", 'value' => $public_root_web));

CORE-815. Fixed in 3.0.5. To patch yourself, update /plugins/support_manager/components/email_parser/email_parser.php line 31 From: return $charset; To: return trim($charset, "\"\'");

Any issues with the above file before I mark this as closed?

Thanks for the report. Added CORE-815 for version 3.0.5.

Moved to feature requests as not a bug.

Why are you trying to be condescending? Is it because you don't understand the problem? Because that's what it looks like. The temp directory in Blesta settings is for reading, writing, and moving files. That's its sole purpose. This value is configurable and must be writable by Blesta. The entire system should use this setting whenever a temp directory is needed. That is why I created CORE-808, because the support manager does not use that setting when dealing with email attachments AND IT SHOULD because where Blesta writes files to should be predictable. Arguing the default permission on Windows is a moot point. Look, I run Blesta on Windows too. I don't have the problems you're having because my permissions just work. Maybe that's because I'm using WAMP. Regardless, the issue you're experiencing is not isolated to Windows. It's a permission issue. It can happen to users on Linux just as easily as it can happen to users on Windows.

Why is that? Can't you simply set the proper permissions to your temp directory, or just update [settings] > [system] > [General] > [basic Setup] to point to the directory you setup in your php.ini file? The purpose of the temp directory is to write files that may be moved, read, or written to. Again, we come back to a permission issue. It isn't satisfactory to say the temp directory as defined in the settings is only good for writing/reading from but not for moving files out of. That's just silly.

There is essentially no performance difference (http://www.phpbench.com/). But I have neither the time nor patience to get into a protracted argument of the pros and cons of performance vs readability which are, on occasion, diametrically opposed. I couldn't possibly disagree more. Readability, while somewhat objective as you've come to find, is not about one man's issues. That's nice, but they're not constrained by this style guide so their opinion is moot. Maybe they prefer spaces over tabs, I don't care. A style guide is created and enforced by those that have their heads in the code each and every day. There are as many style guides as there are development teams. If PSR existed when we started Blesta, maybe we would have conformed to that standard instead (unlikely because tabs are better than spaces), but I digress.

That error tells you that one of the required parameters (required by the resource you're requesting) is not being provided. Check the source docs to see which parameters are required and ensure you're passing them in (http://source-docs.blesta.com/class-Clients.html#_create). Since that method only requires a single parameter it looks like you're missing the "vars" parameter. You should have something like: $params = array( 'vars' => array( // all indexes required by the $vars parameter as per the source docs. ) );

Fixed in CORE-806 for 3.0.5.

I've created CORE-808 to fix the issue with EmailParser::getAttachments() incorrectly using the PHP function sys_get_temp_dir() to determine the temp directory. Instead it should be using the temp directory setting as defined in [settings] > [system] > [General] > [basic Setup].

Slower to type? Because it certainly isn't slower to execute. Why have we made double quotes required for string literals? Because: Double quoted strings are more powerful. It improves readability, allowing quick identification of array indexes vs string literals. All of the Blesta devs come from a C/Java background so it's only natural from our perspective. Because of #3, if we didn't define how string literals should be handled we'd potentially have a mess of code with mixed quoting which negatively affects readability.

Version 3.0.4 is now available. You can download it at https://account.blest...er/client_main/. This is a patch release that corrects issues with 3.0.0. Patching Blesta See Patching Blesta in the User Manual for instructions. Release Notes - Blesta Core - Version 3.0.4 ## Version 3.0.4 2013-10-07 ### Bug * [CORE-728] - Some email templates contain URL tags not prepended with the HTTP protocol * [CORE-729] - Some email templates incorrectly have the HTTP(S) protocol prepended to certain URL tags at run time * [CORE-762] - LogicBoxes: Additional fields are shown when going back to edit service details before creating it * [CORE-770] - Update "uncanceled service" error message when attempting to delete a module row that is referenced by canceled services * [CORE-772] - Plugin::getEvents() and Plugin::getActions() not invoked after upgrade * [CORE-774] - Appending service to existing invoice does not recalculate invoice totals * [CORE-775] - Changing a tax rule's status to 'inactive' sets it to an invalid status * [CORE-776] - Transaction fails to apply due to rounding error * [CORE-777] - Tax Rules Level 2 missing zebra-striping * [CORE-778] - Universal Module: An empty service option row should not be saved as a valid option * [CORE-779] - Attempting to void a paid invoice displays an unvoid button on error * [CORE-780] - Editing a template may cause an undefined property Emails::$parseError if errors are set for the template * [CORE-781] - Support Manager: Last reply info in ticket is non-determinisitc * [CORE-782] - Packages with 0 quantity can still be ordered * [CORE-783] - Import Manager: Invalid join in Blesta 2.5 migrator * [CORE-784] - API: companies/generatekeypair never completes * [CORE-793] - Setting package prices to non-double types causes number_format error * [CORE-794] - Default from addresses contain port number when hostname contains port number * [CORE-795] - Email Log incorrectly logs email content when HTML is disabled * [CORE-796] - Security: XSS Vulnerability in message dialogs * [CORE-797] - Security: Potential XSS Vulnerability in uncaught exception messages * [CORE-798] - Order Plugin: Cannot add multiple addon services due to error that the parent service ID already exists as a child to another service * [CORE-799] - 2Checkout: Payment logo URL from 2Checkout is no longer valid * [CORE-801] - AppController:base_url does not contain port number, if given * [CORE-802] - Plesk: Canceling a service deletes all customers * [CORE-803] - Client payments without account set first name as last name * [CORE-804] - Support Manager: mailto link contains HTTP protocol * [CORE-805] - Namecheap: Domains not available ---

Try the attached (place in /components/gateways/merchant/stripe_gateway/). It should resolve the issue. stripe_gateway.php

Mainly, what you're probably looking for is /app/views/default/admin/default/structure.pdt and /app/views/default/client/default/structure.pdt.

This looks like a bug with the order plugin. Try editing line 83 of /plugins/order/controllers/main.php. From: "<link href=\"" . Router::makeURI(str_replace("index.php/", "", WEBDIR)) . $this->view->view_path . "views/" . $this->view->view . "/css/order.css\" rel=\"stylesheet\" type=\"text/css\" />" To: "<link href=\"" . Router::makeURI(str_replace("index.php/", "", WEBDIR) . $this->view->view_path) . "views/" . $this->view->view . "/css/order.css\" rel=\"stylesheet\" type=\"text/css\" />"