impressao3d

After trying multiple troubleshootings (from disabling all plugins) plus suggestions available online such as updating permalinks, plugins, php version etc which did not work, I have found the solution to the issue and I would like to share it.

It had application firewall (WAF) / ModSecurity with OWASP ModSecurity Core Rule Set. I use runcloud hosting and after disabling the firewall then the error is fixed!

Olá Marco, e malta da Moloni, obrigado pela ajuda.
Entretanto já conseguimos resolver o problema:

Eu inicialmente no código estava a usar o $order_id como se fosse o $order_id standard que é obtido pelo woocommerce, o que funcionava sempre ao fechar encomendas directamente no woocommerce.
// Get the order ID
$order = wc_get_order( $order_id );
// Get document ID from the order
$documentid = get_post_meta($order->id, '_moloni_sent', true);
(etc)
Mas ao fechar encomendas pelo API este $order_id standard do woocommerce já n?o estava disponível e o $order_id disponível pelo Moloni disponibilizava a info de forma diferente sendo a order_id como
“your_reference”
$your_reference = $order_id->your_reference ?? '';

pe?o desculpa se n?o descrevo o código da forma mais tecnicamente correcta, espero que tenha sido claro, deixo aqui o código e espero que possa ser útil para mais alguém:
https://github.com/jcmatoskx/MyRandomSnippets/blob/main/Moloni-Save-Codigo-AT-Number

• This reply was modified 10 months, 3 weeks ago by impressao3d.
• This reply was modified 10 months, 3 weeks ago by impressao3d.

I really appreciate the update @cptjump
I have sent this info over to Runcloud support as well as we are still exchanging tickets.
I sure am greatful I found you with the same issue because at this point I am really not sure what else I can do to help.
I admit I don’t really get who/where exactly is the fault, if is it WordPress core related because of that new function or Runcloud related because of the server configuration.

Having this issue happening on all my sites has been a hair pulling nightmare, especially justifying to my clients or superiors why is this happening and them assuming it’s somehow my fault :P.

If there is anything I can do to help, some place else I can also manifest this issue just let me know, and please do keep me updated with your findings!
Thank you so much for your updates so far.

• This reply was modified 1 year, 6 months ago by impressao3d.

I am still going through it with the Runcloud team.
I have made some several videos of me creating a brand new, fresh runcloud WordPress installation and uploading images to it and replicating the issue of duplicated uploaded images on the WordPress media library.

I tried clearing caches, using different browsers, incognito mode, also using entirely different computers, trying to use different internet connections, and in all of them the issue is replicated, however the latest update from Runcloud is that they are not able to replicate it on their side, but I believe they are not trying with enough images.

Awesome to know that we are narrowing this down. Indeed Runcloud and the Litespeed technology seem to be the only common denominators at this point. I don’t currently have access to another type of host so I am very glad you could chime in @cptjump and thank you very much @threadi for your help in troubleshooting this so far.

I have already just contacted Runcloud support with all this info, see if they can shine some light on this.

Thank you for your input @threadi

I actually just made a whole new video where I make a fresh installation of WordPress 6.2 and replicate the issue of the duplicated images here:
https://files.fm/u/5ea4au22b

Muito obrigado Marco por teres guiado com a luz ??</img>
já percebi que estava a haver um problema com o CRON e ao correr o valor
pvkw_points_last_update_datetime?
já actualizou
muito obrigado Marco Deus do Woocommerce Português pela aten??o, paciência e compreen??o!

We came across a new problem that is exactly the inverse of the situation reported before. It seems there are KIOS Pickup points which exist in the VASP network, are in the API as well (as confirmed by VASP support) but that do not show here on the VASP Expresso Kios network for WooCommerce?plugin

This is one of those points:

Papelaria A Capa
Código Postal: 4585-015
PAPELARIA A CAPA AV BOMB VOLUNTARIOS 1674 C COM SOL LJ9 R/C 4585-015 BALTAR

We recently got an answer from VASP regarding this issue and the previous mentioned point:

“O ponto de venda indicado n?o está disponível na nossa API.

Os pontos disponíveis tanto na API, como nas várias plataformas utilizadas pelos clientes para cria??o de servi?os est?o sincronizados (salvo raras exce??es de algum problema numa aplica??o especifica).

Neste caso concreto, e similarmente ao que já tinha indicado anteriormente,? parece-me que a lista de pontos disponíveis que est?o a utilizar n?o está correta.

Consegue confirmar que este ponto está efetivamente disponível no plugin que est?o a utilizar? O plugin utiliza a nossa API, pelo que deveria estar também sincronizado com todos os nossos servi?os.”


So VASP confirms that this point is not available at their API as well, however when testing and using VASP Expresso Kios network for WooCommerce plugin I can confirm that it is still allowing me at this very moment to select this pickup point

We are on version 2.3.0 of the plugin
Is the database of these points dynamic? Could it be somehow storing a wrong KIOS point?

Thank you once again for your attention on this matter Marco

VASP mentioned this problem is solved by restarting the main VASP windows program (the one that is used to communicate and generate their transportation documents).

Partially this problem was originated because we had their software running on a computer that is always turned on and only set to hibernate/sleep, so when this problem sometimes happens, restarting the program does fix it.

However this does not work for all points.
Here is a recent example of one that is available to be picked in the VASP woocommerce plugin, but not existant on their Windows application:

112181 – Coffee Shop A Pimentinha
Urb Pimenteiras Lt 8 Lj B
2415-767 Leiria


Just to clarify, Portugal VASP Expresso Kios network for WooCommerce
uses the VASP API to get the pickup points, correct?
Does it have its own saved database or use transients of some kind that could be outdated?

Thank you for clarifying Marco

They requested us to send them examples of these broken / unsynced pickup points, which we have already done and now we’re waiting for a response on their side.
We will update here acordingly.
Thank you for your concearn Marco!

• This reply was modified 2 years, 1 month ago by impressao3d.
• This reply was modified 2 years, 1 month ago by impressao3d.

Update: we have also contacted VASP on this issue

I have the same problem, I use oxygen (themeless builder plugin) and I have some custom woocommerce emails in a custom folder.
Before they always used to be logged, but since June WP mail logging stopped making a log of these emails, even though they seem to be sent

Yes it would be great because it’s an amazing way to decrease friction for user registration

we contacted directly with Webdados to solve this issue.