Hello.
There is an issue when using HikaShop on a Joomla 4 website that uses the Yootheme Pro template.
I have been going through the support forums for both Yootheme and HikaShop, in an effort to find a solution to this issue. Unfortunately, both HikaShop and Yootheme are saying that the issue people are having is the other organization’s fault. This doesn’t help anyone, and those of us that are having this issue need HikaShop and Yootheme to work together on a solution.
Here are the facts of the issue.
- This occurs on Joomla 4 and is typically found when someone migrates from Joomla 3 to Joomla 4.
- The website needs to use HikaShop, Yootheme Pro template, have the HikaShop Cart module displayed, and Joomla caching needs to be turned on.
- When all of this is done, which is a very normal setup, you will get “1 blog”, “1 post”, “blog”, or “post” appearing in the upper left corner of the website in a narrow white section on the top of pages.
- That immediately goes away if you unpublished the HikaShop Cart module, or turn off the Joomla caching.
- It only appears when using the Yootheme Pro template, and I have verified that by trying other templates.
Granted this is not an issue that is breaking the functionality of the websites that have the issues, but it looks bad and we should not have to live with it.
I personally have 4 live websites that currently have this issue, and another 2 that will be migrated within the next 2 weeks. Plus I have another 5 websites that will be migrated to Joomla 4 in the next 4-6 weeks that will have this issue as well. That will be 9 websites for me with this issue.
In looking at the forums on both Yootheme and HikaShop I can easily see that I am not alone in this as others are reporting the same issue. Neither HikaShop or Yootheme are offering a fix for this as both organizations are saying the issue is the fault of the other.
This doesn’t help anyone.
I am calling for both Hikashop and Yootheme to come together and work on a fix and to stop pointing fingers at the other organization. This issue obviously needs to be solved by both of you, even if in the end the code of just one system needs to be changed.
I am posting this on both support forums in the hope that it will help move forward a solution for this problem.
If you have a website that has this issue please post a reply to this post stating that you do have the issue as well. If we can all come together, maybe we all can work to resolve this.
Thank you.