-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken table layout when reporting WordPress vulnerabilities. #134
Comments
@oscarssanchez This issue was fixed, however we couldn't fixed it in a general way without breaking backwards-compat. That's why you need to use the second argument to If you pass all of your columns through If you pass only select columns through So, for example, if you have 4 columns and only the first one is passed through Please let me know if that helps resolve the issue. |
@schlessera The new function to display a table seems to now be
|
@schlessera I encountered the same issue as @UVLabs and would like to know if there is a solution or a workaround. |
@UVLabs @alexisferat $table = new \cli\Table();
$ascii = new \cli\table\Ascii( [
Colors::width( 'value 1', true ),
Colors::width( 'value 2', false ),
Colors::width( 'value 3', false )
] );
$ascii->setWidths( $widths );
$table->setRenderer( $ascii );
$table->setHeaders( [ 'module', 'key', 'status' ] );
$table->addRows( [ $rows ] );
$table->display(); |
Hi,
Running wp vuln status through WordPress 4.9.6 breaks the table layout when the package reports any vulnerabilities with WordPress version (not plugins, not themes. See screenshots).
Expected behavior:
Table layout is not broken. Expected to see the same layout as it is with the reports of plugins and themes.
Current behavior:
The table layout breaks.
Steps to reproduce:
Run wp-vulnerability scanner through a WordPress 4.9.6 install
1.- wp vuln status
WP-CLI version: 2.0.0-alpha-2646dac
Screenshots:
Layout broken when reporting problems with WordPress 4.9.6:
Layout is fine when reporting no vulnerabilities with WordPress 4.9.7
It seems like it has been a recurring issue (#106)
Thank you!
The text was updated successfully, but these errors were encountered: