Woocommerce activation

Support
#1

Dear sirs
I want / need to install the woocommerce plugin. So I installed and activated the woocommerce plugin version approved by you under
Pro -> Validation.

The installation didn’t work as expected, because I’ve got an error.

error
error882×775 34 KB

The “Details” info stated:

error-details
error-details781×717 38.4 KB

Based on the {“success”:true} message, I figured the installation went OK though.

So I reloaded and was able to activate the plugin. After activation I’ve got the error message:

Undefined property: stdClass::$theme_location in /home/xu169nap/www/home/pi/wp-content/themes/pro/framework/legacy/functions/plugins/woocommerce.php on line 545

and one more where I can’t see the line number.

bummer…

you’ll find the details in respect to the url in the private message.

What do I need to do, to get woocommerce running without a fuzz?

I had to deactivate the woocommerce plugin for the moment. It needs to be sorted out first.

#2

Hello @VRANKOVINA,

Thanks for writing to us.

I went ahead and checked your settings it seems that the WooCommerce plugin was not properly installed. I deleted the WooCommerce plugin and reinstall the plugin again and it is working fine at the moment. Please check your site now.

Thanks

#3

thank you for your effort but nope, it does not.
the line “545” error persists.

See secure message.
My browser is chrome. Cache deleted before testing of course. Tested in Safari and Pale Moon as well.
I deactivated the woocommerce plugin again. The site is live, so this error is not nice to be seen besides the menu underneath is not visible.

It looks like woocommerce requires a standard menu or at least standard header? I have a custom header with my own menu structure. This is not a matter to change. Even if I’d like to.

Cheers

#4

Hello @VRANKOVINA,

I checked your given screenshot and I was able to replicate the issue. It seems that there might be an issue of plugin conflict between the latest version of the WooCommerce plugin and UberMenu plugin. I would suggest you please deactivate the UberMenu plugin and check it.

Thanks

#5

As said: deactivating UberMenu is not an option. Anyway I did what you’ve suggested and the php error was indeed gone.
Unfortunately this is not the solution.
What do you suggest as next pls?

Kind regards.
Ondrej

#6

Hey Ondrej,

Just go to Plugins > Add New and search for “WooCommerce”:

Screenshot 2024-11-14 at 11.05.43 AM
Screenshot 2024-11-14 at 11.05.43 AM1148×1156 120 KB

WordPress will download the same version from the plugin repository.

Best Regards.

#7

Hello ruenel

I beg your pardon, but are you sure with your advise? I’m not certain, you’ve read the messages above.

In addition: simply deinstalling the woocommerce plugin does not completely wipe it out from the database. I’ve done that. It needs some manual database clean up. This was not intended by the “maker” though. So kinda annoying.

Anyway I need to keep the UberMenu and I really need to get woocommerce running. I assume, as you deliver UberMenu with Pro and approve Woocommerce, it should be a matter of your support.

#8

Hi Ondrej,

I have rechecked your website and found the issue you described; it might be an issue with the latest version of WordPress, PHP, and the Pro. My colleague has already reported the issue to our development team for further investigation. Till the fix comes, I would suggest you add the following code to the wp-config.php to suppress Warning messages.

define( 'WP_DEBUG', false );

Thanks

#9

Thank you very much, I tried this already. Google knows… :wink:
PLS look at the screenshot in the secure note…

Spoiler alert: nope. No luck with that.

#10

You should change wp-config.php not the child theme functions.php file when editing WP_DEBUG. There is probably a debug setting in your hosting providers dashboard. Otherwise it can be changed through FTP. We’ll release a fix to remove the warning. You can safely ignore it though. Have a great day.

#11

roger that - i’ll check it and will report.

btw sorry, my bad, I misread the “wp-config.php”… next time I’ll read twice and not around midnight.

EDIT: OK. Well checking the wp-config.php this line of code is included by default? See screenshot in the secure note.

#12

Hi Ondrej,

It seems that the warning messages are now suppressed. As Charlie says, we will release a fix in one of the upcoming updates.

Thanks

#13

Thank you very much for the info. I hope I can convince the “party” to be patient. For the moment, they are not.

#14

Hi Ondrej,

The warning messages are not a blocker, but still, we will fix them in one of the upcoming releases.

Thanks

#15

Well - if you look at the screenshots I posted above - they are, pretty significant in respect to usability of the site.

#16

I realized one more thing since the update to wp 6.7 - do I need to repeat your credentials to the site in the new topic? I guess so, duh… ok. Its about the blog page.

#17

Hi Ondrej,

Thanks for creating the new thread.

#18

:thinking:

#19

Hey Ondrej,

We will be replying to your other thread shortly.

Thanks.

#20

Hi guys
Is there any progress in the woocommerce case? I really need to get this running.