almcr

this theme uses CSS grid, ensure that your browser supports that, or else it will not display the sidebar. theme does not use fallback code for browsers that do not support CSS grid, like my version of Chrome. I play around on an old XP computer and Chrome and Firefox will no longer update to the latest browser levels, so until I get a new machine, some things like CSS grid will not work on Chrome, but it will on the version of Firefox I can run. good luck, Al

I guess I would buy the suggestion that it is the obsolete browser except for one thing. it needs to switch the html/css code to display a different page, right, so why would any browser, obsolete or not, flip the current html/css code in and then immediately flip it out for something else? I doubt if it is going to do that unless it is receiving something from www.ads-software.com telling it to do that, so the mystery remains.

Al

ps it is not a big problem, just a perplexing one, why would this page do that?

• This reply was modified 8 years ago by almcr.

get_stylesheet_uri is not used in the original theme simple-grey.

the problem is that the simple-grey theme uses ‘get_template_directory_uri’ to retrieve its CSS file, and this function retrieves only the parent theme’s CSS file whether you are using it in a theme alone or you are using a child theme. if the simple-grey theme had used ‘get_stylesheet_URI’ to get its CSS file, then this function would have retrieved the parent theme’s CSS file when used in the theme and retrieved the child theme’s CSS file when used in a child theme.

need to figure out some way to bypass the enqueue to the parent theme’s CSS file when using a child theme. hard to do when the child functions.php is processed before the parent theme’s functions.php file.

the theme needs to be updated to get the CSS file in a standard fashion that would allow you to code up a basic child theme. I do not want to use the theme without somehow setting up a working child theme.

Al

because the order of processing functions.php is child then parent theme,
the normal way (see codex re Child Themes) to code the enqueues for the CSS files is to use a get_template_directory_URI() in the child theme’s functions.php, which retrieves the absolute path to the parent theme’s directory and the CSS file coded in that function from the parent theme when this code is used in the child theme’s functions.php, and
then use a get_stylesheet_uri in the parent theme’s functions.php, which retrieves the current theme’s stylesheet, in this case, the child theme’s style.css, even though this code is contained and executed in the parent theme.

the order is important as this creates the HTML code that will access the CSS files in the sequence that is best, the parent theme’s style.css and then the child theme’s style.css.

however, the theme “simple-grey” enqueues a CSS file called “/css/simple-grey.css” and does not enqueue the CSS file “style.css” at all.

Because it uses the “get_template_directory_uri” function in the theme to get the CSS file it wants to use, then when you set up a child theme which uses the get_template_directory_uri function to enqueue the CSS file it automatically defaults to using the parent theme’s CSS file (which works OK) and
then the parent theme uses the same function to enqueue the CSS file which also automatically defaults to using the parent theme’s CSS file (which does not work OK).

somehow the second enqueue should point to the child theme’s CSS file, not the parent’s CSS file. can you change the way that a theme enqueues its CSS files?

hope this explains things,
and the challenge of creating a child theme for this theme can be overcome

Al

I offered a solution in this post:
https://www.ads-software.com/support/topic/how-to-change-spacing-above-nav-menu-get-rid-of-page-titles-and-logo-questions/

use a child theme, add CSS code to style.css in the child theme to do what you want and do what you want with the top space at the top of any page

Al

have you tried what I suggested above?

changing the amount of space between different elements is what that takes care of. it is advised that you use a child theme of your theme. in this case, it does look like you are using the twentysixteen theme.

set up a child theme and play around with the style sheet CSS, you need to identify the CSS code that is setting the spaces between one item and another, but using the Chrome inspect function, that is easy to do. any changes you make in the CSS code in the child theme stays with the child theme. if you go back to the original theme, then they disappear.

good luck

Al

one other thing: do use a child theme and make your code changes in it.

Al

I would say: refresh your page, if you have eliminated the code to display the h1 title, then there is no way that they will show unless you are using the wrong HTML code to show them.

confirm to yourself using the Chrome/FF inspect function to verify that you are actually using the code that you think you should be.

Al

in post #1, the author went to underscores.me and generated his new theme called simple-portfolio and then modified that over the next posts.

