AbanteCart Community
Shopping Cart Operations => Support => General Support => Topic started by: jaysbar on September 02, 2016, 11:56:10 AM
-
Hi
When I checkout and the order has been processed, how can I change the default message and why do I get the "text_message_account" message?
Your Order Has Been Processed!
text_message_account
Continue
Thanks
Jay
-
Where do you see an error?
Did you change anything in your template? Say in the head.tpl or header.tpl.
Looks like you have 2 issues here.
1. Your font awesome is not working correctly on this page.
2. Language definition for this page is not loaded correctly or missing completely.
-
Hi
I see this error after I have checked out.
1. I have a basket full of goods
2. I choose PayPal checkout
3. I make the payment
4. PayPal redirects me to my Abantecart site
5. I see a message stating that my 'order has been processed' but I also see "
text_message_account"
Any ideas where I should look? I don't recall chaning anything in header and head .tpl .
My View Source looks like this:
<div id="maincontainer">
<div class="container-fluid">
<div class="col-md-12 col-xs-12 mt20">
<div class="">
<h1 class="heading1">
<span class="maintext"><i class="fa fa-thumbs-up"></i> Your Order Has Been Processed!</span>
<span class="subtext"></span>
</h1>
<div class="contentpanel">
<section class="mb40">
<h4 class="hidden"> </h4>
<p>text_message_account</p>
-
First check that text_message_account language definition exists in Admin in section checkout/success of storefront.
This is coming from file /storefront/language/english/checkout/success.xml
Do you use English language?
-
Hi
In Admin, I done "Search Entire Site" for "text_message_account". No results match.
Yes, I am using English as my language.
What should I do to fix the issue?
Thanks
Jay
-
Hello.
Please search forum ;)
this issue is very easy to fix http://forum.abantecart.com/index.php/topic,4914.msg21341.html#msg21341
-
Basara
Thank you buddy! This has resolved my problem. Hopefully it will be fixed in 1.2.9 :)
Jay
-
Hi, Jay
This issue is not present in 1.2.8 clean install, you see it because you upgrade your store from 1.2.7