Menu Content

Support

> Forums, FAQs & Paid Support
Welcome, Guest
Username Password: Remember me

Cannot change text in invoice email
(1 viewing) (1) Guest
Support forum for customers who have purchased this product. Archive only, no new post can be added.

NOTE: This category has been locked. If you have purchased paid version, please, use our Support Ticket system instead. If you are using free edition, please see the Community Support section.

TOPIC: Cannot change text in invoice email

Cannot change text in invoice email 11 years, 4 months ago #40088

I have been using VM Invoice for sometime now and all has been working fine. However I have noticed that the text in the invoice email has reverted to the standard line "We are attaching an invoice for your purchase."

No matter how many times I change it, every time I click save it goes back to "We are attaching an invoice for your purchase."

How do I fix this?

Thanks Dave
The topic has been locked.

Re: Cannot change text in invoice email 11 years, 4 months ago #40090

I have the same problem. After push "save" command the form return to the default values.
The topic has been locked.

Re: Cannot change text in invoice email 11 years, 4 months ago #40091

I user joomla 2.5.11 and virtuemart 2.0.22 with php 5.3.26 on Apache/2.2
The topic has been locked.

Re: Cannot change text in invoice email 11 years, 4 months ago #40105

I have the same problem and apparently is with the new version 2.0.26 of VM Invoice. Help please.
The topic has been locked.

Re: Cannot change text in invoice email 11 years, 4 months ago #40112

Exactly the same for me since the new update, impossible to change the Invoice Email.

Please find us a solution.

Thank you.
The topic has been locked.

Re: Cannot change text in invoice email 11 years, 4 months ago #40116

Exactly the same issue here.

This error was found in the logs:
PHP Warning: trim() expects parameter 1 to be string, array given in /home/xxxxx/public_html/administrator/components/com_vminvoice/helpers/invoicehtml.php on line 447
The topic has been locked.
User Login Empty