Hey Chris,
I honestly think the Joomla developers have pushed themselves a bit too far into a corner with all these constant architectural changes in the CMS. Many extension developers are basically hitting their heads against the wall trying to constantly adapt to new APIs, namespaces, and internal rewrites.
I am of the opinion that yes these architectural changes are a PITA but needed. We really had to come out of the Joomla 3 architecture and move to the Joomla 6 architecture and the pain isn't over yet. However the full use of namespaces and the DI container really does make it better for developers in the long run. To me it is just part of the job. As for now, you don't even have to change your codebase all that much to run on Joomla 6. So developers have years and years to update, so I don't see the problem. You can do it at your own pace. Heck, every so many years I revise the complete codebase anyways.
The funny thing is that there is now always the option to go back to the proven Joomla 3
Oh gosh, I saw that come by as well. Why? Is keeping a J3 fork easier than updating your extension
I’ve got good news for you — you don’t need to change anything in your file.
I like good news
The problem only occurs on Joomla! 5.3.x.
Hmm, I did test it on 5.3.3 and could not replicate it.
Of course, for older Joomla versions, it’s still worth using this fix as a workaround.
Yes, I am keeping the is_dir now because it is good enough for what it needs to do.
To be fair, our solution is probably even better anyway, because it simply works consistently regardless of the Joomla version. ?
Exactly.
Kind regards,
RolandD
=========================
If you use our extensions, please post a rating and a review at the
Joomla! Extension Directory