I assume the subject of this thread is a typo, as 1.15.0 is the most recent PHPLIB release.
I followed up on all of the issues raised in PHPLIB-1055 but I’ll address some other points below.
In fact, PHP library references are completely removed from this seminal “connect to your cluster” tutorial. Only access options described are for: PyMongo Driver, Node.js Driver, MongoDB Shell, and Compass.
This wasn’t mentioned in PHPLIB-1055, so I’ll field this here.
For language-specific examples within other product manuals (e.g. Atlas, MongoDB server), drivers teams generally get a produce example code, which then gets added to our test suite (for ongoing test coverage) and parsed by other teams to incorporate into their own docs. One example of this is PHPLIB-350 and the DocumentationExamplesTest.php file in the PHPLIB repository.
I’m not familiar with that page but it appears to be maintained by the Atlas team. I don’t recall ever seeing a ticket related to the Atlas connection examples you referenced above, but I’ll follow up internally with that team to ask why only a subset of drivers are included (PHP is not the only one missing).
There are several other deprecated references in Atlas start-up guide and tutorials for use of PHP library.
I assume this is referring to something other than the missing connection examples above. Can you share references to these docs pages so I can look into this further?
Documentation issues can be reported here.
Slight correction. Most MongoDB manual pages should have a “Share Feedback” widget in the bottom right corner. If so, that’s the preferred way to report documentation issues since it will spawn a JIRA ticket with the correct template and context (also without requiring the user to have a JIRA account). In the absence of that, creating a DOCS ticket directly will still get the attention of the right people and can be triaged or moved to other teams as needed.
PHP driver docs are handled entirely by the driver engineers, so reporting issues directly in either the PHPLIB or PHPC (for extension docs on PHP.net) is preferable.
In @G_Chase’s case, one of the issues pertained to code examples within the Atlas UI itself. Since that’s a separate team, I created an internal ticket for them to look into that and cross-referenced it with PHPLIB-1055 for context.