1.2 Child theme bug

  • cb-rcw

    #546

    After a clean install of Graphene 1.2, everything looked normal. Once a child theme was created with an identical style.css file (named graphene-child and references graphene), the RSS button image disappeared and the top menu bar loses its silver tabs and black border and is replaced with a dark gray bar.

    Das Capitolin

    #12877

    Nobody else has this issue with child themes on 1.2?

    Adriana

    #12878

    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

    http://www.rederpg.com.br

    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 )

    Adriana

    #12879

    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.

    Adriana

    #12880

    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

    http://www.rederpg.com.br

    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 )

    Adriana

    #12881

    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

    #12882

    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! 🙂 🙂 🙂 🙂 🙂

    Das Capitolin

    #12883

    I understood your message perfectly, Adriana, and thank you for sharing the details of your findings with us. Syahir Hakim has done a wonderful job with Graphene, but I believe 1.2 should have remained in beta until these obvious issues were corrected. I know that Syahir has other obligations, but it’s better to fix this theme now before too many people update (without a backup) and lose their progress. I suspect we will begin to see many more problems reported here in the next week.

    Admin

    Syahir Hakim

    #12884

    @Das Capitolin, in your first post what do you mean by “an identical style.css file”. Identical to what?

    @adriana: I did a check for these items you mentioned:

    * 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 all of them seems to work just fine. As for the header image size, did you follow the steps outlined here: https://forum.graphene-theme.com/topic/header-image-size-change

    Also, if you could, please post your child theme’s style.css and functions.php file content on pastebin so that I can investigate further.

    Das Capitolin

    #12885

    Syahir:

    What I mean is that I copied the style.css file to the graphene-child directory, and it was identical to the original version 1.2 file except for theme references to graphene. This is how you explain to make a basic child theme, however in doing so the RSS button image disappears.

Viewing 10 posts - 1 through 10 (of 22 total)

You must be logged in to reply to this topic.

Do NOT follow this link or you will be banned from the site!