Posts Tagged ‘google’

You can search Print-Bingo.com!

Monday, February 14th, 2011

The other day we added a Google Custom Search box to the top right of print-bingo.com, our awesome web based bingo card generator.  We’ll probably tidy up the setup if we discover that it is used frequently enough.  The nice thing for our setup is that we configured this Google Custom Search Engine to search the three sites that have print-bingo.com content, the site itself, our corporate blog (the site you are reading right now), and our support forum.

This is actually our second run-in with Google Custom Search.  Late last year we played around with this technology when we created KittenSearch.net, the cutest search engine in the world.  We still haven’t decided if we’ll keep KittenSearch.net around or not.  We learned a few things, and that was the primary goal.

Google Chrome Built-in PDF Viewer Incompatibility with IFRAME and a Workaround

Saturday, December 11th, 2010

With the recent automatic upgrade of Google Chrome to version 8, Google made their built in PDF viewer the default viewer *.  I.e. there is now no need to separately download Adobe Reader or Adobe Flash Player to browse the web with Google Chrome.

Generally, I like this addition to Google Chrome; however, it caused some work for us.  Our web based bingo card generator, print-bingo.com, is highly dependent on PDF’s.  That’s the sole reason why our bingo cards are dead-easy to print out by the hundreds.  Unfortunately, Chrome’s built-in PDF renderer does not display PDFs that are in an IFRAME tag properly.

For the last few days, this is what users of print-bingo.com would see after generating 5 pages of bingo cards on print-bingo.com:

 

Broken PDF rendering in an IFRAME in Google Chrome 8 - screenshot from print-bingo.com

Broken PDF rendering in an IFRAME in Google Chrome 8 - screenshot from print-bingo.com

Chrome tries to scale the parent page to fit everything in… and it fails badly.

We were not able to get things working 100% the way we would like, but we have a workable situation now.

The basic steps that we had to take:

  • Change from IFRAME to OBJECT tag.  For whatever reason, this fixes the zooming issue.  And it was quite simple.  In our case, there wasn’t much difference between the two HTML tags.
  • Unfortunately, we can’t find a way to get Chrome to print the contents of the object tag without printing the rest of the page (though, perhaps using CSS  might work).
  • Instead, we added some bold warning text that gives Chrome users instructions to use the manual download links. We use a little function to identify Chrome users – the two key lines of code are: 
    $u_agent = $_SERVER['HTTP_USER_AGENT']; 
    if(preg_match(‘/Chrome/i’,$u_agent)) { $ub = “Chrome”; }

So, we ended up with a workaround.  We sincerely hope that Google will add the missing interface elements that will make things just work, but until then, we are doing some other site improvements as we prepare to bump up the price of Premium Access to $12 in 2011.

* If you want to go back to using Adobe Reader in Google Chrome, you can turn off the  built-in viewer by going to the special address about:plugins and change Chrome PDF Viewer to Disable.  Of course, website owners should not depend on end-users to do this just to visit your site!

 

 

Is it a good thing when you don’t notice that your AdWords campaign was turned off?

Thursday, September 16th, 2010

We’ve run campaigns for print-bingo.com on Google AdWords from day 1.  Actually, we ran ads before the site was even on the print-bingo.com domain.  So, it’s been years.

We learned this week that Google has quality checks to make sure that AdWords customers are running legitimate websites.  I.e. they don’t want to sell advertising to scammers, malware installers, virus tricksters, and whatever Google deems to be low quality sites.  As with all things Google, these are highly automated processes. This quality score concept  makes sense –  I would be less likely to click on ads if there was a chance that the landing page was virus laden.

Apparently,  after our large edits to print-bingo.com in  August, we tripped the quality scanner and our AdWords campaigns  were turned off.  We sent a support request in to Google and a few days later, after a manual review, our ads are now running again.  Yay!  More advertising expenses.  :)

The strangest thing is that we didn’t even notice for two weeks.  We’re happy to say that sales are up so much year over year, that we just didn’t notice.  It did seem weird that we weren’t getting many (in retrospect, zero) referrals from Google AdWords that lead to conversions, but that happens some days, so it didn’t shout problem.

What’s the point of this post?  Well, actually, I think we’re bragging about our increased sales.  But on a practical note, make sure you watch your campaigns – I couldn’t find a way to get email notifications, but it might be buried in the interface somewhere.  You can always watch your logs.  Anyway, the point is, even if things are going well, it’s possible that they could still go better.

Technical notes: If you want to see when you’ve been visited by the quality bot?  Check your web access logs for the user agent AdsBot-Google.

Print-Bingo.com Works with Google Chrome Web Browser (again)

Monday, July 5th, 2010

Today we updated print-bingo.com’s programming.

The biggest fix, is that our site now works properly in current versions of Google Chrome. Our web based system for generating highly printable bingo cards is great… but once in a while we run into compatibility issues. For now, it’s fixed. We’ve tested in current Firefox, Internet Explorer, Google Chrome, and Apple Safari web browsers. Ironically, part of the programming fix was related to a compatibility tweak for Mozilla browser from years back. Mozilla users, if you actually still exist, you will need to use a different browser to use print-bingo.com now.

At the same time, we made live a feature that we wrote for a custom bingo job a few months back. All bingo cards within a single run are now guaranteed to be unique. Previously, it was entirely random if a card was duplicated in a run – but it was highly, highly, unlikely. In fact, we programmed an email notification if the dupe-tester actually catches a dupe.

We had to hard-code a duplicate entry to actually make sure the dupe tester and the email notifier worked. The odds of duplicate cards that are randomly generated is extremely low – you can’t generalize exact odds, since every custom bingo card design is different.

The site has probably generated 1,000 card runs since the new code went live… and we haven’t been notified of a duplicate card yet. If we ever catch a dupe, we’ll be sure to post about it.

More code changes are on the way. It’s summer, traffic to print-bingo.com is lower than normal.

User Scripts Broken in Google Chrome?

Friday, December 11th, 2009

A little while ago my custom user script for Chrome stopped working. I’m currently using the “dev channel” at home. When I first switched to Chrome, that was the only version that supported user scripts (basically GreaseMonkey from FireFox integrated into Chrome).

My script is simple, it makes some font and color changes to a few websites that I view regularly to make them more legible (IMHO). I should bundle it into an extension some day…

Anyway, it took a bit of research to figure out what happened. Look here on the Google Chrome blog:

[r33013] Disable –enable-user-scripts. (Issue: 27520)
NOTE: You can now install user scripts by navigating to them. You will have to reinstall your current scripts (they aren’t migrated).

– http://googlechromereleases.blogspot.com/2009/12/dev-channel-has-been-updated-to-4.html

So, scripts are still supported, but I have to install it again. I didn’t quite understand “navigating to them” meant, but it actually means exactly what it says. In the address bar browse the file system, e.g. go to here:
C:\Users\%username%\AppData\Local\Google\Chrome\User Data\Default\User Scripts

Then double click on your .JS file, and a little extension installation prompt pops up. It’s pretty cool actually.

Hmm… now that Google Chrome regular version supports extensions, I might be able to take myself off the dev channel.