prwood
Forum Replies Created
-
It’s important that users are not redirected to /content/ when they go to /. We are serving additional content outside of WordPress using other applications under other subdirectories, and so rather than putting all of WordPress right at the document root, we want to restrict WordPress to handling only requests for content under /content/, with the exception that ‘/’ should also be handled by WordPress.
@aestheticdesign – Thanks for the reply. I don’t want to 301 redirect the user to /content, I actually want to serve the homepage from /. All other content on the site would be served from /content/*.
Forum: Plugins
In reply to: [JSON Data Shortcode] How to display values in ArrayI’m also interested in accessing array values. The JSON I’m working with contains a number of items in an array, and I don’t see any way currently with this plugin to access parts of an array.
Forum: Themes and Templates
In reply to: Tweaking the new gallery feature in 2.5on line 382, i changed
$url = get_attachment_link($_post->ID);
to
$url = wp_get_attachment_url($_post->ID);
Ah, thanks! I’ve been wanting to figure out how to do this. I wish there were a nicer, less hack-ish way to go about it, but this will work for now. Couldn’t figure out how to do it with a plugin.
Forum: Alpha/Beta/RC
In reply to: Gallery customizationI’d love to see some more documentation, particularly as to how Matt does his new gallery on ma.tt. I know the old gallery was done using the Gallery package from gallery.menalto.com, but the new one is done using Gallery 2.5’s internal gallery function.
I’m having a heck of a time figuring out how to customize the gallery for my own needs. Seems like I’d have to gut a lot of the WordPress code to do it. For example, I’d like the thumbnail images to link directly to the full sized version, rather than to an attachment page and then to the full sized version.
Forum: Installing WordPress
In reply to: ‘duplicate key’ errors when upgrading from 2.2.3 to 2.3(Should have said I tried an upgrade from 2.2.3 to 2.3.1-RC1, not 2.3.1… just because I was impatient)
Forum: Installing WordPress
In reply to: ‘duplicate key’ errors when upgrading from 2.2.3 to 2.3Ok, so I tried an upgrade from 2.2.3 to 2.3.1. I dropped the terms, term_taxonomy,a nd term_relationships tables which the previous upgrade had created, then ran through the upgrade script.
After churning for a bit, I was left on a blank screen with no options to continue. So I reloaded the upgrade script, which again prompted me to upgrade the database. At that point, I got the same database errors that I got before.
So it seems that on the first run through, there is something that doesn’t finish cleanly. Then, when I try to re-run it, it’s unable to get past inserting the data into the terms tables since that’s already been done.
Any thoughts?
Forum: Installing WordPress
In reply to: ‘duplicate key’ errors when upgrading from 2.2.3 to 2.3Yeah, I think I’ll just wait for 2.3.1. We’ll see what happens then…
Forum: Installing WordPress
In reply to: ‘duplicate key’ errors when upgrading from 2.2.3 to 2.3Not that I can recall. As far as I know, I’ve only run production versions of WordPress.
Forum: Installing WordPress
In reply to: ‘duplicate key’ errors when upgrading from 2.2.3 to 2.3Here’s an example:
WordPress database error: [Duplicate entry '1' for key 1] INSERT INTO www_terms (term_id, name, slug, term_group) VALUES ('1', '1_Uncategorized', 'uncategorized-3', '1') WordPress database error: [Duplicate entry '1-category' for key 2] INSERT INTO www_term_taxonomy (term_id, taxonomy, description, parent, count) VALUES ('1', 'category', '', '0', '0') WordPress database error: [Duplicate entry '66' for key 1] INSERT INTO www_terms (term_id, name, slug, term_group) VALUES ('66', 'Site Updates', 'site-updates-2', '1') WordPress database error: [Duplicate entry '66-category' for key 2] INSERT INTO www_term_taxonomy (term_id, taxonomy, description, parent, count) VALUES ('66', 'category', '', '0', '74') WordPress database error: [Duplicate entry '67' for key 1] INSERT INTO www_terms (term_id, name, slug, term_group) VALUES ('67', 'Food', 'food-2', '1') WordPress database error: [Duplicate entry '67-category' for key 2] INSERT INTO www_term_taxonomy (term_id, taxonomy, description, parent, count) VALUES ('67', 'category', '', '0', '32')There’s no way to ignore it as far as I can tell; going back to wp-admin just takes me back to step 1, and the failed database upgrade repeats again…
I’m having this same issue, trying to upgrade from WP 2.2.1 to 2.3. I get a whole page of errors about duplicate entries for key 1 and 2, just as the original poster did. I’ve tried restoring my wordpress code and database, as well as disabling all plugins. Thus far I haven’t figured out how to get past these errors to complete the upgrade.
Any hints?
Forum: Themes and Templates
In reply to: Indicating moderation in popup commentsP.S. I did try replacing the call to get_approved_comments with a direct wpdb call that included non-approved comments, but this doesn’t work because it just shows ALL of the comments to EVERYONE:
// $comments = get_approved_comments($id);
$comments = $wpdb->get_results(“SELECT * FROM $wpdb->comments WHERE comment_post_ID = $id ORDER BY comment_date”);Can anyone help put this puzzle together?