SYNC4489

I was looking too for a setting to show/configure the arrows in the mobile slider, but as I understand it’s not implemented yet, correct?

@anastas10s the issue is now gone, I don’t have any pictures.

But as @titsmaker said, the woocommerce plugin latest version on the plugins update page was 7.3.0.
Then, it suddenly disappeared and 7.2.3 was proposed instead.
The day after, the 7.3.0 popped up again (and I updated).

Since yesterday, the 7.3.0 became available again. weird…

Yep… same thing
Maybe 7.3 was faulty and it has been removed?

Try to add this to your active theme functions.php (or better with a snippets plugin):

function my_open_short_description(){
    ?>
    <script type="text/javascript">
        (function($){
            $("#postexcerpt").removeClass("closed");
        })(jQuery);
    </script>
    <?php
}

add_action( 'admin_footer', 'my_open_short_description', 10, 1 );

The new certificate started working in the late afternoon, even if it was renewed at 9:27 in the morning…
So probably some installation/cache trouble upon renewal?

Anyway, since yesterday afternoon the certificate was updated and optimization started working again, problem solved.

Apparently the certificate on that node (117) has expired this morning 18th November at 9:26AM UTC

yep, same problem… reported too

Hello, no problem I had already fixed it in my file.
If with the next plugin update the file will be ok, so far so good ??

Thanks!

Hi,

did you have the chance to look about the problem?

Thanks

Hi Matt,

the vat_number field is added by the “Aelia EU Vat Assistant” plugin.

This is the full HTML added by the plugin at the checkout page, into the div “woocommerce-billing-fields__field-wrapper”

<p class="form-row aelia_wc_eu_vat_assistant vat_number update_totals_on_change address-field form-row-wide" id="vat_number_field" data-priority="250">
<label for="vat_number" class="">EU VAT Number&nbsp;<span class="optional">(optional)</span></label>
<span class="woocommerce-input-wrapper"><input type="text" class="input-text " name="vat_number" id="vat_number" placeholder="EU VAT Number" value="MT12345678" valid="0" aria-describedby="vat_number-description">
<span class="description" id="vat_number-description" aria-hidden="true">Enter your EU VAT Number (if any). Country prefix is not required.</span>
</span></p>

To be noted that on our website all the billing fields are hidden by a simple CSS visibility:hidden and height:1px, because we do not want customers to be able to change their billing details as they wish. I don’t think this should pose a problem as it’s only a mere CSS and if no address is added by the addressbook plugin, it works flawlessly since months…

The problem occurs only when a new address is added at checkout page.
If the addresses are just switched on the dropdown select, the vat_number field is correctly kept.

Thanks in advance!

I confirm that the temporary fix found at

https://gist.github.com/fitimvata/09b177f8c822c8a2ffedf987058f0fe3

as suggested in the official bug tracker solves the problem with WC 5.5.1

Done!
Thanks Andrea

Ok found the problem!

many months ago we had overriden the posts_search function for the native woocommerce product list to better suit our needs, and to avoid modifying the ATUM search (as it would not work with our custom code) we were intercepting the action ‘query-attachments’ from ATUM.

Apparently since the update >1.8.4 the search action has become ‘atum_fetch_stock_central_list’ so our code was running also on ATUM search, breaking its functionality.

So far so good, thanks anyway for your help :))

Hi, the extension that “fails” is just MEGA.nz cloud, nothing to do with Atum or wordpress, etc.
I don’t know why it gives the error as it works flawlessly, anyway it’s there since years and always gives that message.

The problem arose when we upgraded from 1.8.3 to 1.8.4 (and now 1.8.5)
We also disabled the MEGA extension just to be sure, but nothing has changed, the search in the Stock Central does not work anymore.

We are considering to revert to 1.8.3, are there any problems or particular procedure we should be aware of before downgrading?

PS: yes, I mentioned the wp.hooks as I saw it in a another post…