Archived topic
Search/Firefox
23 replies · Started by Patrick on July 20, 2019
Then you might need to contact the original site developer and see if he can contact Thrive's support for you.
Sorry I don't have any other solutions - we certainly can't fix issues for other products.
We definitely have other users using Thrive without issues so I'd think it's a certain module/functionality that's causing it.
This is ridiculous. Thrive is working completely fine for me, it's GP that isn't. If you want to take that up with Thrive and argue about whose scripts are doing what, feel free.
I'm sorry for the inconvenience but GP itself is working perfectly.
When there is a js error (from any of the plugins), it stops all scripts (search and mobile menu from GP) from working on your site.
You've already tested that both features from GP are working perfectly without Thrive so that is telling us the plugin is the issue which is something they will need to look at.
Again we have lots of users using Thrive without issues so I'm guessing it's a certain module from the plugin that's causing the issue. We can't really do anything else to debug if you can't disable any of your plugins and unable to set up a staging site so you can go through the debugging test.
GP isn't working perfectly if your scripts aren't always firing.
And instead of having your tech staff actually investigating it on your end or talking to a company who produces a product you claim your theme is compatible with you demand a customer give you a test environment or else there's nothing you can do?? Unbelievable.
Just close the ticket, I don't want to hear from you again. Worst customer support experience of my life.
Hey Patrick,
Sorry you didn't have a good experience here - hopefully I can help clarify some things.
Our navigation search option uses javascript (as well as our mobile menu toggle).
Javascript is awesome, but it does have one major flaw. If there is a javascript error on the page, all of the javascript that fires after that error will no longer work.
So you could have some perfectly good javascript that works 100% of the time, but if there's an error above it, the browser never actually reads it. It simply stops at the error and gives up.
I can't actually see the error that Leo pointed to anymore, but that looks like the issue. If that module (or anything) has an error, it will break all of the other javascript on the page, regardless of where it's coming from (a theme, your other plugins).
If you're able to narrow that error down and fix it, everything else will begin to work.
Let me know if that helps at all - I'm happy to help narrow it down if you'd still like my help.
The console error Leo was pointing to doesn't have anything to do with the problem. The error simply shows up for any undefined countries in a plugin doing a geoip lookup. So, my guess is you and Leo are in different countries or using VPNs that make it appear so. Totally irrelevant though.
In any event, I got up in the middle of the night to do a quick temporary theme change and search worked fine. The search problem also didn't exist prior to switching to GP. (Not 100% sure about the hamburger menu as I don't recall testing that in my previous theme) Maybe they were using a different search/menu implementation then you guys...I don't know.
About all I can say at this point, is from my perspective, other themes don't have a problem that GP does.
The next thing we can do is create a Duplicator (https://wordpress.org/plugins/duplicator/) backup of the site. Then you can send it my way and I can install it on my staging site. That way I can debug and find the issue without making any changes to your live site.
If that sounds good, you can upload the Duplicator .zip to Dropbox or something similar, and then send it our way: https://generatepress.com/contact
Let me know :)
Hmm that would have been a stellar option yesterday when I said I didn't have the ability to generate a staging site on this particular hosting account.
In any event, while I genuinely appreciate the offer (and you popping into the thread), I have to decline. I showed the thread to my business partners and they made it clear that we were no longer going to be switching all our sites to GP.
Despite the problems, I still personally like the theme and know the error could eventually be worked out (most tech problems can be). But when you've got 20 sites you need to standardize on a new setup and this is site #1, I understand my partners concerns about committing to one where we weren't happy with the support.
I'll probably still use the theme for personal projects that don't have investors since it's got some good bones to build on.
No worries, I hope you find a solution that works for you and your investors :)