-
Contact DetailsWebsite With Issuehttps://www.pdxaa.org/meetings/ What happened?Front end users on website are unable to open drop down pick lists for location, day, time and meeting type. They work fine for logged in admin but not for someone with no login. I checked settings, didn't see any that look helpful. We're using TSML Version 3.16.18, with TSML UI selected, on WordPress 6.8.1 running Blocksy theme. Meeting Guide on smartphones is unaffected so we're not totally SOL for users. Testing front end access using Firefox and Vivaldi. Now, to further compound the problem, I cleared the hosting service's cache (it's worked before for some issues) and the list on the front end has disappeared completely. What browsers are you seeing the problem on?Firefox Relevant log output/errors |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
hi @Spsrky ive converted your issue to a discussion. we ask that users not create issues and let the devs do that once we determine the problem we havent made any changes to the plugin or tsml ui in quite some time, can you tell us when you first noticed the issue with the dropdowns? it sounds like clearing your hosting cache may have reset permalinks, please try going to wordpress admin settings > permalinks and clicking save changes |
Beta Was this translation helpful? Give feedback.
-
Resetting permalinks took care of restoring the meeting list in the backend but not in the front end for users. We first noticed the problem with the dropdowns today. The only recent change we've made was to add Woo Commerce about two weeks ago. |
Beta Was this translation helpful? Give feedback.
-
Hi @Spsrky @joshreisner, I'm chiming in just to say that dropdowns are working normally for me on https://www.pdxaa.org/meetings right now. Perhaps you've made changes since reporting the issue. Just letting you know. |
Beta Was this translation helpful? Give feedback.
That's ugly but it wasn't the source of the problem. I deactivated several plugins that had updated in the past two days and that eliminated the problem. Turning them back on one at a time showed that it was a Jetpack update that was at fault. WooCommerce seemed to want Jetpack installed (we hadn't been using it previously) but deactivating doesn't seem to have broken anything in the online store, so I'm just leaving it off. Let's call this one closed unless you have something to add.