Child Theme CSS Not In Editor After Switch To WWW

Steps taken in move from non-WWW to WWW:

1. SETTINGS > GENERAL
2. Changed WORDPRESS ADDRESS (URL) & SITE ADDRESS (URL) to WWW version
3. Installed & activated VELVET BLUES UPDATE URLs plugin
4. Ran plugin. No links were changed.
5. Verified permalinks contained WWW
6. Added code to WP-CONFIG.PHP:

define('WP_HOME', 'https://www.powerengineeringalta.ca');
define('WP_SITEURL', 'https://www.powerengineeringalta.ca');

• This reply was modified 6 years, 1 month ago by JPecsenyicki.
• This reply was modified 6 years, 1 month ago by JPecsenyicki.

If you modified the DB, you don’t need to then set DEFINEs in wp-config.php

I see you’re using “twentyeleven-child”. And this is the CSS file that’s loading:

https://www.powerengineeringalta.ca/wp-content/themes/twentyeleven-child/style.css

• This reply was modified 6 years, 1 month ago by Steven Stern (sterndata).

I’ve commented out the two DEFINE lines. The STYLE.PHP file from the Child theme is still not loading into the edit box.

STYLE.PHP from the Child theme is visible when its URL is entered directly into the browser, and is obviously loading to apply styles to the WordPress site itself.

https://www.powerengineeringalta.ca/wp-content/themes/twentyeleven-child/style.css

However, it’s still not loading into the edit box in APPEARANCE > EDITOR.

That certainly is perplexing.

Can you give me a screen shot of what you see when you go to appearance->editor?

Screenshots are at the following link:

Child Theme CSS doesn’t display; Parent Theme CSS does display

That’s not what I asked for.

What do you see in Appearance->Editor?

Screenshot of Appearance > Editor

https://www.powerengineeringalta.ca/wp-content/uploads/2018/09/appearance-editor-screenshot.jpg

What I see is that no CSS code appears in the edit box for the Child Theme.

That link doesn’t work. Please put your screenshot in imgur.com and paste that link here.

I’m sorry, I don’t have an imgur account.

I’ll get one if it’s absolutely necessary, but before that, please try this link first:

Screenshot in blog post

Yesterday I deactivated all plugins to see if they were creating the issue…but that didn’t solve the problem.

I also temporarily deleted various security-related HTACCESS files in different folders, and that didn’t fix it, either.

• This reply was modified 6 years ago by JPecsenyicki.

OK, I have no idea why that editor is not working.

My advice is to pretend it’s not there. Download the CSS file, edit, and upload instead.

I’ve solved it. It’s working now.

The top navbar has a background gradient. Since I never fully understood the stylesheet syntax for background gradients, I had used CSS from an online generator.

The generated code inserted into my Child theme’s STYLE.CSS file was:

background: -moz-linear-gradient(top, #3a66a7, navy); /* FF3.6 */

background: -webkit-gradient(linear,left top,left bottom,color-stop(0, #3a66a7),color-stop(1, navy)); /* Saf4+, Chrome */

background: -webkit-linear-gradient(#3a66a7, navy); /* Chrome 10+, Saf6 */

background: linear-gradient(top, #3a66a7, navy);
	
filter: progid:DXImageTransform.Microsoft.gradient(startColorStr='#3a66a7', EndColorStr='navy'); /* IE6-9 */

The last line with the Internet Explorer filter may have had some kind of syntax error somewhere, and when the WordPress editor saw this it refused to load any of the Child theme’s CSS into the editor.

(When this line was commented out, the WordPress CSS editor resumed working for the Child theme. Strangely enough, when it was commented back in, the editor continued to work. I must have changed something in that line, but I can’t really report what it was.)

Just to sum up, the source of the problem was some kind of syntax error in my Child theme CSS from this line:

filter: progid:DXImageTransform.Microsoft.gradient(startColorStr='#3a66a7', EndColorStr='navy'); /* IE6-9 */

Generally, I ignore anything IE specific because people shouldn’t be using IE.

Anyways, thanks for taking the time to look into this for me. I appreciate your help very much.

And thank you for sticking to it. I’ll remember this case and hope I can pass it along to the next person with a similar issue. (What a silly choice by the editor!)