I found this blog when someone posted in the PPCF Forum about a new free version of SpeedPPC that someone had cooked up. Being a user of SpeedPPC myself and of course also a coder, I just HAD to check this out. I’ve got too much on my plate right this second to put it through its paces, but the overview sounds great and I’ve little doubt that it will be a very handy script indeed!

Check out the free PPC campaign builder now!

A while back, a “big league” adsense earner gave me some heads up about using properly formatted code on my pages, so that the SE spiders would handle it better and rank the pages better. His arguments on the whole made sense, and I certainly couldn’t argue with his income levels. But I just never took the time to really figure out all the areas of proficiency I needed to have when it came to coding my templates properly. HTML and CSS can be such a pain in the rear!

Anyone building portal web sites or doing any type of AdSense or other PPC oriented income stream, has undoubtedly run across “scraping.” It’s the concept of grabbing content from another web site, and displaying it on your own site. Now, issues of legality or ethics aside (don’t even get me started down those roads - I have vary strong opinions on the subjects that go a bit against the “mainstream”) - this has been used for a long time and is a cornerstone of how RSS feeds are used today. But it really gives you no power… all you can do is regurgitate the content. Sure, some clever people will run it through their own processor first, changing keywords, or in some cases swapping out links with their own (oh you dirty black hatter… ). But it’s possible to do MUCH more, with the same basic idea… just taken up a level.

Here’s a little something that can work both as a security feature if enabled, and a debugging tool if disabled.

Anywhere you have include statements (especially your satellite index.php if using my method), you can use the @ symbol to determine if errors are output to the browser, or hidden (suppressed).

So for example, this:

< ? include ("somefile.html"); ?>

Would display all sorts of ugly errors if the file couldn’t be found, or if there was generally any problem with it.

However, this:

< ? @include ("somefile.html"); ?>

I have decided to begin to take down my thoughts & ideas on programming, with the eventual expectation of turning them into some kind of course, book, autoresponder series, SOMETHING. In the mean time, they will begin to appear here as I sit down and blast them out. So, watch for ‘em! You just might learn a thing or three.