I find that some PHP Frameworks are quite good
Methinks we have a different definiton of "good", but some of your points do have merit. (which is more than I can say for most pro-framework arguments).
Better documentation than the language they are for is often fact, but In PHP's case I'm highly skeptical as php.net is one of the BEST language references I've ever come across. Things only seem to go pear shaped when people ignore it, or fail to keep up with the version changelogs.
I don't tend to find forums relating to frameworks useful, as more often than not they're echo chambers for the bad practices that resulted in a framework being built in the first place. When the concept of the framework itself came from an ignorance of the underlying language, the forums, "experts", advice, and "special libraries" are all doing nothing more than continuing that particular flavor of derp. When the foundation is cracked and insecure, rip it out instead of building something new on top of it.
When it comes to security updates, when everything ends up built upon dependency hell, where this library relies on this framework that was built with this tool with ZERO understanding of how any of it works, applying updates becomes a nightmare and a half. See the pinnacle of such stupidity and fragility: NPM.
Whilst the PHP ones aren't as bad as client side HTML/CSS/JS, or server side node.js, they still come into being either out of misplaced laziness stemming "wah wah, I dunz wunnu lurn", or an attempt to shoe-horn in programming models and structures that have ZERO business in PHP in the first place.
So many of those "common structures" are illogical, bad practice, or just plain ignorant of what PHP is and how it works. Take MVC. It's a GREAT programming model if I'm writing event driven low level code for motor control in C++ under QNX. It is an utter mismatch of task complexity when it comes to doing anything in PHP.
I appluad the idea of separation of concerns MVC brings to the table, but they do not even come close to lining up to the non-event driven input > process > output model that is the heart of how/when PHP is called. This is why every blasted MVC framework for PHP feels like stuffing a cows size 19 hoof into a ladies size 5. A ferrier is gonna look at you like you're out of your mind.
It's not a bad concept, it just draws the lines in the wrong places, and as such results in hard to follow, hard to maintain, bloated slow code. MVC in PHP is false simplicity in the form of task complexity mismatch.
... and it seems to go like that for every framework I've ever had to deal with. It's all bloated nonsense you have to learn on top of the underlying language, that results in more complex, more cryptic, and harder to maintain code. It sure as shine-ola doesn't make collaboration any easier.
Well, unless everyone working on a project has ZERO blasted business working on the project in the first place, and are just blindly plagiarizing others without the slightest understanding of how anything works.
As @Gary-SC described said folks on DigitalPoint, frauds. We have way too much "fake it until you make it" going on in this industry.