if you look at twentysixteen, it looks like they have generated a new theme by going to https://underscores.me and generating a theme called twentysixteen. they then tweaked it and eventually published it, many of the themes have a note in the theme info at the top of style.css referring to underscores.me. twentysixteen does not but others do.

there is no point in re-inventing the wheel every time you want to create a theme, use a starter theme like underscores to get a long way on the path to a new theme.

Al

OK, that is what I figured.

still different to not see closing tags on a template file, other than functions.php. I noticed it in some of the template files used in “underscores”.

Al

pmmueleer: “your account has been suspended” comes up when I try to go to your link

A child theme is so simple to create. As the Codex says, create 2 files in your child theme folder, one called functions.php and the other, style.css. Copy the code given in the codex into each of these files, make sure you update the theme info to match the one you are making a child theme for, and then activate it. No more worries about changes to the original theme.

It is important to note that in child themes template files like header.php and index.php can be copied into the child theme and updated as you wish. As for the functions.php file in the parent them, you cannot just copy it into the child theme and go, it won’t work. Because the child’s functions.php file is read before the parent’s functions.php, this complicates its usage in a child theme.

All in all, if you are using a theme from the www.ads-software.com repository, do use a child theme of it. When the theme changes, as it inevitably will, you will not lose your changes and would only have to make updates to your child theme if something changes in the parent theme that you are changing in your child theme.

Al

There are 2 chunks of code, one for the menu and one for the header image enclosed in “<?php” and “?>” tags, just switch them.

you may have to make updates to the CSS after doing this.

please do this in a child theme, leave the code in the theme twentysixteen alone. copy header.php into your child theme and modify it.

Al

To change the amount of white space, in Chrome, I just right click on the area and then, using the inspect function, look at the CSS code affecting the variable you are interested in. I put this CSS code in a child theme style.css to change various spaceings:

“.site-header {
padding: 1.0em 7.6923% 1.0em; /* 2.625em 7.6923% */ }
.site-branding {
margin: 0.875em auto 0.875em 0; /
* 0.875em auto 0.875 auto */ }
.site-main {
margin-bottom: 2.0em; /* 3.5em */ }
.site-main > article {margin-bottom: 2.0em; /* 3.5em */ }
.site-footer {
padding: 0 7.6923% 1.75em; /* 0 7.6923% 1.75em; */
}

/* screen size >= 710px */
@media screen and (min-width: 44.375em) {
.site-header {padding: 1.5em 7.6923% 1.0em; /* 3.9375em 7.6923% */}
.site-main {
margin-bottom: 3.0em; /* 5.25em */ }
.site-main > article {margin-bottom: 3.0em; /* 5.25em */ } }

/* screen size >= 910px */
@media screen and (min-width: 56.875em) {
.site-branding {margin: 0.875em auto 0.875em 0; /
* 0.875em auto 0.875 auto */ }
.site-footer {
padding: 0 4.5455% 1.0em; /* 0 4.5455% 3.5em; */ } }

/* screen size >= 985px */
@media screen and (min-width: 61.5625em) {

.site-header {
padding: 2em 4.5455% 2.0em; /* 5.25em */ }
.site-branding {
margin-top: 1.3125em; /* 1.3125em */ margin-bottom: 1.3125em; /* 1.3125em */ }
.site-main {
margin-bottom: 3.0em; /* 7.0em */ }
.site-main > article {margin-bottom: 5.0em; /* 7.0em */ } }”

Al

ps hope I have inputted the CSS code correctly, if not, then I stand corrected.

I agree with points made above.

this theme was added to the main theme repository, and at one time, did work with the latest version of wordpress (4.3.1) but has been changed (in functions.php) to require 4.4. 4.4 does not even exist as a production version and is a beta/test version only.

I don’t understand why the theme was added and used by many users and then changed in this way. obviously it is going to break websites that use it, change it back, and if the requirement for 4.4 is needed, then bypass the condition in the theme or at least remove it from the repository until the level of wordpress matches the theme.

Al

think about what 2015 would look like without the sidebar, just a bunch of posts without any theme title or navigation.

the design of the theme itself does not lend itself well to a full-page display. the sidebar info is really vital to the theme and would need to be displayed somehow on a full page display, otherwise you will lose the theme name and navigation menu info. when you make a full page display on any other theme, this info is displayed by default, all you are dropping is sidebar info.

Al