blueblimp

The problem is every time you update wordpress and add a new feature to the template we have to copy the keys over to the new template. If its in the dabase you don’t have to worry bout copying stuff over every time. The more stuff you all in the settings the less that has to be copied.
Another idea that might work better is to have a place in the settings to insert html code into the database. For example a database entry where I can put all my meta tags that aren’t directly supported by wordpress.
If you do this it woud be just as cool is you allow this for the sidebar as well and give the option to place at the top or bottom of the bar (for things like link pool, etc.)

Rss is short for Rich/RDF Site Summary (or Really Simple Syndication) . They are XML files that allow other website or readers and such to pull the content from your blog and reference it. There are also programs that pull all these into one place (ex: all my daily comics, news sites, blogs etc. get pulled into a single program.) so a person never had to go out and visit every single wesite. I use one called sharpreader (www.sharpreader.com).
I would suggest leaving them alone but if you REALLY want to you could just delete the files marked rss and then remove the links to them in the template file.

ok, I figure out about the drop down box for the posts but what is missing is the meta info. These are the ones that GeoURL and GeoTags Use.
<meta name=”ICBM” content=”LAT, LONG”>
<meta name=”DC.title” content=”Blog Title”>
<META NAME=”geo.position” CONTENT=”LAT; LONG”>
<META NAME=”geo.placename” CONTENT=”City, State”>
<META NAME=”geo.region” CONTENT=”US-UT”>
Also can you put a setting to turn OFF the individual blog item drop down and just use the meta items or, what would be real cool, toggle the blog to single user mode and move a single dropdown to the sidebar that uses the defaults.

Ok, I plugged in my geourl made sure it was activated and renamed index-geo.php to index.php, but for some reason nothing is showing up.

Yeah, I figured that but I meant id the wordpress maintainors wanted to add it in they’d probably code it into the db with everything else.

Hmm, Being as I coded this in .71 it looks as if it won’t work in .72. It looks like they moved the configs to the db.