Jump to content

sunrisepro

Members
  • Posts

    201
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by sunrisepro

  1. Hey - I bought your template a couple of weeks ago but have not received the template nor gotten any response from you on installation.
  2. I don't know - that would prolly be a good Q for Ken.
  3. There have been no updates since the theme was made, I'm still running 3.4.3.
  4. It's definitely an issue with the custom theme - this time an old customer who has paid online before was unable to pay. See the attached screenshot.
  5. The error happened with a new customer. I sent them an invoice and the 'Pay now' link from the email resulted in the error (I tried myself on an incognito window & got the same error). I just put the theme back and will see if it happens again.
  6. It's something theme related because the issue was fixed when I went back to the Bootstrap theme. I take it my theme dev is no longer in business?
  7. whtheme.com is no longer in business? I had to switch back to the default Bootstrap theme after a new client got this error when trying to pay their first invoice: Attempt to modify property of non-object on line 173 in /home/username/public_html/blesta/app/views/client/sunrisepro/client_pay_method.pdt When I look at line 173 in the theme, it has this: <strong><?php echo $this->CurrencyFormat->format($this->Html->ifSet($total), $this->Html->ifSet($currency->code));?></strong> I've had old client pay invoices online with no problems in the last week.
  8. Yes it is, seems like 5.3 is the system default but options include 5.4/5.5/5.6/7.
  9. It's working after my host looked into it & provided a fix: I believe I managed to resolve the issue by changing the pipe email forwarder to the following: |/usr/local/php53/bin/php-cli /home/username/public_html/blesta/plugins/support_manager/pipe.php I sent a test email and so far I have not received a bounceback email. The issue was caused by the fact that the default PHP binary used when the email was piped did not have the mailparse PHP extension. The following PHP binary, however: /usr/local/php53/bin/php-cli does have the extension and now the email piping should work. I don't know how common this issue may be but maybe it's worth noting in your documentation?
  10. OK, let's see what my host says.
  11. Here's the new error in the returned mail: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: pipe to |/home/username/public_html/blesta/plugins/support_manager/pipe.php generated by support@mail.com local delivery failed The following text was generated during the delivery attempt: ------ pipe to |/home/username/public_html/blesta/plugins/support_manager/pipe.php generated by support@email.com ------ PHP Fatal error: Call to undefined function mailparse_msg_create() in /home/username/public_html/blesta/plugins/support_manager/vendors/mime_mail_parser/MimeMailParser.class.php on line 113 Fatal error: Call to undefined function mailparse_msg_create() in /home/username/public_html/blesta/plugins/support_manager/vendors/mime_mail_parser/MimeMailParser.class.php on line 113 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us" dir="ltr"> <head> <title>Blesta</title> <link rel="stylesheet" type="text/css" href="/home/username/public_html/blesta/plugins/support_manager/app/views/errors/css/styles.css" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> </head> <body> <div class="program_error"> <h3>Oh noes!</h3> <div class="contents"> <p>Call to undefined function mailparse_msg_create() on line <strong>113</strong> in <strong>/home/username/public_html/blesta/plugins/support_manager/vendors/mime_mail_parser/MimeMailParser.class.php</strong></p> </div> </div> </body> </html>PHP Fatal error: Uncaught exception 'UnknownException' with message 'Invalid callback Session::sessionWrite, cannot access private method Session::sessionWrite()' in Unknown:0 Stack trace: #0 [internal function]: UnknownException::setErrorHandler(2, 'Invalid callbac...', 'Unknown', 0, NULL) #1 {main} thrown in Unknown on line 0 Fatal error: Uncaught exception 'UnknownException' with message 'Invalid callback Session::sessionWrite, cannot access private method Session::sessionWrite()' in Unknown:0 Stack trace: #0 [internal function]: UnknownException::setErrorHandler(2, 'Invalid callbac...', 'Unknown', 0, NULL) #1 {main} thrown in Unknown on line 0 PHP Warning: Invalid callback Session::sessionClose, cannot access private method Session::sessionClose() in Unknown on line 0 Warning: Invalid callback Session::sessionClose, cannot access private method Session::sessionClose() in Unknown on line 0 Action: failed Final-Recipient: rfc822;|/home/username/public_html/blesta/plugins/support_manager/pipe.php Status: 5.0.0
  12. I'm confirming that Mailparse is active with my host..
  13. I don't have the time to enable & setup SSH access right now, and I have no idea what the 'CLI version of PHP' even means. Aside from SSH, what do you think is the problem?
  14. It was 744, just made it 755. Still not working: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: pipe to |/home/username/public_html/blesta/plugins/support_manager/pipe.php generated by support@email.com local delivery failed Action: failed Final-Recipient: rfc822;|/home/username/public_html/blesta/plugins/support_manager/pipe.php Status: 5.0.0
  15. OK, that worked. I have to note the loss of income in my records though. Question: how do I 'archive' a client?
  16. Here's the last error message: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: pipe to |/home/username/public_html/blesta/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1/ Action: failed Final-Recipient: rfc822;|/home/username/public_html/blesta/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1/ Status: 5.0.0
  17. Added by cpanel when I created the forwarder. I did remove the first slash from yours tho. Tried it again with the first slash & cpanel saved it as |/home/username/public_html/blesta/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1/
  18. I tried that - editing was not allowed due to the existing transaction.
  19. Nope - another email delivery error.
  20. That's usually the world we live in but it's not completely applicable for hourly based invoices & client disputes. Ideally the client would have disputed before paying, rather than paying and then disputing.
  21. When I made the new forwarder it became |/home/username/usr/local/bin/php /home/username/public_html/blesta/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1/ Is that right?
  22. Nope - here's the email error: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: pipe to |/home/username/public_html/blesta/plugins/support_manager/pipe.php generated by support@email.com local delivery failed Action: failed Final-Recipient: rfc822;|/home/username/public_html/blesta/plugins/support_manager/pipe.php Status: 5.0.0
×
×
  • Create New...