mumkin

Somewhat relatedly: If you don’t want snoopy people to be able to discern what version of WP you’re running, you probably want to edit your theme’s header.php to remove the meta tag immediately following your title. It calls<?php bloginfo(‘version’); ?>, so you’ve got this in the source of every page:

<meta name="generator" content="WordPress 2.0.1" /> <!-- leave this for stats -->

Flock works with my standalone WP 2.0 install. Obviously it’s a more limited interface, but I just walked through the config and successfully composed a draft which was sent to my site. What didn’t work for you?

Go to your Admin > Options > General page. Is there a check beside “Anyone can register” ? If not, check it and click the Update Options button.

your current wp-login is not so very different from the link you provided.

What is it that you want to change, specifically? The wording? the layout?

Rich Boakes’ Autometa plugin automatically generates keywords for a post; it has a dictionary of words to ignore, though not user-configurable. Only problem with autometa is that it will likely require you to make a minor edit to functions.php, or await the release of WP 2.01.

I like WP-ShortStat, myself, in conjunction with Google Analytics (using boakes’ plugin) and good old Webalizer. None quite do the path analysis that it sounds like wp-detective purports to offer, but then again, it sounds like you’re not particularly interested in that.

WP Codex: Using Custom Fields: Displaying Custom Fields.

To think that someone would search for content after a) they found what they’re looking for or b) noticed the obvious end to the page is absurd.

I would be one of those absurd people, and am made very uncomfortable by the extra-long pages.

To your a) : Users will not universally hit your site seeking a single piece of data, and then depart once that goal has been achieved. In that your site is not a yellow pages type reference, but rather a “here’s what’s going on in our community” site, users are very likely to browse about to update themselves on local matters. People will continue to seek content after they’ve “found what they were looking for” because they are very likely interested in finding additional information on the same subject, and, curiously, their scroll bars tell them that there is more information somewhere toward the bottom of every page. Maybe useful links, or the missing navbar or something.

To your b) : While your light grey footers do serve to visually indicate the end of content, keep in mind that they are YOUR footers, unique to your site. Your readers are consumers of many other websites beyond asburypark.com, and will come to your site with certain expectations, based on their experiences with pretty much every other site on the Internet. What is more familiar to them: the design of this new local-issues blog, or the visual cues provided by the scroll bar which appears alongside every other window — browser or otherwise — in their entire computing experience?

Proportional scroll thumbs provide a strong visual cue about how much content a given page contains, and your artificially lengthened pages subtly say that readers MUST scroll down, at the risk of missing content. Then, of course, the content which they were “promised” isn’t there.

The only sites I know of which feature pages that are significantly longer than their content are 1) attempting to hide keywords in black-on-black as an outdated SEO ploy, or 2) badly coded in some way. One of the first things I did when looking at your site was to select-all, to see what was hiding in the empty space at the bottom. While this is likely not what the majority of your readers will think, it wouldn’t surprise me if a significant minority of them did. Not the ideal first impression.

Consider, also, the merits of a page’s scrolling *stopping* when it hits the content bottom. People who use the page-up/down keys are going to overshoot your footer, as will people (like myself) using trackpads with “side-scroll” regions, or folks who scroll using the wheels of their mice, or rely on alternative input methods. If your pages were only as long as their real content, then there would be a nice firm barrier at the bottom of each page, which prevented people from scrolling into the oblivion of your padding.

Don’t seem to be able to chmod /cache. The directory is owned by apache and it’s not my box. As I say, I’ve got the blog working at the moment by defining DISABLE_CACHE as true… my concern now is to learn what I might have done to cause the problem in the first place.

Aha! I found Podz’ post of instructions on disabling the cache and added a line to my wp-config.php My site is being served once again.

Not a long-term solution — obviously I managed to break something — but it works in the short term.

feed://madbum.com/articles/the-bum-news/feed/ should do it.

If you look at the css (https://davidhoefler.com/blog/rsc/basic.css) you’ll see how the blockquote is being styled.

Of course, if people are browsing with their font size jacked-up, it may well be that they require the larger size in order to read your text. Consider the implications for users with limited vision.

I would very much like there to be explicit instructions re: upgrading from recent releases, so that I don’t have to feel as though I must delete and re-up everything outside of wp-content. Other people feel similarly, and references to the changelog in the codex really aren’t sufficient from a user-friendliness perspective. If the canonical download’s readme says “to upgrade, delete everything except stuff that you’ve changed and then replace it with this new stuff”… well, that’s not really speaking to the masses.

Case in point: this most recent time I accidentally overwrote my custom smilies. There was no reason to overwrite wp-images for a 1.5.1.2 -> 1.5.1.3 upgrade, but I forgot about my smilies at the time and just blew them away. Had the changelog been included in the readme, and been phrased as instructions and not developer-centric information, it would have been a boon.

Given the current size of the WP download — a 360K zip — downloading the whole thing just for upgrade purposes isn’t a problem. What is a problem, however, is the confusion that comes from having all those unnecessary files. An official 1.5.1.2 -> 1.5.1.3 upgrade, like angusman’s, which didn’t contain unnecessary files, all would have been groovy.

I’m not complaining so much for my own sake … I’m more concerned for the sake of those whom I introduce to WordPress. People who don’t read support regularly or even see new release announcements. It’s one thing for me (/we/the media/etc) to give our WP-using friends a “heads-up!” when we see that security updates are available; it’s a completely different kettle of fish if, duly alerted, said people are unable or are too intimidated to successfully update for themselves.

Huh. I’ve just installed the netflix plugin and all is good.

Try looking at https://codex.www.ads-software.com/Answers-Trouble_Shooting#Headers_already_sent, in particular, the Interpreting the Error Message section.

According to the codex, your error message is identifying a problem with mynetflix.php on line 61. My copy of the plugin only has 60 lines, so it sounds like you may have introduced some erroneous whitespace when you were editing the file to add your feed url.