peterjanes
Forum Replies Created
-
Forum: Plugins
In reply to: [Post Kinds] Quick PHP warning fixI missed the GitHub link in the readme, just saw the SVN repo on the plugin page. Looks like you made a better version of the change earlier today anyway… thanks!
There’s a mismatch between the filename and the setting that loads it. I worked around the problem by renaming
inc/class-transient.phptoclass-transients.phpand changing all of the occurrences ofDebug_Object_Transientinside it toDebug_Object_Transients.Forum: Plugins
In reply to: [Redirection] Warning messages after update to WordPress 3.5@cardoza and @kitelife and others with missing groups:
(Edited to use the solution in current SVN instead)
Instead of changing $wpdb->prepare to $wpdb->query, just remove the
$wpdb->prepare(and the closing), i.e. change$rows = $wpdb->get_results( $wpdb->prepare( "SELECT {$wpdb->prefix}redirection_modules.name AS module_name,{$wpdb->prefix}redirection_groups.name AS group_name,{$wpdb->prefix}redirection_groups.id FROM {$wpdb->prefix}redirection_groups INNER JOIN {$wpdb->prefix}redirection_modules ON {$wpdb->prefix}redirection_modules.id={$wpdb->prefix}redirection_groups.module_id ORDER BY {$wpdb->prefix}redirection_modules.name,{$wpdb->prefix}redirection_groups.position" ) );to
$rows = $wpdb->get_results( "SELECT {$wpdb->prefix}redirection_modules.name AS module_name,{$wpdb->prefix}redirection_groups.name AS group_name,{$wpdb->prefix}redirection_groups.id FROM {$wpdb->prefix}redirection_groups INNER JOIN {$wpdb->prefix}redirection_modules ON {$wpdb->prefix}redirection_modules.id={$wpdb->prefix}redirection_groups.module_id ORDER BY {$wpdb->prefix}redirection_modules.name,{$wpdb->prefix}redirection_groups.position" );My source control system didn’t pick up 3.4.2’s template.php. Works fine now.
Forum: Plugins
In reply to: [Cleaner Gallery] [Plugin: Cleaner Gallery] PHP warningHaven’t seen that behaviour, but I can’t see any way it would be related to the warning (or the fix for it): all the cleaner_gallery_get_setting method does is cache the settings that were in the database. You might want to start a new topic, though, since it’s a different bug than what you reported above.
Forum: Plugins
In reply to: [Cleaner Gallery] [Plugin: Cleaner Gallery] PHP warningYou can work around the warning by adding this at line 83 (for plugin version 0.9.2):
if ( !$cleaner_gallery ) { $cleaner_gallery = new stdClass; }All it does is create an instance of an empty object that the settings will be cached in, if it doesn’t already exist.
Replace line 170 with the second line of the patch, omitting the ‘+’ prefix. (In “unified diff” syntax, a ‘-‘ prefix indicates the original content, and a ‘+’ prefix indicates the new content.)
Forum: Plugins
In reply to: [Category Custom Fields] Plug in support – categorycustomfields@alicornea: The reason the new versions aren’t showing up on http://ww.wp.xz.cn/extend/plugins/ may be that the “Version” field hasn’t been updated in categoryCustomFields.php. There’s been no update to the Changelog in readme.txt for 1.2, either.
Also, @claudeschneider’s bug isn’t completely fixed: one of the occurrences of “width” is still misspelled as “widht” on line 74 of categoryCustomFields.php.
Forum: Fixing WordPress
In reply to: Auto update to 3.04 issue with wp super cache pluginDonncha – must be, given that I don’t remember writing or adding it! The bad plugin does kill the site exactly as described above, though—as soon as WP_CACHE is enabled the entire admin section goes to 500, with no browser output and (on DreamHost at least) no messages to the error log.
Forum: Fixing WordPress
In reply to: Auto update to 3.04 issue with wp super cache pluginI found that I had a
wp-super-cache/plugins/rebuild-if-links-updated.phpfile, apparently from an old install, which causes the admin pages to die with a 500 on its add_filter() call. (WP reports that that method doesn’t exist when WP_DEBUG is enabled, but it’s silent otherwise.) Could be the issue that’s causing the recent reports.Forum: Fixing WordPress
In reply to: Tweetbacks-Plugin generates wrong short-URLs…This patch stops shorturls from being generated for non-published posts, so it should prevent the wrong permalink from being added to the short URL list:
--- tweetbacks/tweetbacks.php +++ tweetbacks/tweetbacks.php @@ -343,7 +343,7 @@ return; } global $post; - if (!isset($post->ID) || $post->ID == 0 || $post->ID == "") { + if (!isset($post->ID) || $post->ID == 0 || $post->ID == "" || $post->post_status != 'publish') { return; } else { $post_id = $post->ID;Forum: Themes and Templates
In reply to: Problems With P2Also having the “reply” problem. I don’t think this is the root cause, but I have noted that each time I click “Reply” I get this warning in the Firefox error console:
Warning: reference to undefined property s.dataFilter
Source File: http://myhost/wp-includes/js/jquery/jquery.js?ver=1.2.6
Line: 11Forum: Fixing WordPress
In reply to: wpautop breaks block-level insI’m not sure if this is a complete fix, but it fixes the occurrence I was seeing: in function
wpautop, addinsanddelto the last two regexes that start withtable|thead|. In 2.0 they’re on lines 72 and 74, on opposite sides of the singleif ($br)condition.Forum: Fixing WordPress
In reply to: wpautop breaks block-level insI’ve been doing block-level <ins> and <del> with 1.5.x and it’s always worked, but since upgrading to 2.0 this morning it’s broken. I have XHTML auto-correction turned off, but it doesn’t seem to make a difference if it’s turned on. The behaviour happens with a “virgin” installation and with all content-editing plugins disabled too.