HikaShop - Transactional Emails, Market: Vendor Registration

-- HikaShop version -- : 6.4.1
-- HikaMarket version -- : 6.1.0
-- Joomla version -- : 5.4.3

Hello

I'm still validating transactional emails, specifically regarding HikaMarket, Market: Vendor Registration.

I've registered a new seller in the e-commerce platform and I can see that messages are being sent to both the e-commerce administrator's email account and the registered seller's email account.

The problem is the email template used to create them. I've configured a custom email template, which I use for all transactional emails. However, in this particular email, I can't see the preview; it's not working. Most importantly, the emails are reaching recipients using Hika's default template instead of my custom one.

Where can I check to correct this error?

Thanks!

Hello,

What is a "transactional email" for you ?

Please note that HikaMarket emails are using different templates from HikaShop ; the emails are not handle by the same "component", they are not stored in the same folder.
So when you're talking about "hika's default template" ; you need to be more precise.. HikaSHOP or HikaMARKET ?

Regards,

Hello

I understand, sorry for not being clear, I'm learning about these components as I go.

Regarding what I call transactional emails, these are all the emails sent by Hikashop/HikaMarket for the operation of the e-commerce platform: registration, order status changes, sales, stock shortages, communication between buyers and sellers, etc. Perhaps I'm using too broad a term, and for you, transactional emails might be a different concept.

Regarding the question about the emails, it's more or less as I mentioned: a new seller registered on the e-commerce platform (I assume this mainly involves HikaMarket). In practice, I see that two emails arrive: one to the seller who registered and another to the e-commerce admin. I understand that this is the email I highlighted in the screenshot, which is in the list of available emails in the HikaMarket settings.

Specifically, when editing that email, I can select an email template from the existing ones or a custom one. I've attached a screenshot of that setting. However, the problem is that even though I configure my custom email template, the messages arrive to the recipients with a different template than the one I created.

I hope that clarifies things. Thanks!

Hello,

Thank you for the clarification even if I'm missing an important point to fully understand the situation:

So when you're talking about "hika's default template" ; you need to be more precise.. HikaSHOP or HikaMARKET ?

I still don't know what is your final result ; what template is being used for hikamarket emails...

So, I will take a hypothesis that it's HikaMarket default email template (the green one).
Nevertheless, I've send a message to Nicolas in order to clarify how template should work with other components.

HikaMarket has the emails stored in the "media/com_hikamarket/mail/" folder and it provides also few templates.
Best is that you copy your template from "media/com_hikashop/mail/template/" into the HikaMarket one (and provide another name so it will be display correctly in the list).

By doing that, I think the customization should work.
In the meantime, I'll see how HikaShop and HikaMarket could share templates for their mails.

Regards,

Hello,

Well, it is very difficult for me to follow your instructions.

The screenshot I sent you is how the email arrives to the vendor after registration: "email-Market Vendor registration.png". I cannot tell you the template name because I do not select it manually, it just uses that one automatically.

On the other hand, I tried to follow your instructions in different ways and create copies of the existing templates:

1 - Via FTP, I copied the template that works correctly for other emails, "custom_new_abierto.html.modified.php", located in the path "/media/com_hikashop/mail/template". I renamed it to "vendedores_abierto.html.modified.php" and saved it in the path "/media/com_hikamarket/mail/template". Then I logged into the site admin -> HikaMarket configuration -> Main tab -> Email options -> E-mail Market: Vendor registration. I edited it and searched for the template recently created via FTP in order to select it, but it does not exist there, apparently it is not being recognized.

2 - I accessed the same screen, site admin -> HikaMarket configuration -> Main tab -> Email options -> E-mail Market: Vendor registration. I edited the email and pressed the + button to create a new template. The template was created without any problem, but if I check via FTP, the new template is created in the path "/media/com_hikashop/mail/template".

3 - I tried to modify an existing template named "vendor.html.php".

In every case, I registered a new vendor, and in all cases the result was negative. The email always arrives using the default template, the green one.

I do not know what other tests I can perform, but I am not managing to improve this.

