wperic

[Ignore–I edited the previous.

I was actually able to log into a file editor on my hosting site and fix it. But to do it by FTP I’d suggest this:
0. Connect to WP hosting site with FTP. Either make copy there if Filezilla does that or download the corrupted file and make a backup on your desktop (or wherever).
1. Make a copy of the corrupted file (corruptedfile-copy.php or whatever).
2. FTP the original corrupted file back to your desktop with Filezilla.
3. Fix the original on your desktop.
4. FTP the original back to your host, choosing to overwrite the original (that’s why you have the copy up there–insurance).
5. See if the problem is fixed.

I also discovered that if you use the back button on your browser right away when you get the error message, it does seem to take you back to the guilty page in the WP editor.

Curioser and curioser.

I just had to reboot my computer and when I restarted Firefox and went back to the site, it was formatted correctly.

Whatever. WP usually seems to do a good job of updating and not getting hung up by what’s in the cache, but maybe something like that happened this time.

Also, mimicing some other divs in the neighborhood I had changed the css heading for this id to “div#content div#category_art.” I don’t know why that would make a difference, given my understanding of how IDs work in css.

Thanks to all.

The site is not public yet. I just set up a pastebin acct. Should I post the entire child theme style.css and the resultant page code (html) for one of the category archive pages?

Nope. That didn’t make any difference.

@alchymyth: will try that.
thanks.

No. That’s not it. I was looking in the wrong place.

Hold the press. I think I see what I did–forgot the “id= ” bit.

Duh! Sorry.

Everything else is styling fine. It’s just the styling for #category_art that’s not applying.

It’s gone–I did go in an fix the code via FTP. Basically I had missed a semi-colon and gotten some of the nested quotation marks wrong. Once I fixed those by going the long way around, I’m OK. But I’m still thinking there should be a way in from within WP.

Thanks.

Oops. Once I logged in locally and changed WP address and Site address from localhost to the IP address, it’s working OK.

OK.
Thanks.

Resolved.
Changed the WP directory owner/group to apache/apache and the updates work. Still mysterious about how to use the ftp option on localhost if the ownership of the WP directory isn’t right, but that’s not important now.

I think I finally figured it out–need to also allow a specific override in httpd.conf for the DocumentRoot directory.

Can anyone help me on this? My WP is at Document Root/dsescaleWP.

I’ve got “day and name” permalink setting chosen, yet WP assigns a different permalink without the day and name when I create a page. However neither the assigned permalink nor the “correct” on will open the page:

The requested URL /dsescaleWP/test-page-2/ was not found on this server.

I’ve got the .htaccess file and it’s being written to:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /smashing/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /smashing/index.php [L]
</IfModule>

# END WordPress

I believe mod_rewrite is on, since the line “LoadModule rewrite_module modules/mod_rewrite.so” is uncommented in httpd.conf.

What else do I have to do to get permalinks to work right?