Lots of them! LOL
In all of the tracks, the high level examples don't match the details of the low-level examples.
Mostly, in one track of the docs (i.e. How To Create A module)
https://docs.joomla.org/J3.x:Creating_a ... sic_Module
The basic inline documentation shows one thing and then the details show another.
As an example (using the above link to the docs), scroll down to the section titled "Creating mod_helloworld.xml" and you see that code. Then click on the "manifest files" explainer link and it tells you the version element you just saw is no longer valid.
This same inconsistency is found throughout every aspect of the developer documentation.
When reading the updater docs, it should very clearly say "if this doesn't match, this won't happen!"
More importantly, to the entire joomla project, if you rebuild the updater links, why is it not showing something as checked out and if it's not checked out, what is the check-in resetting that people should know about?
In all of the tracks, the high level examples don't match the details of the low-level examples.
Mostly, in one track of the docs (i.e. How To Create A module)
https://docs.joomla.org/J3.x:Creating_a ... sic_Module
The basic inline documentation shows one thing and then the details show another.
As an example (using the above link to the docs), scroll down to the section titled "Creating mod_helloworld.xml" and you see that code. Then click on the "manifest files" explainer link and it tells you the version element you just saw is no longer valid.
This same inconsistency is found throughout every aspect of the developer documentation.
When reading the updater docs, it should very clearly say "if this doesn't match, this won't happen!"
More importantly, to the entire joomla project, if you rebuild the updater links, why is it not showing something as checked out and if it's not checked out, what is the check-in resetting that people should know about?
Statistics: Posted by ppetree — Wed Jun 12, 2024 8:08 pm