javiermates

Ok. I figured out what triggers the error.

The error occurs when the child theme inserts its own js, no matter its content, even if it is empty. But only if it depends on ‘ct-scrips’.

If the script is placed only with jQuery as a dependency, everything works normally.

• This reply was modified 1 year, 2 months ago by javiermates.

Hi.

You can download the child theme at this link:

https://drive.google.com/file/d/1_L8v94SFs2W4Moxt7hHlnd5J99OJcHIw/view?usp=sharing

In Firefox the message is different:

Uncaught TypeError: document.body is null …

• This reply was modified 1 year, 3 months ago by javiermates.

Hello. I have disabled any caching and minification systems on this site. Uses a Blocksy child theme. The theme does not modify or interfere with Blocksy coding, it is merely CSS:

https://esceptica.net/

Please tell me when you have reviewed it, so I can activate the caches again. Thank you.

Obviously, it is necessary to activate all error reporting in wp-config.php. Something like:

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, true);
define(‘SCRIPT_DEBUG’, true);

Try PHP version 8.1, if you haven’t tried it already.

It’s strange, it’s definitely this plugin. As soon as it is disabled the warning disappears.

Appears on all administrative pages. The warnings disappear when you deactivate the plugin. I haven’t tried it in the pro version.

The problem is that if there are no custom fields like in my case, the wrong behavior of the plugin can go unnoticed by a tester.

The plugin always fills in the address field, no matter if it is Express or not, or if you enabled changing the address or not.

That’s the problem, I’m already using “Use place order button”!

I am not using PayPay Express.

Indeed the plugin does not do what you say. I explain the steps I follow:

Once on the checkout page, I fill out the billing fields. There are custom address fields there, but mandatory ones that I need.

When the customer chooses to pay with PayPal, the popup opens that requests their login and/or confirm the payment. With the option you indicate, the user cannot actually change the address from that screen.

However, once the customer confirms their payment, the control returns to the checkout, but the “Send to a different address” checkbox is enabled on its own, and the standard shipping address fields in that section are filled out, but not my custom fields (because it obviously don’t know them).

I just wish it didn’t try to fill in the fields like other plugins do.

Sorry, I don’t know if we’re talking about the same thing.

Yes, there is an option to disable PayPal shipping address, in the advanced options tab, but the only thing it does is prevent the customer from changing their address from the PayPal popup.

But no matter what is chosen there, the plugin tries to fill the fields.

How do I not use express checkout then, or avoid that behavior?

I have deactivated almost all the plugins that are not essential for the store and the problem persists.

The only thing I can suggest you try is the Astra theme (free version), using the theme’s native cart. Maybe toggling the use of ajax when adding items to the cart will make a difference.

Sorry, my mistake

I have deactivated almost all the plugins that are not essential for the store and the problem persists.

The only thing I can suggest you try is the Astra theme (free version), using the theme’s native cart. Maybe toggling the use of ajax when adding items to the cart will make a difference.

I promise to review what you tell me, but it will take a while. For now my installations are no longer in multisite mode, so I would have to spend some time doing tests in the sandbox, but for now I don’t have time, but I want to help to discover the cause of the problem.

I will review it soon.