Leaderboard

Awesome! Awesome! I believe it is a time issue. The revenue is correct, just not for the time period you expect. We need to investigate a bit more.

The install.php file can't be used to mess anything up. If it could, we'd require removing it. I think you're just used to other applications that require you to do that. Blesta is smarter than those applications.

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 ---

For 2.5, look in order_forms/register_client/templates/ (If you're using the register order type) and look at step1.pdt and structure.pdt. You will notice the form fields exist here, and you can pre-populate them from your session variables. I'm assuming you were the one I talked to over the phone?

Does anything show up in the module log? Tools > Logs > Module. If the email address entered into the gateway in Blesta doesn't match that from which PayPal is including in their IPN call, it won't be credited. Some people have multiple aliases, and we have a task so that these aliases can be added to the gateway and be accepted as well. (CORE-697) I found a task, CORE-662, that resolved an issue with an error being displayed within Blesta when returning from PayPal. This was solved in 3.0.1. However, this may be a matter of the user clicking the return link, which is mentioned in this case, and an automatic redirect. This may require another look. I agree, the user shouldn't be able to edit the item. I have assigned this to CORE-809.

Ah now I get it. I was missing that extra encapsulation array. Thanks for the timely response. Rock on.

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].

Virtualizor is assigned to task CORE-419 and tentatively assigned to 3.2. It's possible it could be pushed back beyond this depending on need and workload for 3.2.

Hmm.. You might could use a php if statement in the mean time. if company_id==1 then .... else .... and have two different scripts from google for the two sites.

So its actually really easy to set it up already. Just add the script google analytics gives you at the bottom of the structure.pdt for whatever company you want to track.

I haven't upgraded yet but I wanted to say I really like how you layed out the security fixes. The fact that you mentioned their were potential security issues and the fact you fixed them. Well done!

This made me LOL A feature to set the number will be in a future release. For now, this should work for changing it after the 1st one has been created. Cody or Tyson may have a better suggestion, though.

Thanks for the suggestion.. If I'm remembering correctly, you suggested this early on. Definitely needed!

Blesta 2.5 would use the auto-incrementing client id from the database as the client id. v3 uses clients.id_value and clients.id_format. This isn't yet customizable in the interface, so you may be able to make a change in the database. BACK UP EVERYTHING FIRST Look for the client where id_value is the largest, and change it. If you want the next client to have an ID of 12345, set it to 12344. Then, create a new client. Then, change the id_value back that you changed to 12344. If you want to include other characters in the client id, you can as well. For example.. HOST-12345 USER-12345-CO abc-12345 12345-xyz To do that, look in company_settings for the key clients_format and change the value. Be sure to include {key} in your string, someplace. Again, make sure you back up everything first. I'm not 100% sure the first thing I mentioned will work as intended.

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

This is fixed in v3.0.4.

Fixed in CORE-805 for v3.0.4 of Blesta.

This is assigned to CORE-628 and is a blocker for 3.1. Packages will be drag-n-drop sortable within their groups. ie, under Packages > Groups, click a group, and drag-n-drop the packages within the expandable area. A similar method for sorting configurable options will be in 3.1 as well.