:tools: Scheduled maintenance

Heads up! Downtime for the Forums, related to the NodeBB upgrade, is planned for Thursday, December 14, starting from 10:00 UTC.
Please make sure to finish all your posts before this time. The downtime should only last for a few minutes.

Google did it again (opera 12 search)

  • So google is persistent with not letting Opera 12 users use it anymore. Last solution required tempering with .dll files, and now even that wont do the trick any more. Any new solution out there .. ? Please help, I dont want to change my Opera 12 as a default browser.

  • I dont want to change my Opera 12 as a default browser.

    So change your search engine.

  • toi ko hiu chug ta dih noi gj ve diu nay, hay yeu nhug gj ban co the

  • What's the problem, exactly? Whatever it is, I don't see it yet (and I'm using the same DLL patch that you are). I'm talking U.S. Google, btw. How about you?

  • What patch is that?

  • It was an edit to change the user agent id for Firefox's string because Google was being stupid about displaying the current look of the page to Opera. So when masked as Firefox now, the numbers in the string are sufficient for Google not to do that.

  • 1st) can anyone explain the problem to me? As rseiler I don't see any problems with google (the search engine) and using O12.17x64 (Be it with g <search term> in the address bar, the search with <google> field, googles website or via marked term->menu->search with->google - way of search shouldn't make any difference, but wanted to mention it just in case)

    2nd) rseiler - and why a .dll for that? Shouldn't opera:config->user prefs->custom user agent be enough for that if one really wanted to exclude the mentioning of opera from the masked agents or to identify as an up2date browser?

  • In override.ini:
    [site]
    User Prefs|Custom User-Agent=Mozilla/5.0 (Windows NT 6.2; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 Opera 12.17

  • Fair - and better than modifying the DLL - but Firefox is now at 36.

  • I think the idea is to find the "sweet spot" (if any) between an older spoofed ID that still works at a site and a newer spoofed ID that may also indicate a critical feature availability of that pretended browser that isn't actually there in old Opera and thus breaks the site code.

  • I have to apologize, my override.ini file restored itself to default, dont know how. Once I added the necessary lines, it is all working again like it should.

  • Ah, good.

    @Shandra, because I wasn't aware of that at the time, though using the one in opera:config would be very ill-advised, as it changes it for all sites.

    The one in override.ini, mentioned in the next post, is the way to go. I wasn't aware of that either back at the time, though I would have noticed it earlier if the "User Prefs|Custom User-Agent" line ever actually appeared in the file.

Log in to reply
 

Looks like your connection to Opera forums was lost, please wait while we try to reconnect.