Unexpected HTML output when updating WordPress #191

rodrigoprimo · 2014-11-17T16:58:47Z

If I update WP using wp core update I get a lot of unexpected HTML output coming from WordPress itself:

$ wp core update
Updating to version 4.0 (pt_BR)...
Descompactando a atualização...
<p>Algumas traduções precisam de atualização. Descanse por mais alguns segundos, enquanto atualizamos elas também.</p>
<div class="update-messages lp-show-latest"><h4>Atualizando traduções de WordPress (pt_BR)&#8230;</h4><p>Fazendo download da tradução de <span class="code">(http://downloads.wordpress.org/translation/core/4.0/pt_BR.zip)</span>&#8230;</p>
<p>Descompactando a atualização&#8230;</p>
<p>Instalando a versão mais recente&#8230;</p>
<p>Tradução atualizada com sucesso.</p>
</div><script type="text/javascript">
                (function( wp ) {
                    if ( wp && wp.updates.decrementCount ) {
                        wp.updates.decrementCount( "translation" );
                    }
                })( window.wp );
            </script></div></div>Success: WordPress updated successfully.

This output is coming from the new WP code to automatically update translations when updating core.

It seems that WP_CLI\UpgraderSkin is not being used in this context because the static method Language_Pack_Upgrader::async_upgrade() instantiate Language_Pack_Upgrader class with a hard coded skin. I guess we will have to open a new ticket on core. I decided to open an issue here first in case anyone has another idea on how to fix this.

The text was updated successfully, but these errors were encountered:

danielbachhuber · 2014-11-18T00:10:57Z

I guess we will have to open a new ticket on core.

Please link the ticket here when you open it.

rodrigoprimo · 2014-11-25T12:03:05Z

https://core.trac.wordpress.org/ticket/30497

danielbachhuber · 2016-08-17T13:24:40Z

@rodrigoprimo Can you provide a reproducible test case for this? I'm not sure whether it's still a bug, as I can't reproduce locally.

rodrigoprimo · 2016-08-17T20:29:08Z

@danielbachhuber I'm not able to reproduce this anymore so I guess it was fixed somehow. Closing the issue. Thanks.

danielbachhuber · 2016-08-17T20:55:49Z

@rodrigoprimo 👍 thanks

ernilambar · 2016-08-18T11:02:42Z

I got similar output when I upgraded from 4.5.3 to 4.6. I ignored it thinking some language update issue. Hindi language was activated in my system. May be it appears in update in language other than default English.

rodrigoprimo · 2016-08-18T16:54:42Z

@ernilambar I was testing with Brazilian Portuguese activated on my WP. Are you able to reproduce this issue again? Maybe it is necessary to make sure translation files are outdated and that is what I missed last time I tried to reproduce it?

ernilambar · 2016-08-19T02:50:24Z

Steps to reproduce.

Install WP 4.5.3
Install and activate hi_IN language
Update to 4.6.
After update:

Updating to version 4.6 (hi_IN)...
https://downloads.wordpress.org/release/hi_IN/wordpress-4.6.zip से अपडेट डाउनलोड कर रहे हैं...
अपडेट अनपैकिंग...
<p>अपने अनुवाद कुछ अपडेट की जरूरत है। हम के रूप में अच्छी तरह से उन्हें अद्यतन , जबकि कुछ और सेकंड के लिए तंग बैठो।</p>
<div class="update-messages lp-show-latest"><h2>Date Today Nepali (hi_IN)&#8230; के लिए अनुवाद का अद्यतन किया जा रहा है।</h2><p><span class="code">https://downloads.wordpress.org/translation/plugin/date-today-nepali/2.2/hi_IN.zip</span>&#8230; से अनुवाद डाउनलोड किया जा रहा</p>
<p>अपडेट अनपैकिंग&#8230;</p>
<p>नवीनतम संस्करण स्थापित(इन्सटॉल) कर रहे हैं&#8230;</p>
<p>अनुवाद सफलतापूर्वक अपडेट किया गया.</p>
</div><script type="text/javascript">
                    (function( wp ) {
                        if ( wp && wp.updates.decrementCount ) {
                            wp.updates.decrementCount( "translation" );
                        }
                    })( window.wp );
                </script>Cleaning up files...
