I have a question about how I can make packages with different languages. Since my site handles languages such as English and Spanish. I have a package that is in Spanish but when I make the package in English and instead of when I click the flag to change the language does not show me the package if I do not know that it goes directly to the main page of the packages and I do not want that. I want it to be done in such a way as it is done with joomla articles that when I am reading an article in English and I click the flag to change it in Spanish I show the associated arithmetic but apparently in the SPBOOKING component can not be created menu links to a package so you can associate it with your other language counterpart. How can I make package associations with different languages?
SP Booking doubt about mulitidioma packages
15 replies
Hello Guadalupe Amador Beltrán
Apology for the inconvenience. Please share your administrator access here to check the issue. Use the Hidden Content box to share the credentials. Make sure that you have a full site backup with you before sharing.
Best regards
I send you the link and access data. You can also see a video of the problem in the following post on facebook
Please take a full site backup with Akeeba Backup in ZIP format and share here. Follow this tutorial. I will share it with the developer team. I have shared your issue and they have asked for it.
The backup link is in the hidden section
I have shared it with the team. They will work on it.
Any progress on the reported problem?
It is under development. It will be fixed on the next update.
What is the release date of the component update?
Unfortunately, it will be delayed. It will take months to be honest.
Any progress information for the solution to the problem reported from the component?
Sorry, no update is scheduled yet.
Hello. Have you fixed the behavior problem that |if you change language sends you to another page and not to the other language version of the same package that you are viewing?
Sorry, it has not been fixed yet. It will checked on the next release. Unfortunately, I do not have any estimated date to share.
Any progress information for the solution to the problem reported from the component?
Apology! It is still not fixed. I have asked the team to give priority on this topic.