David Ruekberg

Great, thanks!

Thanks, 8.1 seems to be working fine. It’s not that the deprecation notices were showing up in the log, they were listed in the header even for site visitors, which took up almost the whole screen. Anyway, thanks for the reply, I appreciate it and look forward to the update.

Brilliant. Thank you so much. Another reason to love this theme. The support is so friendly and helpful.

Thanks, I will. I appreciate your help.

• This reply was modified 11 months, 1 week ago by David Ruekberg.

Thanks, Ben, that was the problem. When I was hunting around for solutions earlier I hestitated to disable Jetpack Comments because I wanted users to be able to log in with a Facebook or WordPress account. I guess they will have to wait for me to approve the comment, or else register on my site. If there’s a workaround I’d love to know. For now, this works, thanks again.

Why did you give it 5 stars?

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

Hi, thanks for your previous suggestion. Sorry about my long absence. That issue was consuming too much time. Anyway, I’m back, and tried the suggestions. I used Meks to disable all plugins, activated WooCommerce, changed the theme to Storefront, and tried to update WooCommerce. It failed with the same error, so I deleted the plugin and tried to install it manually. That failed, with the error that the destination folder already existed. So I deleted the folder via FTP and tried again to install WooCommerce. That worked, but the problem persists. I don’t really want to have to delete the WooCommerce folder every time I need to update. And since all the other plugins were disabled and the theme is Storefront, I don’t know why it continues to fail to update.

The error log in the previous comment suggests there is a problem with The Events Calendar hook to WooCommerce. I don’t really know what that hook if for and would be happy to disable it if I could figure out how. Suggestions?

Thanks, the updates didn’t help, just copying it over to a new event and deleting the original. Maybe a database entry got corrupted or something.

I’ve since set up a staging site. Thanks for the suggestion and the help.

Yes, I’ve just created a staging site, so the next time WC updates, I’ll test it out there. Hopefully it will save a fatal error log this time. Would that be located in the WC folder? As I said, I have to delete that before I reinstall, but I’ll look before I delete. The other logs show up after the WC folder is deleted (see previous message). Where is the fatal error log stored?

Hi @anastas10,

Thanks for the quick reply. Unfortunately, I don’t have a debug.log. As I was preparing last night’s message I found instructions on how to enable that, so the next time this happens (it happens every time I update WC), I will be able to capture the error.

In WooCommerce status, there is no “fatal-errors.log”, only “wc-services” going back to 2022-11-28. Which is weird because in order to fix my installation I had to delete the WooCommerce folder in my WP plugins directory so the new one would install, but maybe there is a log hidden in another folder (e.g. “woocommerce-services”).

I ended up just copying the event to a new post and deleting the old one. The new one shows up. Not sure what happened to the old one, maybe got corrupted in switching from Gutenberg back to Classic editor. Thanks for the suggestion though. Someday when I’m brave I’ll set up a staging site. Good idea.

Thanks for your reply. I contacted the theme creator, and they gave me some code to paste in that solved the problem. The discussion is here.

FYI here’s the code:

.tribe_events.entry {
  background: none;
  border: none;
  box-shadow: none;
}
.tribe_events.entry:before {
  display: none;
}

OMG, thank you for the FAST reply and the PERFECT solution. I’m not a coder so I would never have been able to do that myself.

Yeah, the screenshot showed the old layout, but mainly I wanted to have the info box be transparent so my custom background color showed and so the text didn’t overlap. It works! Thank you so much!

Hi Niklas,

Thanks for your help. Sorry about my slow reply. Yes, that fixed it. I disabled “”PayPal Standard” and things went back to normal. Looks like WooCommerce removed this as in option in a subsequent update.

Thanks again.

I’m getting this error as well. I tried the test at Google Rich Results Test (which replaces the Google’s Structured Data Testing Tool you recommended for a similar issue at https://theeventscalendar.com/support/forums/topic/missing-field-location-google-search-console/). Under “Events” there are four warnings.

At the top:
Missing field “eventAttendanceMode” (optional)
Missing field “performer” (optional)
Missing field “eventStatus” (optional)

Further down under the “organizer” field:

Missing field “organizer.url” (optional)

There is data in the Organizer section of the page and reported in RRT.

Here’s the affected URL:

https://poetry.ruekberg.com/event/poetry-image-and-sentence/

Thanks for any help you can give.