Leaderboard

I am not sure the best section for this, but Michael thought here would be best. This may or may not be an issue I just got an email from paypal that they are making changes. here is the email I received. ACTION MAY BE REQUIRED: PayPal service upgrades for merchants. Because we support our merchants in helping them grow their business, we continue to make significant investments and improvements to our infrastructure. These improvements sometimes require us to perform necessary service upgrades. Please read below as we explain what the change is, and what action may be required by you.* What’s happening? Over the course of 2015 and 2016, PayPal will be working towards upgrading various SSL certificates. The changes include upgrading the following: The version of the VeriSign Trusted Root Certificate used to establish secure connections to PayPal. The signing algorithm of certificates (from SHA-1 to SHA-256). Why is this happening? We’re taking measures to address industry-wide security concerns which aren’t unique to PayPal. When implemented, these measures can help us improve the security and reliability of our PayPal integrations and help guard against current and future security threats. When is this happening? We’ve published the schedule of our service upgrade plan. Please check our 2015-2016 SSL Certificate Change microsite for the most recent updates as published schedules may change. Our efforts to upgrade SSL certificates for our production endpoints are scheduled to start in May 2015, and will continue into next year. Please note – The Sandbox environment is ready for testing. Testing in the Sandbox environment is one of the best ways to make sure your integration works. What do I need to do? For information regarding the important details of these upgrades, how it may impact your integration, and what you must do to future-proof your integration, please refer to the Merchant Security System Upgrade Guide on the microsite. *Please note – If you’re impacted by this upgrade, you may be required to implement these changes prior to the dates listed on the microsite. Otherwise, you may not be able to process payments through your current integration with PayPal. In addition, if you’re integrated with a third party, please check with them on any additional steps you may need to take. Questions can be directed to our Merchant Technical Services team on our Technical Support website. Click here for more information. Thanks for your patience as we continue to improve our services.

Your server just needs to be able to connect to PayPal's API with their upgraded SSL. If your server doesn't accept their certificate, or understand SHA-256 signed certs, then it will not work. Unless your server is old, it should work fine.

@PaulV , i think cody ask about the due date and not the invoice date , and her question is clear , is the same issue as @phamhung has . sometimes the due date will be earlier than the invoice date . @Cody , i have asked about this subject , the answer was no probleme , because the due date can also be referrel to the proforma , and in most case the due date is not needed to be mentioned if the invoice is paid fully , as is not a legal element that the invoice should have , as the date and the number and other info . but i preffer listen to more EU customers about this subject .

Thanks for the clarification

My guess is there was whitespace in the username somewhere, which you failed to enter during the login attempt. Blesta doesn't care if you use numbers, letters, symbols, or any combinations of those.

I wouldn't suggest putting much effort in modifying the admin interface. Since it sees so much activity each release, it will be a pain to keep up to date.

Don't do an addon package....! Make an order form... Make it Domain and Other. Select the Domain group via the dropdown box. Then select the hosting packages... That's all you have to do.

You can record a payment on their profile page and then select the method, then enter the value of the payment, and then select the invoice and save . Eg:

Use the "Record Payment" option in Blesta under their client profile page. Record Payment is under Actions. Also, you can get there by clicking Pay next to the invoice, then record payment instead.

Blesta is transparent about encryption and what algorithms are used. You will always be able to decrypt your data, with the exception of hashed data, like passwords which are bcrypted HMAC-SHA-256 hashes and are not reversible, even by Blesta. So yes, you can get your data out.

even if you use the var innodb_file_per_table = 1 i have though this var can avoid this situation , because every database in a separate file .