Forum Replies Created
-
I’m still lost! In my test site, I upgrade again the graphene to 1.2.1
I do not understand … I believe everything is related in some way, but while I do not understand what’s happening I do not know where to get start to correct …
Leaving the differences in the CSS of my child theme to the graphene theme in the side for a while (if that is possible), the behavior of the child theme does not obey the settings of the admin panel.
in Header display options I choose
Link header image to front page
Disable feature image replacing header image
hide the top bar
and search box location is placed in navegation bar
In columm options
I choose 1 columm in the right
In post display options I check
Show excerpt in front page
and hide post tags (actualy, in my real child, this is not market. I change the code in the loop.php to only show tags in single pages and not in the front page, but to make easy just to see the effects, here I chose hide at all)
And this is how the child looks like (with child theme and graphene 1.2.1) http://www.drquem.com.br/blog/
when need looks like this one (with child theme and graphene 1.1.4) http://www.rederpg.com.br/wp/
Like I said, in this moment, I’m not focus on the fact the almost ALL thins that I wrote in the CSS is not being respected… but in something bigger: the setting of the theme, when using a child, is not being respect…
I don’t have columm, I don’t have link in the header, the top bar is showing, the search is in the wrong position… The only thing that is working is not showing the tags (and this one is the only that is not my real intention… what I want is not show tags in the front page and show in the post page… )
Like I said, I’m totally lost!
PS: I did not make any changes on funcions.php at this momment, but changed a little the following files:
loop.php
header.php
footer.php
🙂
But if helps, my actual CSS (graphene 1.1.4 , my child theme, WordPress 3.1) working nice on my site right now. 🙂
It’s a little messy because we did a lot of last minute changes and have not had time to clear the codes yet.
I’m not sure if will work post in this way, but…
/*
Theme Name: RedeRPG
Description: Child theme for Graphene (de Syahir Hakim http://www.khairul-syahir.com ) made by Adriana Almeida e Fábio Birous
Author: Adriana Almeida e Fábio Birous
Author URI: http: //www.rederpg.com.br
Template: graphene
Version: 2.2.0
License: GNU General Public License, v2 (or newer)
License URI: http://www.gnu.org/licenses/old-licenses/gpl-2.0.html
*/
@import url("../graphene/style.css");
body{
/* background:url(images/sprite_h.png) left -196px repeat-x #4a4949; */
background:url(images/bg_g.png) repeat #000 fixed;
}
#content-main {
padding: 0 0 0 8px;
}
#top_search button{
background:url(images/search.png);
}
#header{
height:115px;
margin:0 0 5px 0;
-moz-box-shadow:none;
-webkit-box-shadow:none;
box-shadow:none;
}
#header_img_link{
height:115px;
}
.featured_slider{
margin-bottom:15px;
padding-top:10px;
padding-bottom:5px;
}
.post .date{
background:url(images/calendario.png) no-repeat;
height:80px;
width:58px;
margin:-2;
}
.post-meta ul{
background:url(images/dado-li.png) no-repeat;
}
.banner1 {
padding-left:12px;
}
.banner2 {
float:right;
padding-right:10px;
}
h2 a, h2 a:visited, a, a:visited {
color:#600;
font:normal 20px;
}
.entry-content h6, .comment-entry h6{
font-size:11px;
text-align:right;
}
.entry-content h3, .comment-entry h3{
font-size:16px;
}
.entry-content ul li{
list-style-image:url(images/dado-li2.png);
margin-bottom:3px;
}
blockquote{
background:url(images/blockquote.png) no-repeat #e1e0e0;
text-align:justify;
line-height:20px;
color:#474747 !important;
}
table td, table th, table tr{
font:normal 12px;
line-height:20px;
text-align: justify;
}
.post-tags{
width:500px;
float:left;
font:normal 11px tahoma;
line-height:16px;
margin-top:5px;
color:#929292;
}
.sidebar h3{
width:243px;
font:normal 16px/36px arial;
padding-left:12px;
margin:-15px 0px 3px -12px;
color:#ab1c11;
background:url(images/sidebar.png) no-repeat;
}
#nav{
height:46px;
background:url(images/sprite_h.png) left top repeat-x #4f0310;
width:100%;
border-bottom:3px solid #fff;
padding-top:12px;
}
#footer{
background:url(images/sprite_h.png) left -117px repeat-x #000;
height:49px;
position:relative;
-moz-box-shadow:0 -3px 7px 0 #000000;
-webkit-box-shadow:0 -3px 7px 0 #000000;
box-shadow:0 -3px 7px 0 #000000;
}
.block-button, .block-button:visited{
display:block;
font:normal 11px arial;
text-decoration:none;
padding:2px 5px 2px 5px;
color:#fff;
margin-top:5px;
position:relative;
border:1px solid #43020e;
float:right;
-moz-border-radius: 1em 2em 1em 2em;
border-radius: 1em 2em 1em 2em;
-webkit-border-radius:1em 2em 1em 2em;
-moz-box-shadow:0 0 5px #4a0310;
-webkit-box-shadow:0 0 5px #4a0310;
box-shadow:0 0 5px #4a0310;
background:#620919;
background:-moz-linear-gradient(#461515, #911616);
background:-webkit-gradient(linear, 0 0, 0 bottom, from(#461515), to(#911616));
background:linear-gradient(#461515, #911616);
-pie-background: linear-gradient(#461515, #911616);
}
.block-button:hover{
text-decoration:none;
color:#fff;
cursor:pointer;
background:#1C5FA5;
background:-moz-linear-gradient(#911616, #461515);
background:-webkit-gradient(linear, 0 0, 0 bottom, from(#911616), to(#461515));
background:linear-gradient(#911616, #461515);
-pie-background: linear-gradient(#911616, #461515);
}
.comment-link{
float:left;
padding-top:5px;
text-align:right;
}
.comment-link a, .comment-link a:visited{
font:normal 12px arial;
}
.entry-content .excerpt-thumb{
float:right;
margin:5px 5px 0 3px;
}
#content{
background:#e3e3e3;
border-top:21px solid #e3e3e3;
padding-bottom:20px;
text-align:justify;
}
.post{
width:573px;
padding:25px 18px 20px 24px;
background:#fff;
margin-bottom:5px;
text-align:justify;
-moz-border-radius:1em;
-webkit-border-radius:1em;
border-radius:1em;
}
.entry-footer{
border-top:1px solid #e3e3e3;
margin-top:5px;
clear:both;
}
.comment-link{
float:right;
text-align:right;
padding-top:1;
}
.add-this, .add-this-right{
float:left;
padding-top:1px;
}
.add-this-right{
float:left;
padding-top:0;
}
.adsense_single{
text-align:center;
background:#e3e3e3;
}
#comments li.depth-1{
background:#e9ecf5;
padding:18px 0 10px 20px;
margin-bottom:10px;
-moz-border-radius:1em;
-webkit-border-radius:1em;
border-radius:1em;
}
#commentform{
background:#eee;
width:615px;
padding:18px 0 15px 0 !important;
margin-bottom:10px;
-moz-border-radius:1em;
-webkit-border-radius:1em;
border-radius:1em;
}
#container {
background-color:#fff;
}
.slider_post h2 a, .slider_post h2 a:visited {
font:normal 20px georgia;
letter-spacing:-1px;
}
a:hover {
color: #900;
text-decoration:underline
}
#LoginWithAjax table td, #LoginWithAjax table th, #LoginWithAjax table tr {
text-align: left;
border: none;
font-family: tahoma;
padding: 2px 5px;
}
#LoginWithAjax table tr {
background: none;
}
#container h1, #container h2, #container h3, #container h4, #container h5, #container h6 {
color: #c90;
}
.sidebar h3 {
background: -moz-linear-gradient(left top, #660000, #330000);
background: -webkit-gradient(linear, left top, left bottom, from(#660000), to(#330000));
background: linear-gradient(left top, #660000, #330000);
background: -pie-linear-gradient(left top, #660000, #330000);
border-bottom: none;
color: #fc3
}
#nav {
border-bottom: none;
}
#content {
border-top: none;
}
.home #content {
background: url("images/dragao.jpg") no-repeat scroll 0 0 #E3E3E3;
}
.home #sidebar_right {
margin-top: 341px;
}
.featured_slider #slider_root {
margin: 42px auto 0;
-moz-border-radius: 5px 5px 5px 5px;
-webkit-border-radius: 5px 5px 5px 5px;
border-radius: 5px 5px 5px 5px;
-moz-box-shadow: none;
-webkit-box-shadow: none;
box-shadow: none;
}
.featured_slider {
background: none;
right: -258px;
margin-bottom: 46px;
-moz-box-shadow: none;
-webkit-box-shadow: none;
box-shadow: none;
}
div#vs_main2 { /* alinha o slider vertical de imagens da galeria */
margin: 0 auto;
}Hi
Sorry, I put fire in the discussion and then disappear. But I was working on other things and decided to take a break on the issue of upgrading the theme. Besides, for some reason I have not received email notifying me of new posts in the discussion. Luckily I came here to look! 🙂
I’ll read everything you wrote with calm. I see I have to make changes in the function.php (in the previous version of the theme, changes in heather worked only with a change in CSS, but no problem, is a easy change! 🙂 ).
I am pretty sure that my child theme was created right because I follow the parameters in a tutorial for creating themes child by WordPress itself, but I’ll also take a look at your post about this matter to see if there are any differences in the design process suggested by WP and for you.
As the next few days here we have a big holiday, so I don’t know if I can test everything and give feedback if it worked, but I thank you the work in helping us find solutions and as soon I could test, I’ll give you a feedback! 🙂
PS: If someone wants to see, screenshots from the test server (My theme with the new Graphene):
http://www.rederpg.com.br/Testsite-01.jpg
(and Testsite-02.jpg and Testsite-03.jpg)
I mark in green all things that I change in my theme and now is somehow wrong. All the choices of graphene is marked to work as I want (2 columns, hide top bar, etc) and all is working well in the old graphene (as you can see in my real site)
DONE! Sorry for all this messages! 🙂 🙂 🙂 🙂 🙂
I KNOW that the theme author is not responsible for the changes we make on child themes and had other priorities. But one of the great advantages of WP is precisely the possibility to change themes in a sort of large collaborative work. Although I changed a lot the original theme (in some points, major changes, in others, not so much), I wanted to leave the credits for the original theme, just for respect and admiration to those who took the trouble to mount the base from which I created my theme …
so I really would love some support, at least to give us a direction where we can begin work to re-make our themes compatible with the original theme! One hypothesis of what might be causing this incompatibility might already be pointing me in the right direction to solve … Unfortunately, I am not able to imagine what could be.
Moreover, the support that we are asking is not to solve something that went change and them go wrong. But something we changed, worked perfectly and now with the update, stopped working. So we know that works, but something in the new theme is overriding the choices of the child theme. Even more when we see that even small changes, such as the Das Capitoline made, generate the same problem …
I hope I have not missed much in my writing in English and you are able to understand what I wrote ….
I KNOW that the theme author is not responsible for the changes we make on child themes and had other priorities. But one of the great advantages of WP is precisely the possibility to change themes in a sort of large collaborative work. Although I changed a lot the original theme (in some points, major changes, in others, not so much), I wanted to leave the credits for the original theme, just for respect and admiration to those who took the trouble to mount the base from which I created my theme …
so I really would love some support, at least to give us a direction where we can begin work to re-make our themes compatible with the original theme! One hypothesis of what might be causing this incompatibility might already be pointing me in the right direction to solve … Unfortunately, I am not able to imagine what could be.
Moreover, the support that we are asking is not to solve something that went change and them go wrong. But something we changed, worked perfectly and now with the update, stopped working. So we know that works, but something in the new theme is overriding the choices of the child theme. Even more when we see that even small changes, such as the Das Capitoline made, generate the same problem …
I hope I have not missed much in my writing in English and you are able to understand what I wrote ….
Adriana Almeida
PS: If someone wants to see, screenshots from the test server (My theme with the new Graphene):
http://www.rederpg.com.br/Testsite-01-top.jpg
http://www.rederpg.com.br/Testsite-02-Middle.jpg
http://www.rederpg.com.br/Testsite-03-botton.jpg
I mark in green all things that I change in my theme and now is somehow wrong. All the choices of graphene is marked to work as I want (2 columns, hide top bar, etc) and all is working well in the old graphene (as you can see in http://www.rederpg.com.br/wp )
I could not resist and installed the new graphene in a test server. And first of all, I apologize for the long post (a lot to say and since my english is not great, I need many words to explain myself… – I think my post is too big… I will try to break then in more than one…)
I’m trying to understand the heart of the matter, but until now, no clue. But I can anticipate: the side menu is not the only problem.
Somehow, the new graphene is not talking to the child theme. I do not know if all the elements have been renamed, or what it is, but beyond the side menu, I found other problems (all using a child theme):
* The option “Hide the top bar†is not respected
* The option “excerpts show in front page†is not respected
* The option “Link header image to front page” is not respected
* The Option “Post date display as an icon (including the year)” is not respected (Or any options on “Post date display”)
* changes in the size of the image of heather (in my css, I determined the height to 115 px) are not respected
And that’s just what I saw in 20 or 30 minutes of testing. Apparently, in graphene without theme child, everything works perfectly, and has some great things as include the new stipulations of the favicon for WP3.1 (I had to put my code in the heather), a widget for banners (solution used on my site, but by inserting code in the heather …), possibility of more columns (I do not care for this right now, but is good have this option) and other cool stuff.
Since most of the solutions I had already implemented, I can live without this update, but I’m thinking of future upgrades, and advantages that I may be losing if I unlink totally my theme of Graphene theme. A lot of options and choices, and the quality of solutions delivered, make Graphene an excellent theme, either to use alone or, even more in my case, to be the foundation for a child theme.
I could not resist and installed the new graphene in a test server. And first of all, I apologize for the long post (a lot to say and since my english is not great, I need many words to explain myself…)
I’m trying to understand the heart of the matter, but until now, no clue. But I can anticipate: the side menu is not the only problem.
Somehow, the new graphene is not talking to the child theme. I do not know if all the elements have been renamed, or what it is, but beyond the side menu, I found other problems (all using a child theme):
* The option “Hide the top bar†is not respected
* The option “excerpts show in front page†is not respected
* The option “Link header image to front page” is not respected
* The Option “Post date display as an icon (including the year)” is not respected (Or any options on “Post date display”)
* changes in the size of the image of heather (in my css, I determined the height to 115 px) are not respected
And that’s just what I saw in 20 or 30 minutes of testing. Apparently, in graphene without theme child, everything works perfectly, and has some great things as include the new stipulations of the favicon for WP3.1 (I had to put my code in the heather), a widget for banners (solution used on my site, but by inserting code in the heather …), possibility of more columns (I do not care for this right now, but is good have this option) and other cool stuff.
Since most of the solutions I had already implemented, I can live without this update, but I’m thinking of future upgrades, and advantages that I may be losing if I unlink totally my theme of Graphene theme. A lot of options and choices, and the quality of solutions delivered, make Graphene an excellent theme, either to use alone or, even more in my case, to be the foundation for a child theme.
I KNOW that the theme author is not responsible for the changes we make on child themes and had other priorities. But one of the great advantages of WP is precisely the possibility to change themes in a sort of large collaborative work. Although I changed a lot the original theme (in some points, major changes, in others, not so much), I wanted to leave the credits for the original theme, just for respect and admiration to those who took the trouble to mount the base from which I created my theme …
so I really would love some support, at least to give us a direction where we can begin work to re-make our themes compatible with the original theme! One hypothesis of what might be causing this incompatibility might already be pointing me in the right direction to solve … Unfortunately, I am not able to imagine what could be.
Moreover, the support that we are asking is not to solve something that went change and them go wrong. But something we changed, worked perfectly and now with the update, stopped working. So we know that works, but something in the new theme is overriding the choices of the child theme. Even more when we see that even small changes, such as the Das Capitoline made, generate the same problem …
I hope I have not missed much in my writing in English and you are able to understand what I wrote ….
Adriana Almeida
PS: If someone wants to see, screenshots from the test server (My theme with the new Graphene):
http://www.rederpg.com.br/Testsite-01-top.jpg
http://www.rederpg.com.br/Testsite-02-Middle.jpg
http://www.rederpg.com.br/Testsite-03-botton.jpg
I mark in green all things that I change in my theme and now is somehow wrong. All the choices of graphene is marked to work as I want (2 columns, hide top bar, etc) and all is working well in the old graphene (as you can see in http://www.rederpg.com.br/wp )
Tks Das Capityolin,
I really want do the upgrade, but right now, I think is better to play safe and do nothing!
I will try to see if anyone of my team wants to reproduce our site elsewhere and made a test and see if is possible to do the upgrade. Until that, I will stay in 1.1.4!
Tks again.
Viewing 10 posts - 1 through 10 (of 11 total)
- 1
- 2
