Joomla Translate module support

Hi Admin,
Many Thanks to your suggestion I was able to understand that it is due for an Helix Ultimate / Solidres bug that I reported to their support here:

- github.com/JoomShaper/helix-ultimate/iss...uecomment-1407060480
- github.com/JoomShaper/helix-ultimate/iss...uecomment-1405329823

- www.solidres.com/forum/report-bugs/11876...ol-not-working#19615

(Waiting for a fix suggestion)

Looking for a solution I found this interesting article from Brian that maybe can be useful also to you for all what we discussed on last days:
gist.github.com/dgrammatiko/efb3de4aa7cab4813a244f93f73cc0fd

Hi Emiliano,

I admire your skill and determination. You must be logged into Joomla R&D.
Recently, Joomla has been going some where wrong.
And you could change it

>gist.github.com/dgrammatiko/efb3de4aa7cab4813a244f93f73cc0fd
Yes, this is very interesting code. But why can't I see this on joomla.org?
And it seems to me: it is best to use original libraries, without any "covers". Because as a result we need to know both APIs. And each "COVER" limits the original library and adds its own bugs.

about "helix-bootstrap" it seems to me: each component should move all the libraries it uses into its own namespace and add them to its software. (unless it's a very simple component). CMS collects a lot of software from many developers. And yes, the resulting CMS will be heavy and big. But as a result, we will have a lot of software with great opportunities for end users!
And it will work every time. And this software will be reliable and simple for the end user.


All developers have their own ideas about how things should look and work.
we see
- when clients can't find settings to enable/disable any library - they just don't want to check these settings. The program should work always and everywhere.
- when other developers remove all libraries from other developer - which they use it. To avoid conflicts with your own library
- when developers modify an external library for personal purposes. And others see the standard library but cannot use it.

Yes, it's great to have several popular libraries in Joomla core. But all developers want more features, and they ask for extended libraries. As a result: Joomla doesn't use "popular libraries" because they have a very simple and lightweight interface and others can't use them - because they don't give them all the features they need.

Joomla should be simpler and not change its API every time. After each such change, Joomla lost developers, lost software and lost customers.

Regards
Andrew
OrdaSoft team

Hi Andrew,
thank you for your answer and sure I understand you.

"...Joomla should be simpler and not change its API every time..." = I'm agree. Let's look at the positives: it seems that for Joomla 5 there won't be any changes of this type

"...After each such change, Joomla lost developers, lost software and lost customers..." = I have actually noticed some changes. I hope the Joomla team can take note of that to improve in the near future...

- Joomla 1.5 was popular
- Then the Joomla team decided to create a new great product and killed the joomla core and the joomla.org interface - and lost a lot of customers and developers .... But created joomla 2.5
- Then Joomla 3 was created - errors from the previous update were not repeated
- Next Joomla 4 - all experience after Joomla 1.5 is moved to the trash - along with popularity and reliability

I'm sorry maybe I'm wrong

Sincerely
Andrew

Hi Andrew,
unfortunately you are not wrong, that is what happened...

joomleb wrote:
Hi Admin,
Many Thanks to your suggestion I was able to understand that it is due for an Helix Ultimate / Solidres bug that I reported to their support here:

- github.com/JoomShaper/helix-ultimate/iss...uecomment-1407060480
- github.com/JoomShaper/helix-ultimate/iss...uecomment-1405329823

- www.solidres.com/forum/report-bugs/11876...ol-not-working#19615

(Waiting for a fix suggestion)...

All is well that ends well: Helix Ultimate 2.0.12 has been released. I Tested it and the Bug seems has been fixed with success...