Publishing Products not working

Hi all,

I see this wasn’t actually resolved and I am having the exact same problem as those reported above.

I have also tried swapping out themes, disabling plugins, increasing memory limit to 256M etc

All I get when I try to publish a product is the spinning load screen.

Any further advice on this would be appreciated.

Thanks,
Charlotte

Hi!

The infinite spinning loading screen means that the publishing has failed and the script most likely crashed. The cause of that will be in your server’s error logs. Please look there and let me know what it says.

You can also try toggling “fast publishing” and increasing memory limit to 512MiB.

Kind regards,

V.

Hi V,

There are no errors showing in the log I just checked with my hosting company. I just tried to publish another product and it’s still not working, this is what is coming up in the log:

Code:200
Message:
GET /wp-admin/admin.php?page=wookite-plugin&endpoint=product_range&id=NaN&wpnonce=a20d6d411e HTTP/1.1
Size:532

Thanks,
C

The request that you’re looking for should be something like
POST /wp-admin/admin.php?page=wookite-plugin&endpoint=publish_product&job=<some_number>&wpnonce=<some_code>
(notice that the endpoint= part says publish_product, not product_range, and there is job= part involved)

Just to be clear, we are talking about Apache’s error_log file, not your Chrome’s Developer Tools console.

Cheers,

V.

Yes Apache’s error log is what I am looking at.

I have lots of the above and one 500 error:

Code:500
Message:
POST /wp-admin/admin.php?page=wookite-plugin&endpoint=publish_product&job=9c04-7d2c-6f55-e68d-21b2-e967-5fd0-bd4e&wpnonce=6381ccd06c HTTP/1.1
Size:248

All the others are:
Code:200
Message:
GET /wp-admin/admin.php?page=wookite-plugin&endpoint=publish_product&job=9c04-7d2c-6f55-e68d-21b2-e967-5fd0-bd4e&wpnonce=6381ccd06c HTTP/1.1
Size:561

Thanks, C

The first one matters here (the second one just gives your browser a progress update, which is a constant zero because the publisher failed).

See the first line, “code: 500”? That’s a code for “internal sever error”, which means that the publishing script crashed, and there is no way that this didn’t leave trace in your server error logs, unless they are completely turned off.

You need to find where your provider gives you access to those logs. If they provide the site admin functions through cPanel, there is an “Error log” icon in the “Logs” section there.

Did you try the other two things (toggling “fast publishing” in the plugin’s General Settings and increasing the PHP memory limit to 512MiB, even if just temporarily)?

Kind regards,

V.

I did try the fast publishing and increasing PHP memory to 512MB but still doesn’t work.

What might cause the publishing script to crash?

Thanks, C

I did try the fast publishing and increasing PHP memory to 512MB but still doesn’t work.

Thank you. I was hoping that one of these would help, as they often do. ??

What might cause the publishing script to crash?

That’s why I need to know what ended up in error logs when it happened. If something bad is happening on your servers, but not on those that I’m testing on, I’m blind and the error logs are the only way for me to try to find out what’s wrong and then try to fix it.

Kind regards,

V.

That code info I gave you was from the log in the plesk control panel for that domain. That’s all the information there is there?

Thanks,C

The codes above look like they come from an access log to me. That’s the log that gives you what was accessed and what was the response to those requests, but no details on what went wrong.

I have never used Plesk Control Panel, but this looks like valid instructions where to find error logs there.

I hope this helps,

V.

Ok, this is what it in the Apache Error Log:

This is in red

Error –
Premature end of script headers: admin.php, referer: https://thelittlecarnivorecompany.co.uk/wp-admin/admin.php?page=wookite-plugin

These are in yellow

Warning –
mod_fcgid: read data timeout in 300 seconds, referer: https://thelittlecarnivorecompany.co.uk/wp-admin/admin.php?page=wookite-plugin

there are loads of these

Warning – RSA server certificate wildcard CommonName (CN) `*.unlimitedwebhosting.co.uk’ does NOT match server name!?

That’s all that’s in there.

Thanks,C

The first one is the crash. Unfortunately, it doesn’t say what caused it or where. That error means that something went to output before all the headers (i.e., prematurely), which is likely a print of some error message.

Please, look here on how to get more detailed PHP errors.

You might also need log_errors=On in your php.ini file (this seems to explain where that file is).

The second one means that the script was running for too long, which is a bit weird if it failed before that. Let’s focus on the first one first, as the latter could be cause by the former.

The third one has nothing to do with us. It means that you are using a so called wild-card certificate (to enable HTTPS) for *.unlimitedwebhosting.co.uk where * can be replaced by any name (not containing dots) on a server that has a different name (maybe cebcreative.com or something like that). You probably need to replace that certificate with a proper one.

I hope this helps,

V.