pacfire

That’s great – at least you have it under control!

@mpmchugh hit up AIOSEO support to get the same script fix for the Pro version 🙂 I’ve not had a problem since installation – even after updates.

If anyone is experiencing the same problem: QuadLayers (the developers of Perfect Brands) have logged into our website as an administrator and determined that Perfect Brands is operating correctly.

They suggested there is a plugin conflict on our site. I have since systematically deactivated our plugins and have discovered the conflict is with All in One SEO – we have the pro version and have lodged the conflict – hoping for a resolution soon.

If you are having two logos (or listings, depending on your set up) appearing on a single product page (when you only have your set up programmed to only show the logo once) and you have AIOSEO installed, try deactivating AIOSEO.

@falo – if you still have issues – this might help.

Sorry about the delayed reply. Here is the link to the screenshot:

Is this what you need? https://snipboard.io/lGaubR.jpg

Note the Pac Fire brand logo showing twice – I’ve not changed settings – it’s just been since the last update.

Hi @caseproof

Thank you so much for your reply.

I copied that script into functions PHP and reloaded the page – at which point I got a critical error – this is before I tried to put the shortcode in.

I’m going to be 100% with you – I am not very good with PHP so I have no doubt that it’s something that I’ve done.

I have screenshots if you would like to have a look at the situation? I’m so sorry – I apologise for the questions and problems.

Amanda – Pac Fire

Hi @caseproof

Thank you so much for the reply.

I feel like this is going to make me look pretty stupid, but I can see it forming an important part of the site, so I’m going to ask anyway.

I found that snippet early on – but I have no idea how to use it in the premise of bringing the user role name forward and putting it somewhere on the site.

Basically – different user levels have different access levels on the site we are developing. If a user doesn’t have access to a particular part of the site – it can be explained by their access level.

Right now, I have a widget in the sidebar called “logged in user” under which, with shortcode from Shortcodes Ultimate, I have displayed their name, username, payroll number (a custom field) and I have tried to drag role forward also using the “role” as meta, but it doesn’t work so I’m doing something very wrong.

I’m sorry about this follow up question – I’m not a developer by any means, I can occasionally change code to suit our situation, but in some circumstances, like this, I have no idea what I’m looking at…

My apologies once again – thank you for your help thus far.

Amanda @ Pac Fire

…. and like magic, a patched version of WooCommerce has been very quietly released.

I just tried to update the plugin again – and it has indeed successfully updated. This was absolutely a problem the WooCommerce 5.7.0 update.

To all other users watching this thread (@mathewborja @mahasiv), my suggestion would be to try and update to 5.7.1 and see if that resolves your problems – there is a good chance it will.

@adamkheckler perhaps I should have worded my first post more carefully.

All of the symptoms in this post:
https://ww.wp.xz.cn/support/topic/woocommerce-plugin-activation-crashes-site/
…are what I am experiencing. But I have not been able to force the same error – but it sounds very much like this could be my issue also.

@thup90 trouble shooting a conflict is the first thing I did, please see below for the exact steps that I have been through:

1. On update of WordPress, our site crashes. With the update – the error we received on the front end was an internal server error. I checked with our host – there are no problems on their end however they did indicate a huge uptake in resources from our site, Particularly Inode Usage, which I couldn’t see from CPANEL. They said that indicated a corrupt file.
2. I didn’t know what the problem was at the time – so I went trouble shooting in FTP and found that WooCommerce was the problem. I killed the plugin and reinstalled the current version 5.7. Our site crashed again, this time it was a WordPress Fatal error (no other details were given).
3. I uninstalled WooCommerce completely following the instructions, then installed again from scratch. Our site crashed displaying a WordPress Fatal error.
4. I found the thread above and started installing past versions of Woo, I had to go back to the same version as OP, 3.9, to get the site up again.
5. I tried to update 3.9 to 5.7. The site crashed AFTER the updater ran displaying a WordPress Fatal error.
6. I thought it might have been the theme, so I killed Woo yet again. installed Twenty Twenty, reinstalled 3.9, the site worked. Updated to 5.7, the site crashed displaying a WordPress Fatal error.
7. By this time, 4 hours had passed and it was clear the problem wasn’t with me, or the website, but it was indeed with Woo, so killed Woo again, reinstalled the only working version, 3.9 and left the site working – only just.

… and here I am. I will get the server logs for you – but the above is what happened – I went to host support FIRST when I was given the internal server error. There is no issue on their end and the only thing that can see wrong is the heavy consumption of resources that has never been common on our hosting before the update.

I have not updated any of our other, larger sites out of pure terror that this might happen there too.

Hi @thup90

Thanks for your message.

I am not getting the same error message – as in the missing database. All I am getting when I try to update or activate a new version of WooCommerce is an internal server error (500), the whole site locks up and then crashes. Both the front and the back end go down – so I’m trouble shooting through FTP for the most part.

I have re-downloaded the system themes and tried it with TwentyTwenty, turned every plugin off, uninstalled completely then restored. I have tried EVERY install from 5.7 down to 3.9, 3.9 is the ONLY one that has worked for me so far.

I’m also experiencing the issue @mathewborja noted above – where it is consuming system resources (at our host) namely our Inode Usage is through the roof.

I’m not happy that others are experiencing this, but it is making me feel less crazy.

I did post my WooCommerce status above after I had hit post originally – I edited with the log – sorry about the lateness of putting that up.

Any help would be amazing.

Thank you all.