Questo thread è stato risolto. Ecco una descrizione del problema e della soluzione.
Problem: The client was trying to update the woocommerce-multilingual component of WPML but encountered a warning on the admin dashboard indicating that the update was incomplete. The system reported that woocommerce-multilingual needed to be updated to version 5.4.0, but only version 5.3.9 was available, which was the latest at that time. Solution: We recommended the client to manually download the latest version of the plugin from https://wpml.org/download/woocommerce-multilingual-multicurrency/?section=changelog. After downloading, the client should create a full backup of the site, deactivate and delete the current version of the plugin, and then install and activate the newly downloaded version. Additionally, we suggested checking for automatic update issues which might be related to server configuration or specific activities on the server at that time.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket at WPML support forum for further assistance.
Questo è il forum di assistenza tecnica di WPML, il plug-in multilingue di WordPress.
La sua lettura è permessa a tutti, ma la pubblicazione è riservata esclusivamente ai clienti di WPML. Il team di WPML risponde sul forum 6 giorni su 7, 22 ore su 24.
Contesto del problema:
I am trying to update the woocommerce-multilingual component of WPML on my site link nascosto. I received a warning on the admin dashboard indicating that the WPML update has not been completed. The warning states that I am running an up-to-date version of sitepress-multilingual-cms, gravityforms-multilingual, and wpml-string-translation, but woocommerce-multilingual is out of date. The required version is 5.4.0, but I am stuck at version 5.3.9, which is the latest available.
Sintomi:
WPML update has not been completed. The warning indicates that woocommerce-multilingual is out of date and needs to be updated to version 5.4.0, but the latest available version is 5.3.9.
Domande:
Does woocommerce-multilingual version 5.4.0 exist?
Why am I not given the option to install version 5.4.0?
Non sono un madrelingua italiano, ma sto usando l'IA per velocizzare il processo di supporto. Per favore, fammi sapere se questo ti va bene o se preferisci aspettare.
Puoi provare ad andare nel backend del tuo sito > Plugin > Aggiungi nuovo > Commerciale > cliccare sul pulsante "Controlla aggiornamenti" > e aggiornare da lì.
Dopodiché, accedi al backend del tuo sito, crea un backup completo del sito, poi vai su Plugin > Disattiva e rimuovi la versione attuale del plugin. Poi torna su Plugin > Aggiungi nuovo > Carica, carica il file ZIP scaricato e installa + attiva il plugin.
Dear Mihai,
first of all thanks for having replied! 🙂
As per attached image is seems that "woocommerce-multilingual" v5.4.0 does not exist, as our already installed v5.3.9. is the latest available.
So why that "call to action" to update "woocommerce-multilingual" to a not actually available version?
Anyway I will follow the "https://wpml.org/download/woocommerce-multilingual-multicurrency/?section=changelog" way of doing things, as I see there that v5.4.0 is downloadable. I'll keep you posted.
Thanks, e.-
Ok, that worked (attachments).
I think, though, that automatic-update failure should be investigated.
All the best, and thanks again for the provided support, e.-
I am delighted to hear that the issue is now resolved.
There's a chance that this automatic update issue could be related to the server configuration or to things taking place at that moment on the server (backend updates or similar other tasks being run by the server on the server side).
I have not encountered another similar report recently for this type of issue, but I'll be on the lookout to see if this starts happening in multiple cases.
Thank you so much for your time, patience, feedback, and reporting!
If you will encounter this in the future, please do not hesitate to get back to us.
it seems that our troubles are not ended, as the production site (no more link nascosto but in this case link nascosto) seems not to be able to interact with link nascosto. I've tried also adding:
define("OTGS_DISABLE_AUTO_UPDATES", true);
... in wp-config.php, but no tangible results so far.
Our server firewall has white-listed all IPs referring to "d1de48u35hjlfv.cloudfront.net" (143.204.215.56 included), and pings produce replies:
[root@cpn ~]# ping cdn.wpml.org
PING d1de48u35hjlfv.cloudfront.net (143.204.215.56) 56(84) bytes of data.
64 bytes from server-143-204-215-56.fra53.r.cloudfront.net (143.204.215.56): icmp_seq=1 ttl=247 time=6.39 ms
64 bytes from server-143-204-215-56.fra53.r.cloudfront.net (143.204.215.56): icmp_seq=2 ttl=247 time=6.43 ms
64 bytes from server-143-204-215-56.fra53.r.cloudfront.net (143.204.215.56): icmp_seq=3 ttl=247 time=6.45 ms
64 bytes from server-143-204-215-56.fra53.r.cloudfront.net (143.204.215.56): icmp_seq=4 ttl=247 time=6.52 ms
64 bytes from server-143-204-215-56.fra53.r.cloudfront.net (143.204.215.56): icmp_seq=5 ttl=247 time=6.50 ms
I think this might depend on the CDN we use for "www" (whilst "stage" was not under any CDN), which is QUIC (link nascosto). But even bypassing CDN there did not allow us to have the site being able to "talk" with OTGS licensing and update servers. Is there any IP I should try to whitelist (both edge/proxy and server side)?
In the end this is what we get (maybe a false positive - but as matter of fact no WPML updates are listed as available):
###############
WPML plugin is unable to connect to wpml.org.
To check for new versions and security updates, WPML must connect to its own server. Something in the network or security settings prevents this. To remove this warning, allow outbound communication to wpml.org.
###############
Well, it seems that now WPML servers are responding, as I can see what you see in attached images (which is fine).
But now is Toolset complaining about "not being able to connect to toolset.com".
As we don't actually use Toolset I can ignore that, but this is a network issue, which IMHO should be further investigated. I'm available to help, if needed.
Now coming back to update those WPML plugins.
Cheers, e.-
enrico@amd:~$ host d7j863fr5jhrr.cloudfront.net
d7j863fr5jhrr.cloudfront.net has address 108.139.243.95
d7j863fr5jhrr.cloudfront.net has address 108.139.243.82
d7j863fr5jhrr.cloudfront.net has address 108.139.243.101
d7j863fr5jhrr.cloudfront.net has address 108.139.243.53
enrico@amd:~$ host d2salfytceyqoe.cloudfront.net
d2salfytceyqoe.cloudfront.net has address 3.160.213.87
d2salfytceyqoe.cloudfront.net has address 3.160.213.15
d2salfytceyqoe.cloudfront.net has address 3.160.213.188
d2salfytceyqoe.cloudfront.net has address 3.160.213.77
enrico@amd:~$
And overall these are all whitelisted IPs, both CDN and server side:
Nevertheless Toolset is still complaining about "not being able to connect to toolset.com".
Again: we do not use Toolset and so we're not concerned about that.
All the best, e.-
If the notice doesn’t bother you, you can choose to leave it as is; however, I personally prefer to have it removed.
It's also reassuring that there are no functionality issues that could disrupt WPML or the overall functionality of the site. Still, I would prefer not to see the notice at all.
