philor

WordPress isn’t that. If you want something along those lines, in PHP, you might try Drupal, though it’s not exactly aimed at being blog-hosting-in-a-box.

Two parts: having them able to do it, and having the menu item. If you set links_minadminlevel to 1, and then send a level 1 user directly to /wp-admin/link-manager.php do they get in, with the ability to add a link? That works fine for me.
Then, to get the menu item, since it isn’t looking at the options (yet, anyway), you’re right that you have to edit menu.txt after saving a backup copy. Did you by any chance edit it in an editor that converts tabs to spaces, before? menu.php doesn’t do much error trapping, and expects there to be a tab between the level and the filename, and the filename and the label, and if there was a space or spaces instead, it looks like bad things would probably happen. But without tabs-to-spaces, changing it to a 1 gave my test lowly luser a Links menu item.

Huh. Not mine it doesn’t/didn’t. Did you have curly apostrophes rather than single quotes, and how were they encoded in the MT export? I’m planning on spending some time hacking in there this weekend anyway, might as well look at encoding issues while I’m in the neighborhood.

Ah, gotcha, finally. You’d think someone who actually knows WP would have stepped in before now ??
wp_posts.post_category doesn’t mean anything, now that posts can have multiple categories. And category_id is wp_post2cat.category_id, a column in the post2cat table, not wp_categories.cat_ID, a column in the categories table.
Say you have a post, #75, that’s in category #7. The connection isn’t made by wp_posts.post_category being 7, because that only allows for one category. So you have a row in the wp_post2cat table, where rel_id is just an id for that row, and wp_post2cat.post_id is 75 and wp_post2cat.category_id is 7. If it’s in category #7 and category #9, you have two rows in wp_post2cat, both with post_id = 75, and one with each category_id.

CREATE TABLE wp_linkcategories (
cat_id int(11) NOT NULL auto_increment,
cat_name tinytext NOT NULL,
auto_toggle enum('Y','N') NOT NULL default 'N',
show_images enum('Y','N') NOT NULL default 'Y',
show_description enum('Y','N') NOT NULL default 'N',
show_rating enum('Y','N') NOT NULL default 'Y',
show_updated enum('Y','N') NOT NULL default 'Y',
sort_order varchar(64) NOT NULL default 'name',
sort_desc enum('Y','N') NOT NULL default 'N',
text_before_link varchar(128) NOT NULL default '

• ',
  text_after_link varchar(128) NOT NULL default '
  ',
  text_after_all varchar(128) NOT NULL default '

',
list_limit int(11) NOT NULL default '-1',
PRIMARY KEY (cat_id)
) TYPE=MyISAM;
and
CREATE TABLE wp_links (
link_id int(11) NOT NULL auto_increment,
link_url varchar(255) NOT NULL default '',
link_name varchar(255) NOT NULL default '',
link_image varchar(255) NOT NULL default '',
link_target varchar(25) NOT NULL default '',
link_category int(11) NOT NULL default '0',
link_description varchar(255) NOT NULL default '',
link_visible enum('Y','N') NOT NULL default 'Y',
link_owner int(11) NOT NULL default '1',
link_rating int(11) NOT NULL default '0',
link_updated datetime NOT NULL default '0000-00-00 00:00:00',
link_rel varchar(255) NOT NULL default '',
link_notes mediumtext NOT NULL,
link_rss varchar(255) NOT NULL default '',
PRIMARY KEY (link_id),
KEY link_category (link_category),
KEY link_visible (link_visible)
) TYPE=MyISAM;
ought to do you.

Somewhere I saw someone’s comments saying:
Link: [ ] (https:// or mailto:)
If you really want to let people who are crazy enough to expose themselves do it, it would work. I threaten to just remove my Email: input all the time, but I haven’t ever done it.

Simplify your life: just edit the four bits of information at the top of wp-config.php yourself in a text editor, and skip over install-config.php straight to install.php.

I see the rollover effect (quite cute, and well worth opening IE for the first time in weeks), but… the first step anyone will take in trying to help you work around a CSS bug will be to validate your CSS, and since the CSS validator won’t even try when your XHTML is invalid, at that point they’ll either give up, or say “please make sure you have valid XHTML and valid CSS, and still have the problem, and then maybe we’ll see.”
Please make sure you have valid XHTML and valid CSS, and still have the problem, and then maybe we’ll see.

Or, for a fuller answer, no.
An address that’s munged with either hex or URL-encoded entities will get a bit less spam, since there are still people running old harvesters that don’t know better, but it’s still vulnerable. Matt, how long would it take you to write the two lines of code to get around that munging?
The address that I’ve been munging by writing it in the page with Javascript from out-of-order parts in the JS source has gotten three spams in going on two years, so I suspect that if there are Javascript-aware spambots, there aren’t too many of them (harvesting by hand seems as likely). I’d be willing to say that accessible Javascript spamproofing is reasonably effective (though backing it up with a hardened feedback form is probably better than the throwaway address), but as WillMaster‘s happy to tell you, entity encoding doesn’t really do anything much.

Ah, just a disagreement about what counts as a line – your editor must not count blank lines. Anyway, what’s failing is
$dogs = $wpdb->get_results("SELECT DISTINCT
ID, category_id, cat_name, category_nicename, category_description
FROM $tablecategories, $tablepost2cat, $tableposts
WHERE category_id = cat_ID AND post_id = ID AND post_id IN ($post_id_list)");
So my guess would be that it doesn’t like something in the way you populated the category-related data, and for a wild guess based on what the upgrade script would have done if you had done an upgrade, I’d think maybe the category_nicename?

Only 323 lines? If you’re sure, that might be part of the problem, since I just grabbed a fresh copy, and it should be 363 lines long, with line 337 being a foreach that assumes a call to the database asking for post categories was successful. What version were you upgrading from, and did upgrade.php seem happy about what it did?

What do you have for your start_of_week option in Options/General Blog Settings? Due to a couple of what look to me like bugs that I’m emailing Matt about in a second or two, I’d say that Monday should be the only one that works, and depending on your version of MySQL, Saturday may give really odd results (possibly even your off-by-a-week results). Unless, of course, I’m completely wrong ??

Well, the W3C didn’t say that opening links in a new window is wrong, they said it was presentational rather than semantic. XHTML is intended to mark up semantics, while CSS and Javascript handle presentation. Using a rel value that isn’t defined in the rec without specifying a profile is technically wrong, but what Javascript and a browser conspire to do with the semantics of an XHTML page is completely out of XHTML’s scope.
And then there’s the other side of the coin, the one that involves actual people with actual problems. WP makes it possible to have comments in popups by deleting two characters in one file, but keeping those popups from being a miserable pain for the average user requires that the site owner find a link to an article that explains how to add some Javascript. Given that WP includes the template for the popup, I don’t see why it shouldn’t also include the Javascript to make it tolerable.

Tiptoe, through the holy war…
Since wp-comments-popup.php does open a popup (sometimes), wouldn’t the purest path that does the least harm to the most people be to include the javascript to rewrite rel=”external” links in it? You should be able to avoid forcing _blank on people who’ve been cunning enough to avoid the popup in the first place by wrapping the script in something like if (window.opener). Someone who control-clicked the popup into a new tab gets to manage their own links, someone who has a little popup window doesn’t have to figure out how to open links somewhere else that’s big enough to read in.

Do you have PHP auto-prepending something? You’re getting an XML/HTML comment surrounding a PHP comment saying “Author link to posts hack” as the first line of wp-rss.php’s output, and in XML you can’t have anything, not even a blank line or a space, before the <?xml … line. So wherever that “Author link to posts hack” line is coming from, it needs to go away.