Gene Robinson

Carlia- when using jpadie’s plugin solution on 2.8 and later change 'tagsdiv' to 'tagsdiv-post_tag' and all should be well

I take that back. Using the 1.3 beta without editing it I do lose the quick-edit capability.

Applying jazbek’s edits to the more-fields-object.php and more-fields-write-js.php to either ver. 1.2.10 or 1.3 beta solves this for me using WP 2.8.1.

Here are some basic observations. This discussion and support for this plugin in general is forked between the plugin authors support forum and this one here. The last time i can see that Henrik (dev) posted on the WP plugin support forum was 4 months ago. He started a thread on his forum two weeks back from this posting to discuss the beta testing of the 1.3 beta. So all who havent already should head over and grab the current beta, test it and give some feedback, a thank you and possibly some pocket change if you can swing it and maybe it’ll help the devs work the kinks out on the new release… community right?

Quick edit works fine for me with more-fields beta 1.3 and WP 2.8.1. I’ve not been experiencing any new issues since upgrading WP from 1.8

The post metasection of the codex page for Custom Fields should help you out also check this out Perishable Press

Thanks for your patience jaz- it was totally a copy paste error using your file and/or typing the code solved the problem.

jazbek – here are the bugs ive seen since applying your edit. all of the expected behaviors occur when the plugin with your edit is diabled

Bug 1 Location: Posts>Edit or Pages>Edit or Media>Library etc.
Expected behavior: if clicking on the “post” checkbox to check all the below list of checkboxes for bulk action then all the posts checkboxes in the list below should toggle to checked. (this behavior occurs when more fields with your edit is disabled)
Problem behavior: when clicking on the “post” checkbox to check all the below list of checkboxes for bulk action none of the check boxes in the list below toggle to checked.

Bug 2 Location: Posts>Edit or Pages>Edit or Media>Library etc.
Expected behavior: clicking the screen options would reveal screen options for Posts>Edit
Problem behavior: clicking the screen options does nothing

Bug 3 Location: Posts>Edit or Pages>Edit (or More-Fields Custom Post/Page types in main nav)
Expected behavior: clicking on any toggles of the left column admin main nav items ( i.e. dashboard, posts, tools , appearance etc.) would expand the child nav list without leaving the current page
Problem behavior: clicking the toggle does nothing.

Bug 4 Location: Appearance>Widgets
Expected behavior: Widgets should be draggable in to sidebar right column
Problem behavior: Widgets aren’t draggable

the code-styling page is definitely pointing in the right direction for a fix. For the time being i’ll revert back to the workaround I mentioned. At the moment its the lesser of evils till things get sorted.

Yep same here… I’m guessing More-Fields 1.2.10 isn’t working well with the javascript changes for the screen options of the edit page in WordPress 2.8RC1.
For me anything that is in the right column on the edit page disappears (such as the publish box in the default layout) when the plugin is activated; also the show/hide capability of the write boxes are either stuck open or collapsed according to how they were set before the plugin was activated.
One simple workaround is to deactivate the plugin set the screen options to one column and toggle open all the boxes then reactivate the plugin. Not elegant but should work until the plugin comes up to speed with 2.8

Hats of the the dev this is a useful plugin for idiot proofing WP as a CMS

I’m having the same issue as versluis with a site hosted on a MediaTemple Dedicated Virtual Server. I can ftp fine via Fetch or Coda but WP 2.7 fails every time no matter what syntax I use for the hostname. I’m wondering if it has something to do with my DV service. MediaTemple is listed in the codex as a WP automatic upgrade supported host. I wonder if it was tested with MT’s Grid Service only or with MT’s Dedicated Virtual service as well.

@ versluis – what’s your hosting provider / set up?

If I’m hearing you correctly, you want to use one theme for the majority of your site and one theme just for a section of the site for a video gallery. I am suggesting you combine and edit the template files from two themes, thus creating a singular custom theme that switches stylesheets according to what page, category archive or single-post page of the site you’re on.

Forgot to mention the single pages for this category could be likewise conditionally styled in the header.php using (is_single('') && in_category('catidhere')) and the single.php will need a conditional double loop to reflect the markup changes between the themes and their respective stylesheets.

Why not one blog one database. Add the video theme stylesheet to the mainblog theme renaming it videostyle.css then edit and add the page.php template from the video theme into the mainblog theme as a custom page template. Create a page named video and assign it the custom page tempale you just added. Put a conditional statement in the header.php to switch style sheets when on that page.

<?php if (is_page('videopageidhere')) { ?>
  <link rel=”stylesheet” type=”text/css” href=”<?php bloginfo(’template_url’); ?>/videostyle.css” />
  <?php } else { ?>
  <link rel=”stylesheet” type=”text/css” href=”<?php bloginfo(’stylesheet_url’); ?>” />
  <?php } ?>

If you want the page to show posts assigned to a the category “video” integrate this code into the loop for the video custom page template to enable pagination.

<?php
$limit = get_option('posts_per_page');
$paged = (get_query_var('paged')) ? get_query_var('paged') : 1;
query_posts('cat=videocategoryidhere&showposts=' . $limit=5 . '&paged=' . $paged);
$wp_query->is_archive = true; $wp_query->is_home = false;
?>
<?php while (have_posts()) : the_post(); ?>
<!--Do Stuff Here-->
<?php endwhile; ?>

– EM HR