No files found that need cleaned up.
Success: WordPress updated successfully.

rodrigoprimo · 2016-08-19T12:30:54Z

@ernilambar thanks for taking the time to test this. I wasn't able to reproduce the same behavior. Which version of WP-CLI are you running? I just tested with the latest version from the master branch. Here is what I did:

$ wp core download --version=4.5.3
Downloading WordPress 4.5.3 (en_US)...
Using cached file '~/.wp-cli/cache/core/wordpress-4.5.3-en_US.tar.gz'...
Success: WordPress downloaded.
$ wp core config --prompt         
Success: Generated 'wp-config.php' file.
$ wp core install --prompt
Success: WordPress installed successfully.
$ wp core language install hi_IN 
Success: Language installed.
$ wp core language activate hi_IN
Success: Language activated.
$ wp core update
Updating to version 4.6 (hi_IN)...
https://downloads.wordpress.org/release/hi_IN/wordpress-4.6.zip से अपडेट डाउनलोड कर रहे हैं...
अपडेट अनपैकिंग...
Cleaning up files...
No files found that need cleaned up.
Success: WordPress updated successfully.

Are you running the same commands and getting the HTML output?

ernilambar · 2016-08-21T05:41:52Z

Ahh, I had tested in existing WordPress setup. But now I checked again and there is no such output. I am not sure what happening actually 😁

rodrigoprimo · 2016-08-22T15:15:34Z

@ernilambar maybe there was an language update available when you first tested? Do you happen to know how to downgrade a language package so that we can test what happens when we run the commands above with an outdated language package? Thanks for your help!

danielbachhuber · 2016-09-01T13:34:26Z

@rodrigoprimo @ernilambar Is this a core bug, or a WP-CLI bug?

rodrigoprimo · 2016-09-01T14:03:00Z

It used to be a core bug but I'm not sure anymore since now I can't reproduce it 😄

ernilambar · 2016-09-01T14:27:43Z

I saw such output once. I tried but could not specifically reproduce it again.

danielbachhuber · 2016-09-01T20:58:44Z

Ok. If someone can reproduce this with specific steps and identify where the bug is with WP-CLI, then we can get it fixed.

ottok · 2019-03-23T11:25:07Z

I am able to reproduce this still with 5.1.0 -> 5.1.1 upgrade. See https://core.trac.wordpress.org/ticket/30497#comment:4

swissspidy · 2019-03-28T12:56:37Z

Just happened to me today with wp core update --version=nightly.

A workaround could be to disable async translation updates using add_filter( 'async_update_translation', '__return_false' ); and instead encourage users to use wp language core update and the like for updates.

ocean90 · 2019-03-28T17:04:17Z

A workaround could be to disable async translation updates

Fwiw: This is already the case for plugins/themes: https://github.com/wp-cli/extension-command/blob/fba4b2c/src/WP_CLI/CommandWithUpgrade.php#L20-L23

schlessera · 2019-03-29T11:35:02Z

Yes, the behavior for core should be updated to match the one we currently have for plugins/themes.

planetahuevo · 2019-09-05T12:34:21Z

It happened to me today.
I think it only happens when you do an upgrade and you have translations pending to be updated, which is too often in Spanish.
So disabling the async translations could fix the issue.

markhowellsmead · 2019-11-24T10:12:02Z

Following error occurred when the task was run via CRON - I'm not sure whether this is the same issue or not.

Warning: Declaration of WP_CLI\UpgraderSkin::feedback($string) should be compatible with WP_Upgrader_Skin::feedback($string, ...$args) in phar:///home/PROJECT/bin/wp/php/WP_CLI/UpgraderSkin.php on line 59
name	old_version	new_version	status
redirection	4.4.2	4.5.1	Updated

wojsmol · 2019-11-24T11:52:42Z

@markhowellsmead Witch WP-CLI and WordPress version are you using?

ocean90 · 2019-11-24T15:54:06Z

@markhowellsmead You have to update WP-CLI to 2.4.0, see wp-cli/wp-cli#5283.

