Leaderboard

SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '2014-03-13T19:31:57+00:00' for column 'date_closed' at row 1 on line 124 in/home/billing/public_html/lib/model.php #0 /home/billing/public_html/lib/model.php(124): PDOStatement->execute(Array) #1 /home/billing/public_html/components/record/record.php(233): Model->query('UPDATE `support...', Array) #2 /home/billing/public_html/plugins/support_manager/models/support_manager_tickets.php(100): Record->update('support_tickets', Array, Array) #3 /home/billing/public_html/plugins/support_manager/models/support_manager_tickets.php(269): SupportManagerTickets->edit('46', Array) #4 /home/billing/public_html/plugins/support_manager/controllers/admin_tickets.php(289): SupportManagerTickets->addReply('46', Array, Array) #5 /home/billing/public_html/lib/dispatcher.php(111): AdminTickets->reply() #6 /home/billing/public_html/index.php(21): Dispatcher::dispatch('/admin/plugin/s...') #7 {main} Getting this error upon closing a ticket. Not had this error before.

Yes, and they actually use it.

Blesta wouldn't be overriding any of your webserver logs, no. Blank pages can occur for any of several reasons, including a php error or 500 internal server error. You can enable error reporting in Blesta by updating /config/blesta.php (line 11) from: Configure::errorReporting(0); to Configure::errorReporting(-1); And then see if that blank page displays any errors.

We were calling this service price override, and it's assigned to CORE-747 scheduled for 3.3. This one is becoming a big priority for us.

My recommendation is to start local. Friends, family, local businesses. Treat them well and they will tell other people. Do not underestimate word of mouth. You won't see results overnight, but you're building a lasting business, right? People like to do business with those they feel like they can trust, and people trust their friends advice far more than a Google ad (Don't advertise on Google).

It's unresolved, but it's currently a blocker for 3.2. I discussed this one with Cody last week, and he seemed confident that it wouldn't take much time to implement and that it is likely to be included in 3.2. This is assigned to CORE-852 and can be tracked there.

Selling Blesta Owned Branded license for 150 USD 140 USD (edit, see below) via PayPal. + This includes 1 developer license. Ownership of the license can be verified with Blesta staff. Please PM me if interested or just reply here and I will contact you.

I thought we were keeping the thread fresh. Come to think of it, this is in the wrong forum. </closed>

Version 3.0.7 is now available. You can download it in the Client Area. 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.7 ## Version 3.0.7 2013-12-20 ### Bug * [CORE-873] - Favicon missing * [CORE-877] - Security: Support Manager: XSS vulnerability in support manager * [CORE-882] - Line item setup fees do not observe setup fee tax setting * [CORE-887] - Updating a package to change a module group back to Any does not save this change * [CORE-888] - Contacts::add/edit rule validation should ensure only one 'primary' type per client_id * [CORE-890] - Universal Module: Fields fail to validate when pending services approved via cron. * [CORE-897] - Autodebit may reattempt same invoice in same day if payment failed * [CORE-906] - AmazonS3 Backup fails with period (.) in bucket name * [CORE-907] - Client numbers fail to increment when clients_start is greater than current max number * [CORE-915] - 2Checkout: Fails to approve live transactions * [CORE-919] - Root web directory replacement not case-insensitive * [CORE-920] - PayPal: Validate should check either business or receiver_email for match on account * [CORE-921] - Report Manager does not exit after streaming file data for download * [CORE-927] - Client contact numbers appear on the same line in the client interface * [CORE-931] - Security: XSS vulnerability in client payment process * [CORE-932] - Security: Potential XSS vulnerabilities in use of Html::concat() * [CORE-933] - Backup settings incorrectly set messages * [CORE-934] - PHPIDS: Blank minimum impact rating is treated as zero instead of disabling action * [CORE-938] - Services::setFields may cause deadlock * [CORE-940] - Client setting for auto suspension does not disable auto suspension ### Task * [CORE-879] - Exchange rates through Google Finance no longer working ---