simplistik
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: How to use substr with wp_list_categories?the echo argument in list wp_list_cateogries() would have to be set to 0 for you to be able to compare it to any thing and use it as a “variable”. otherwise it’ll just keep echoing instead.
Forum: Fixing WordPress
In reply to: understanding custom fieldsYes you can. But it looks like your condition might be wrong. Where else is $sideHeader defined?
From the initial look it seems if you should be doing something like:
$sideHeader = get_post_meta($post->ID, 'side_header', true); if ( !empty($sideHeader) ) echo $sideHeader;Forum: Fixing WordPress
In reply to: I’m going blind tring to find the error…help pleaseyou have <?php tags while you’re already in your php. your code
elseif (is_page('home')) { echo "<h2>Latest Newsletter</h2>"; <?php query_posts('showposts=1'); ?>would have to be closed out after the echo … in order for you to be able to use the <?php tag again, two solutions:
elseif (is_page('home')) { echo "<h2>Latest Newsletter</h2>"; ?> <?php query_posts('showposts=1'); ?> ...or
elseif (is_page('home')) { echo "<h2>Latest Newsletter</h2>"; query_posts('showposts=1'); ...Forum: Plugins
In reply to: [Plugin: NextGEN Gallery] Upgrade loopI just ran into this problem, it is WPMU specific. The way I got it to work was this:
- Open up the nggallery.php file and change the $dbversion on line 48 to 1.4.1
- Go back to the gallery page in the admin and when it prompts you for the upgrade, upgrade it and it should upgrade properly. This needs to be done on each blog.
- ** If for some reason it doesn’t upgrade, that probably means the database option does not exist in the database. I think this happens if you’ve created a blog during this looping issue, as it doesn’t seem to create the proper options. If this is the case you need to open up your database, go to the wp_x_options table and first see if there is an entry with the option_name ‘ngg_db_version’. If there isn’t create one and give it the option_value of ‘1.4.1’ w/o the quotes, set autoload to yes.
** You might be able to bypass step 3 if step 2 fails, by just deactivating the plug-in and reactivating it. I wasn’t able to do this cause the site that I had this issue on is an live site.
Lastly this all may be caused by only having the plug-in activated “sitewide”. It is possible that if you activate it individually on each new blog instead of making it a “sitewide” plug-in that it won’t suffer from this problem.