Vox

Worked. Ty.

Yes, I can change the meta, just not the filename. I since discovered that video files will not rename either. As another quirk, I discovered that Media Library Folders plugin can edit the filenames, but overwrites WP’s meta in the process. Uggh.

no, I am not using any audio plugins, just wordpress’s core support. To clarify, though, the plugin does everything except filenames. It will change meta, just not file name. This is the case with mp3, mid, and wav extensions. Now that i think about it, I perhaps should mention that the files at issue sit in a subdirectory (/wp-content/uploads/audio/) but so do various image files that can be renamed.

And as an amendment to that, what are the material differences between “is_category()” and “in_category()”? (Sorry, i know this to be an elementary query; it’s just that my brain is so preoccupied by other matters that my own internal processing power is diminished).

Hmm, I can’t seem to implement that and achieve the result that my inarticulate inner brain envisions. But branching from your suggestion, I found

is_category( array( 9, 'blue-cheese', 'Stinky Cheeses' ) ) 
Returns true when the category of posts being displayed is either term_ID 9, or slug "blue-cheese", or name "Stinky Cheeses".

on codex.www.remarpro.com and I’m wondering if that wouldn’t work. Any reason *not* to use “is_category( array())”?

Hey Andrew, css is now rendering as intended. I couldn’t have done it without your help. ?Un millón de gracias para ti!

OK, good catch. I removed it and the behavior improved, but then I found out why I had written that style into the img tag in the first place. For whatever reason, if img was the first element, WP nested it within an autonomously-generated p tag which caused the “<p>image</p>” to sit considerably higher than “<p>first paragraph</p>”. I suppose this relates to WP’s intended behavior whenever posts contain plain text paragraphs without markup, but it was an engineering oversight to fail to treat img as a permissible opening element.

The bandaid that I originally applied back in 2016 (which you discovered and pointed out to me) was to put the img within the p element (i.e. “<p>wrapped paragraph text</p>”). So it turns out that to prevent WP from nesting img within the autonomously-generated p was to myself nest img with its own div.

The styles are now behaving as I desired except for one thing: I can’t seem to get the img to center on a small screen. Any ideas?

On large screens I want the img to float/align right with text wrapping left and under the img, which it does.

On small screens the text wraps to awkwardly so I want the image then to appear as a block element by itself with no text wrapping. That is, as if the img were not floated/aligned (with at is, to mimic the default html/css behavior).

https://www.voxclamantisindeserto.us/2016/11/why-i-wear-skirts/

Basically–on this and another post–I want the p text to wrap the img on ample screens but not on a small screens. I would have thought that changing the img back to a block element would have worked, but no luck so far.

You know, one thing that really annoys me is inconsistency! Now that I have category_base resolved, I have noticed that the theme has another issue in the “h1 page-title” in that “category” and “tag” views have a colon delimiter but “type” (sometimes “format”) does not. Is there any way to make it display the page title as “type: xyz” ?

• This reply was modified 6 years, 11 months ago by Vox. Reason: correct terminology
• This reply was modified 6 years, 11 months ago by Vox.

I just inserted your code and it worked like a charm! Very cool, bro. Thank you.

• This reply was modified 6 years, 11 months ago by Vox.

Thank you. I can’t believe this has been an issue for so long.