RossB

Aha! Well, that appears to account for the misunderstanding re the child theme, WPyogi. Glad to have this befuddling (to me) conundrum explained away. It had me well and truly beat.

Thanks for your response, Krishna. Yes, it’s true I didn’t return to the site until 7 hours later – I went to bed just after posting.

I can’t explain the validation errors if you saw them picked up in relation to the orig Twenty Twelve theme. I really don’t get how that could have happened because I have never modded anything directly on the orig theme. I can only think that some sort of corruption has taken place (when I accessed some of the original theme files to copy them and move them over to my child theme, perhaps?). I’ve done this several times at different points during this design project, which is now several months in duration.

I was aware that I had multiple validation errors in my child theme pages, and had the task of fixing them marked down as a final step before migrating the ppredesign site over to the domain of the original site (www.perthpunk.com). I was perturbed when I was first made aware (some weeks back now) of those validation errors, as many of them are html errors like unclosed paragraphs.

I did post here asking how these sorts of errors could arise when I always work in the text mode in the page editor, but got no response. As you’d obviously know, there is no html visible on the page editor for things like new paragraphs: I just hit the enter key and voila – a new para. So, wouldn’t that mean that those types of validation errors are somehow occurring in the html part of the original theme? Could that explain why it appears that the original theme has been modded, perhaps?

Just scratching around in the dark of my technical ignorance seeking an explanation, because no one is more baffled by this than I.

In lieu of your post above, I wish to apologise for declaring you in error in your statements about my modding the original theme directly. If the errors are there, then of course I can see why you arrived at such a conclusion. I still can’t explain it in terms of any deliberate modding of mine, though.

And I still don’t understand why my site showed up as the original theme, and not the child theme I have been using all along. Last time I switched briefly to the original theme was in response to a post of esmi’s when she suggested I do so to ascertain whether a content center-alignment problem I was having also occurred with the original theme (it didn’t). I distinctly recall the switch because my many mods to the child theme instantly disappeared, and the site looked a complete mess. I was pretty happy to switch straight back to the child, I can tell ya!

Anyway, thanks again for your explanatory post. I certainly believe that you are here to help. This has been my glad experience with the vast majority of members and moderators, with WPYogi being an outstanding example on this and multiple other occasions. Not so sure that this is the case with all, though…to wit, I felt like I’d stumbled into a virtual version of the mad hatter’s tea party at one stage on this thread (absolutely not referring to you!).

And if you have any observations re these damned html errors like the paras missing closes, I’d be very interested. And I would still like to know where I should go – what file – to correct html errors…googling for the answer to this has been fruitless so far.

All the best to you, and I’m sorry about any unpleasantness on my part.
Ross
PS: Will any errors in the original theme be overwritten during the next upgrade? I suppose not, if the html section pertaining to pages and posts is somewhere among the files in the orig theme.

Look, this is offensive, having my word questioned on the basis on no evidence whatever – you are going purely on heresay of a volunteer moderator that I say has made an error.

I have NEVER modded the original Twenty Twelve theme – NEVER. I created the child theme from the start, and have done all my mods only on that. And I have not had the original theme reactivated for months. Fact.

I find the attitude on this thread very strange. I do not understand it.

Can someone please take me at my word and respond usefully? I have always tried to observe etiquette here, and be respectful, and ask that others afford me the same courtesies – including moderators.

If anyone doubts my word, I am happy to reactivate the original theme at a specified time so you can check for yourself whether it has been modded in any way. It HAS NOT!

Huh? I said I was using a child theme and I am! And it’s activated! And I certainly have NOT modded the original theme directly. Beats me how you managed to come out with an incorrect observation like this. You couldn’t have been looking at the URL I posted, and if you were, seems you somehow saw something that wasn’t there!

If you check my recent posts – and there have been quite a few – you’ll note that I have been using a child theme all along, and only making mods to it. I am well aware, and have been for years, that it’s a no-no to directly mod the original theme.

I have tried modding the child theme content.php and comment.php pages using recommendations on WP Support, but none of the things I’ve tried have worked. Hence this post.

Can anyone help, please?

Gulp, I am easily freaked out by this stuff, WPYogi – not your fault! I greatly appreciate your help.

Fixed the missing colon – that, and deleting the Nextgen plugin, got rid of 3 errors and 3 warnings!

I’m sure I added that second curly closing bracket to close off two media queries further up the page, but I’m too confused to see why I put them in now. Will go back over my notes and see if I can locate the advice I got re that. Pretty sure that second closing bracket made a difference I wanted to something….but can’t recall what!

I have to go out now, too, so will get back to studying my notes ASAP.
Thanks again for your fantastic support.

Cheers
Ross

Thanks, WPYogi. Comment tags now added to my slowly growing coding education! I assume you use these tags in this current situation – to see the effect of disabling specific code without deleting it?

OK, so commenting that code out DOES center the content alignment, but it messes up a lot of other stuff. eg: the title and header from the home page suddenly appears at the top of every other page (with the header image aligned left instead of center!) + CSS boxes I’ve put around text on a couple of pages disappear.

So, I guess the question now is, how do I center-align the content area without messing up a whole lotta other stuff? If you have any suggestions on this, would be most appreciative.

Cheers
Ross