Firefox Browser Cache
FYI – to set Firefox to check for a new version of a page at every visit:
- Enter about:config in the address bar
- Change the value of browser.cache.check_doc_frequency to 1
FYI – to set Firefox to check for a new version of a page at every visit:
I had a client that, despite my protestations, wanted a “Intro” page for his website – a landing page with a large clickable image and (gulp) embedded autoplay sound. His site was already set up and live in WordPress, and it already had a static homepage… and it was installed at the root of his site.
Aside: We’re using WordPress as a content management system rather than a blogger. I’ve discovered that, for the average small business/site, full blown CMS solutions such as Joomla, Drupal and MODx (the last being my preferred choice) tend to be overkill. The bells and whistles that these packages contain may get developers excited, but in my experience they simply overwhelm the average client. It’s akin to giving someone Photoshop because they need to re-size some images. WP is stable, mature, relatively slick, and probably the easiest to use. I wish I had the time to redo all of my CMS clients sites in WP.
So what I needed was an opening page that didn’t utilize the site theme. That last bit’s the kicker. You can’t just change the index page, or set up .htaccess to re-prioritize the directory index (if you were thinking you’d drop a static index.html page in there and leave WP’s index.php) – both actions turn WP’s navigation kludgy. An option would be to export the theme and database, reinstall WP somewhere other than the root, put your index page in the root, modify your theme and DB data to correct pointers and URLs, and import it into your new install… but that sure sounds like a lot of work, doesn’t it?
Here’s what I did instead:
That’s it. Obviously, make sure to put a link from the landing page to whatever your WP homepage is (in this case ?page_id=6).
There – that beats the alternatives, no?
Friday I rebuilt my work machine to Windows 7 64bit in preparation for the 8 gig of RAM headed my way (thanks boss!). I also installed the most recent release of Activestate Perl 64bit. Upon getting back down to business I discovered that none of my scripts were successfully receiving command line arguments. If I prefaced the running of the script with perl.exe (eg: c:\perl54\bin\perl.exe e:\scripts\myscript.pl argument1 argument2) it worked fine. Turns out this is a simple registry fix.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\pl_auto_file\shell\open\command]
@=”\”C:\\Perl64\\bin\\perl.exe\” \”%1\” %*”
Is all you need. Dump that into a text doc and change it to a .reg file. Double click it and let it insert into your registry and you’re good to go. For some reason the Perl installer sets the variable acceptance (that’s this bit you see above: “%1” %*) correctly for the file extension .pl, but misses it on the required pl_auto_file.
Silly.
Every time I’d rebuild my laptop I’d forget how to do this, and every time I’d finally figure it out again I’d promptly forget to save the instructions. No longer!