I look forward to your comments, thank you!

Hello,

By default, the setting "market.vendor_registration.template" is "vendor_market".
So the default template would be "vendor_market.php" and not "vendor.php".

I checked the HikaMarket code and it loads the HikaShop mail class, ask it to get the email "market.vendor_registration" and send it.
All the settings for the email are in the HikaShop configuration table and the template should be retrieve in either HikaShop and HikaMarket folders (hikamarket ask to add its folder in the lookup).

Please note that ".modified.php" files are for overrides ; they can't "exists" for HikaShop if there is no email with the same name (without the ".modified").

Regards,

Hello

I think I have found part of the problem; if I associate any template with the email "Market: Vendor registration", such as "vendor_market.php", "vendor.php", or a custom template created by me, it always uses a default template with a green header and footer. As a result, the message arrives to the user with the header and footer duplicated, as shown in the screenshot.

However, if I select "none" in the template select box, meaning no template at all (see screenshots), the message arrives to the user with a green header and a green footer. This means that the green header and footer are defined directly in the mail View Builder.

My understanding is that, besides the fact that the email always uses the same template regardless of which one is selected — which seems to be a bug — I could work around it by writing my customization directly in the mail View Builder.

If you would like to review the issue that would be great, because other emails might have the same problem. Please let me know your thoughts about it.


Thank you very much!

Hello,

Regarding your second screenshot, yes, it looks like you have an email with an incorporated template.
But the email by default does not include the template ; you might have an email override.

Since you're using HikaMarket 6.1.0, the email content (HTML part) should start with :
Regards,

Hello,

As you mentioned, the email had a customization that I removed, but the problem persists. It's not possible to create a custom template that works with this email.

On the other hand, I insist that it is not possible to create a custom template and make it work with this email.

I have tried uploading via FTP a file named "vendor.html.modified.php" into the directory "/media/com_hikamarket/mail/template", but even if I upload 10 files, the interface only shows the 3 original ones.

Also, from the interface itself, I edit a template, make changes, and save it with the same name, for example "vendor". The result is that a modified file named "vendor.html.modified.php" is saved into the directory "/media/com_hikashop/mail/template", and it does not appear in the interface so that it can be selected.

Everything seems to indicate that there is some kind of internal bug where certain templates and working directories are hardcoded for HikaMarket.

I could replace the code of one of the existing templates via FTP with my own code — I tested it and it works — but when I install a component update, I will lose my customization, so it is only a partial solution.

I am really not finding a long-term solution. I need your help with this, since this is not the only email affected by this kind of issue.

Thank you!

Hello,

There is no hard coded templates in HikaMarket.
You can take a look at the plugin "hikashop/market" and see the function "onMailTemplateListing".
You should be able to create tempaltes in HikaShop and use them for any kind of email.
The issue you describe is not an HikaMarket issue ; but it's related to the HikaShop core.

Please note that if you create an override for a template, it won't be listed in the interface, only "templates" are listed, the override system is there to let you customize a file and not loose your modifications with updates ; the fact that an override is not listed is absolutely normal.
But you should be able to create new templates (without ".modified" ; it's a new template, not an override of a template which does not exist) and use it in HikaShop (all emails, even HikaMarket).
If it's not the case, please open a new thread for HikaShop.

Regards,

Hello,

I understand perfectly what you are explaining, and I confirm it, I believe I have mentioned it more than once throughout this thread, of course I can create custom email templates from the interface for HikaShop emails. For example, I use them to notify the customer about new orders, when an order status changes, when a user registers, to notify the administrator, etc.

However, the specific issue is with HikaMarket emails, such as the vendor registration email sent to the vendor, the new order notification email sent to the vendor, etc. No matter if I assign my custom template to them, it is never used. It only recognizes the three templates that come predefined with HikaMarket: "vendor", "vendor_black", and "vendor_market".

I know that the language barrier may make it difficult for me to explain this better, but please believe me that I have tried everything you suggested, and even more, but it does not work the way you describe.

I will open another ticket to report it, if you think it is necessary.

Thank you!