Danno040

The original developers have gone AWOL. They haven’t been active in over a year, and they control the SVN repo for More Fields. All this means that I doubt you’ll see a new version on www.ads-software.com.

I’ve done my best to address issues in my fork, but that’s about all I can really do.

@jedimasta

Are you sure you’ve loaded the code from GitHub? You will actually have to download the code and copy it over the More Fields that is already in your plugins folder.

I have added a “Working with More Fields in templates” to the readme.

As always, any additions you’d like to make would be welcome.

One thing to remember: you have to make sure the “Custom Field Key” is technical_specs. Otherwise, it won’t work.

Also, ankurts snippet works only if you are inside “The Loop”.

Great. I’m in the middle of something, but I will work it into the Read Me very soon.

Not a bad question.

I think they just expected you to notice that it puts all of its data as post meta info, and you would just use the normal get_post_meta functions to retrive them.

If you want to throw a quick example together, I’d be happy to add it to the fork on GitHub.

Overwriting the modified files with what?

I’ve had to make quite a few adjustments to how the admin pages work (because WYSIWYG editors weren’t working).

You don’t have to use the fork, you can always use the version hosted on WordPress. That is what is installed when you install More Fields through the WP admin.

EDIT: I forgot to say: If you have fixes, please submit them. Anything helps.

I’ve done stuff like this in the past:

<?php $custom_field = get_post_meta($post->ID, 'custom_field', true); ?>
  <?php if(trim($custom_field) != '') { ?>
    <p><?php $custom_field ?></p>
  <?php } else { ?>
    <p>No custom field set</p>
  <?php } ?>

More Fields adds stuff to the Post Meta table.

In order to use these values, you’ll have to add them to the template for your post.

Does that help?

I’ve been doing my best to continue supporting More Fields. I’ve been working hard on the WYSIWYG fields on my fork on GitHub.

Any chance it fixes some of the issues you’ve been having with the “official” version of More Fields?

If you don’t mind, try my fork from GitHub. I just removed some deprecated function calls related to the WYSIWYG editor.

I simply could not get DFW to work with multiple editors. Removing the deprecated function call to wp_tiny_mce allowed regular fullscreen to function, so I’m going to call it good. This has been committed to my fork on GitHub.

WordPress Version? More Fields version?

In the lastest version checked into GitHub, I believe I have fixed the replicating box problem.

Still researching DFW.

I just saw this in my install of WordPress. Rest assured, I’m on the case. ??