Custom Fields

Whoa.

So I have a place for the plugin, although I’m not sure the plugin DID anything, but I have to manually write “Listening to: Whatever” every entry. But there is a dropdown menu to the side, it just does nothing… weird? Or normal?

You *can* choose the name of the field from that drop down list if you’ve made a custom field with that name already. And then you write the value in the value box. Be sure to either “Add custom field” or save a post.

The plugin will allow you to pick out the specific fields you want to show, but if you don’t have any extra fields (as I mentioned, plugins may add those) you can use the_meta tag.

Kay, I’m going to give an entry a go and see if this works. Thank you all for being so …explainy! ??

Okay, I have it in there and it works, but the fields come off in one line instead of a little aside or something. A la:

Listening To: Whatever Reading: Yadad Writing: ETc.

I’d prefer:

Listening:
Reading:
Whatevering:

This also sort of hinges on getting 1 entry per page & the bloody next/previous thing to work, so…any help with both would be good.

Are you using the_meta? Or the plugin’s output?

How does it mess with paging and entry per page?

It doesn’t mess with it, I just can’t figure out how to get 1 entry per page & previous/next links.

And I put a meta thingy into the code… I don’t think I’m even using a plugin.

Ok, you need to have “posts paged” selected in Options > Reading > Front page: show the most recent.
The prev/next links are done with <?php posts_nav_link('separator','previous','next'); ?>, write the values you like instead of separator, previous and next. Place the code outside the loop, i.e. somewhere after <?php endif; ?>

As for the custom fields, they are in a list and the list has a class specified to it, post-meta. You have .meta li, ul.post-meta li { display: inline; } in your style sheet. Remove the ul.post-meta li.

Thanks ?? Unfortunately, now I have an even BIGGER problem than the meta stuff.

Parse error: parse error, unexpected T_ENDIF in /home/katehack/public_html/wordpress/index.php on line 118

Whoa.

do you have any text editor where you could see the line numbers and tell what’s on that line (and a few lines around it)? There’s something wrong with the <?php endif; ?>. You did have that in the index file already? That you didn’t insert it? Cause I don’t remember what the original WP index was like so I don’t know if I’ve modified mine “too much”

I plugged it into Dreamweaver and the line in question is the line you said. The <?php endif; ?> ….I had it in there originally, I never added it. I’m not sure what the bloody heck I did.

and you put the posts_nav_link after that endif tag?

I did. I removed them for the time being. I had the previous/next tags working for …3 seconds. Then I did SOMETHING (I have NO idea what) and it …went dead.

What about opening a new thread for the new problem? A lot more people will be willing to help if the problem is adequately described, and the forum post title is meaningful.

I created https://codex.www.ads-software.com/Using_Custom_Fields to help users understand custom fields better. Please add to it, and make it better ??

Here’s a snippet of the original WP index with the posts_nav_link added:
<?php endforeach; else: ?>
<p><?php _e('Sorry, no posts matched your criteria.'); ?></p>
<?php endif; ?>
<p align="center">
<?php posts_nav_link(' a€?? ', __('?? Previous'), __('Next ??')); ?>
</p>
</div> <!-- content div -->

Oh, God, I LOVE YOU.

Thank you SO much, Minna, you’ve been a brilliant help to me.

Please, if there’s anything I can do for you in the future, do not hesitate to ask!