Context Navigation

Changes between Version 1 and Version 2 of Ticket #36335, comment 63

v1	v2
17	17	> > xrstf\Composer52\Generator::onPostInstallCmd
18	18	> }}}
19		This is one example of bad class design in a third-party library. A quick search seems to indicate that the fix for this would completely contained within that third-party library, by renaming the two classes, and changing line 906 in `wp-admin/includes/class.ftp.php`.
	19	This is one example of bad class design in a third-party library. A quick search seems to indicate that the fix for this would be completely contained within that third-party library, by renaming the two classes, and changing line 906 in `wp-admin/includes/class.ftp.php`.
20	20
21	21	> 6) I'm not sure yet how I feel about automatically making so much of wp-admin available on everypage load. In the past, core has forced developers to make a cognitive decision to include those pieces on the front end if they want to use them. Is that a change that should be made? why?