Momo_: you mean your.

Scollan: Dopie: i told you. pre_get_posts inside of your FUNCTIONS.PHP file you dont even touch the loop manually

Louque: Dopie:

Santai: Filipovich: Hmmmm, I’ll take a look at my .htaccess then.

Havlicek: If it’s not going to be stored in a WP table, then why make it WP at all?

Sooy: Finnjaturtle:

Bentivegna: Or better question rodney77 . why NOT have it stored in a WP table or row/

Dukeman: Bu***and, this data certainly could be stored that way, if this makes it more useable by WP — or it could be something else. This is what I’m trying to determine

Anthis: What is the best path forward, and if there are any existing plugins I can use as building blocks

Gertsema: Rodney77: well i mean logic. if you’re using WP it would make more sense to store data using WP data storage parameters, would it not?

Whetzell: Rodney77: Look at the Pods Framework plugin. Its a GREAT framework tool for custom data storage that gives you the option to easily build data inside the normal WP tables posts, users, etc or in their own tables. If you, for some reason, decide to go with custom tables Pods has a load of functionality already written for you

Ihde: Bu***and:

Denault: Rodney77: as far as how you should store it. that is up to a load of different variables and sicen i’m not on the project, I can’t give you clear direction

Hurney: Bu***and, I quess the only question would be scalability. These tables the client has are huge: 30,000 rows, 65,000 rows

Hamstra: Ok Bu***and, i’m going to check out pods right now

Cahan: Rodney77: well I mean, WP is scalable. but the questions as to how to store them depends on other values as well. what other data will he be storing? Is there going to be a blog? How much TOTAL data is to be stored including all data types? Is there taxonomy requirements? etc etc

Mantione: Rudeboy: and how are you grabbing this url?

Grand: Bu***and, there will be very little to the site other than this ability to search for vanity email addresses and order them

Freelove: Rudeboy: you also have a $query_string variable but where is that defined? This whole chunk of code is confusing to me

Funn: Https://

Stadick: Dopie: again. is_archive is going to make that custom query happen for EVERY SINGLE ARCHIVE PAGE. this includes all terms/ taxonomies, date archives, etc

Glaze: Dopie: you have to drill down in your conditional statements to the specific page you want this to happen on

Funn: I don’t want to ever see category 1307 or 1

Lenoch: Dopie: ok then. you want $query-is_main_query && is_archive is_search

Ortolano: Dopie: you ALWAYS want “is_main_query” to be true. && means “and” and means “or”

Steinle: So you want the main query AND a search page OR an archive page

Kirouac: You will want to verify is_search is the right syntax for search results pages

Mathur: Dopie: i dont know for sure. Cant remember

Madnick: Bu***and: Gees, I’m getting confused myself now! :/ Give me a mo

Gillmer: Rudeboy: give me some background. You are creating a drop down that you want to use to send parameters to a query. So give me your use case. Where is this drop down, when is the query running, what happens after the query runs?

Filsaime: I have a wide featured image that won’t crop right. So I have an alternatve version of the image I would like to use as the thumbnail on other page, How should I go about this?

Maccini: And where does this drop down exist what page? an admin screen? the front end somewhere?

Kunkel: Momo_: by “another page” you mean.?

Millison: Bu***and On pages where I loop over posts and display them

Guignard: Momo_: you mean your featured image shows up via a query on another pages throughout your site?