bgturner · 2021-09-17T17:37:40Z

I'm still wrapping my head around a fix, but before my focus time on open-source is up, I wanted to share a more reliable reproduction using the --locale flag within the wp core download command:

wp core download --locale=fr_CA --version='4.8'
wp config create --dbname='local' --dbuser='root' --dbpass='root' --dbhost='localhost' --skip-check
wp core update

swissspidy · 2021-09-20T14:11:03Z

I'm still wrapping my head around a fix

The fix was mentioned in the discussion above already.

We need to add something like the following to Core_Command::update().

// Do not automatically check translations updates after updating plugins/themes.
add_action( 'upgrader_process_complete', function() {
	remove_action( 'upgrader_process_complete', array( 'Language_Pack_Upgrader', 'async_upgrade' ), 20 );
}, 1 );

rodrigoprimo closed this as completed Aug 17, 2016

rodrigoprimo reopened this Aug 22, 2016

danielbachhuber closed this as completed Sep 1, 2016

swissspidy reopened this Mar 28, 2019

swissspidy transferred this issue from wp-cli/wp-cli Sep 20, 2021

swissspidy mentioned this issue Sep 24, 2021

Remove language translation check from core update process #192

Closed

danielbachhuber added bug command:core-update command:core labels Nov 10, 2023

danielbachhuber mentioned this issue Nov 10, 2023

"Some of your translations need updating" message and HTML output on the CLI #124

Closed

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unexpected HTML output when updating WordPress #191

Unexpected HTML output when updating WordPress #191

rodrigoprimo commented Nov 17, 2014

danielbachhuber commented Nov 18, 2014

rodrigoprimo commented Nov 25, 2014

danielbachhuber commented Aug 17, 2016

rodrigoprimo commented Aug 17, 2016

danielbachhuber commented Aug 17, 2016

ernilambar commented Aug 18, 2016

rodrigoprimo commented Aug 18, 2016

ernilambar commented Aug 19, 2016

rodrigoprimo commented Aug 19, 2016

ernilambar commented Aug 21, 2016

rodrigoprimo commented Aug 22, 2016 •

edited

Loading

danielbachhuber commented Sep 1, 2016

rodrigoprimo commented Sep 1, 2016

ernilambar commented Sep 1, 2016

danielbachhuber commented Sep 1, 2016

ottok commented Mar 23, 2019

swissspidy commented Mar 28, 2019

ocean90 commented Mar 28, 2019

schlessera commented Mar 29, 2019

planetahuevo commented Sep 5, 2019

markhowellsmead commented Nov 24, 2019

wojsmol commented Nov 24, 2019

ocean90 commented Nov 24, 2019

bgturner commented Sep 17, 2021

swissspidy commented Sep 20, 2021

Unexpected HTML output when updating WordPress #191

Unexpected HTML output when updating WordPress #191

Comments

rodrigoprimo commented Nov 17, 2014

danielbachhuber commented Nov 18, 2014

rodrigoprimo commented Nov 25, 2014

danielbachhuber commented Aug 17, 2016

rodrigoprimo commented Aug 17, 2016

danielbachhuber commented Aug 17, 2016

ernilambar commented Aug 18, 2016

rodrigoprimo commented Aug 18, 2016

ernilambar commented Aug 19, 2016

rodrigoprimo commented Aug 19, 2016

ernilambar commented Aug 21, 2016

rodrigoprimo commented Aug 22, 2016 • edited Loading

danielbachhuber commented Sep 1, 2016

rodrigoprimo commented Sep 1, 2016

ernilambar commented Sep 1, 2016

danielbachhuber commented Sep 1, 2016

ottok commented Mar 23, 2019

swissspidy commented Mar 28, 2019

ocean90 commented Mar 28, 2019

schlessera commented Mar 29, 2019

planetahuevo commented Sep 5, 2019

markhowellsmead commented Nov 24, 2019

wojsmol commented Nov 24, 2019

ocean90 commented Nov 24, 2019

bgturner commented Sep 17, 2021

swissspidy commented Sep 20, 2021

rodrigoprimo commented Aug 22, 2016 •

edited

Loading