cleanpagedesign

Thanks for the reply. Yes, this is my line of thinking – that it is a device-specific issue. I have turned off caching and advised the user to take certain steps with their computer.

I wasn’t sure if there was any element of caching or similar present in wePOS, or if there was something else in there that I needed to be aware of.

Appreciate the fast response. I’l mark this as resolved.

Thanks for the reply. I hadn’t thought of using the WP customiser Additional CSS panel. I was putting it into my child theme’s custom.css file. Maybe it was a caching issue, or some badly-written CSS on my part!

I’ve now got the changes I wanted.

Thanks for the quick reply. I will take a look at github.

Oh, OK. Cool. It popped up on the dashboard. I didn’t dismiss it because I wanted to leave a review. When I went to edit a page, the pop-up appeared on the editing screen, obscuring the page editor – which I thought was a bit much. But if its not supposed to do that then that’s OK.

Hi Joe

Thanks for getting back to me with these suggestions. It was indeed in the my_calendar_options field in the wp_options table.

I changed it to the live-site address and it’s started working as expected immediately.

Thanks
Dom

Hi Joe

Yes. I’ve just added the links back in on the home page so you can see what’s happening.

https://rhcpc.co.uk/

Thanks
Dom

I, too, was experiencing the same error message in all of the blocks in my events.

Your site doesn’t include support for the “tribe/event-datetime” block. You can leave this block intact or remove it entirely.

Like @steffievolvcom, deactivating WP Go Maps fixed the issue for me.

Just commenting here to add to the conversation.

WP: 6.2.2
PHP: 8.1.17
TEC: 6.0.13.1
Theme: Genesis Framework (child theme)

Thanks
Dom

@intelcoders Hi there. I tried a couple of things and seem to have resolved it, but I haven’t tested it in the real world yet; only on a staging site – but I’ve gone back to it several times and tried in a private browser etc to make sure it wasn’t a one-off.

First thing to say was that I deactivated everything except Woo and WePOS and reverted to the TwentyTwentyOne Theme and I was still receiving the error – so I figured it wasn’t a conflict.

Next thing I did was make sure the /wepos/ URLs (think there’s a /wepos/ and a /wepos/#) were excluded from the cache. The other thing I tried was assigning a sale to a registered user (a test one I had set up). One or the other, or both, of these things appear to have resolved the issue. I suspect it’s the cache, but if it is the user thing, what I thought I could do is to set up a dummy user eg “POS User” and then assign cash sales to them.

Thanks, Leland. is_singular( 'tribe_event' ) did indeed do what I needed. Appreciate the help.

Thanks Guga. That’s prgress, but it seems to target every single page, post and single event.

Is there an is_singular( 'event' ) or ( 'tribe_event' ) that can be used?

OK, thanks. I deactivated all plugins (expect for WePOS and Woo) and the error persists.

I’ll try a support ticket and see if I can get to the bottom of it.

Dom

Thanks @mplusb

I’ll try that and look forward to the update.

Hi @mplusb

You can look at my portfolio site login – it’s happening there: https://www.cleanpagedesign.co.uk/

Thanks

Same here, login box set far left. I also have a language selector dropdown to the right of the login fields.

https://ibb.co/q12Nqbr

@lapzor Yeah, it still looks like it works fine. I installed Enable jQuery Migrate Helper to deal with another issue that came with 5.5, and it flags up deprectaed jQuery when you go to a plugin’s settings screen.

https://ibb.co/T1V7Qgh