SteveYantz

bump

If you agree with this message, help keep it bumped. ~

Thank you, i must have accidentally deleted the paged variable when I was messing with it.
However, after replacing the code with yours, I still get the same result.
If I change :

$paged = ( get_query_var('paged') ) ? get_query_var('paged') : 1;

to

$paged = ( get_query_var('paged') ) ? get_query_var('paged') : 2;

I get the older posts in the result. But just the older posts.

How I can I combine the requests?
page 1 plus page 2?
or better yet, how can I request -every page?-

still looking for an answer here.

Wait, are you saying that upgrades may restructure the database tables in the future? Wouldn’t this mess up the current data in the tables? I’m thinking, they wouldn’t erase the post table to reconstruct it. They might just add or delete known columns. Which wouldn’t effect my unknown custom fields.

Right, I’ve had that problem. That’s why I backup the pages after I make the changes. So I can just paste them back in when I decide to upgrade. I’m guessing the dynamic fix for this would be creating a plugin.

I’m not quite sure how the “quick edit” queries for the data for each individual row on the post page. Trying to figure that out.

Any idea what I could use instead of “$post->custom_field” just to display the current data in the quick edit form?
Since there is no generic “$post” for this page.

Thank you. I’m trying to get some added fields I include in the post table. Inserting it into the DB works. But displaying the fields data in the form isn’t working. I’m going to have backtrack this “$screen” variable I think.

Neh?..

as a permalink? I think you misunderstood my question.
I’m trying to allow myself a new permalink structure without having the id, or postname in the permalink, and still have it work.

My structure:
https://www.site.com/futurama/1
futurama is the category.
1 is a custom field inside the wp_post’s database table.

I can get away with this structure showing up, but it returns no post, unless of course I include an id, or a postname into the structure.
My conclusion is that there’s somewhere that understands the permalink and looks for the id or postname to display a post for that permalink.
I want to go into that function and add a new one, that searches for category + custom field, and grabs the post based on the combination of these restrictions.

Thanks for the help. I figured it out. Withouth the restrictions like GROUP BY or MIN, it showed the rows exactly as expected. For some reason the GROUP BY didn’t like me organizing it by a foreign table? Simply changing GROUP BY key2.term_taxonomy_id
to GROUP BY key1.post_status, fixed the problem.

Didn’t notice the thread move. I guess this might be the best place for the answer.

Well I’m not always going to have the titles of the episodes, but I do want them if possible.
I have a custom field that’s working for the episode number.
post->post_episode

This would all be fixed if I could just add my customized field into the permalink. something like: website.com/category/episode#
Any available help for this?