• Skip to main content
  • Skip to forum navigation

StudioPress

  • Shop for Themes
  • My StudioPress

Forum navigation

  • Home
  • General Genesis Discussions
  • StudioPress Themes
  • Genesis Blocks
    • Genesis Blocks
    • Genesis Custom Blocks
  • Retired Themes
  • FAQs
  • Forum Rules
  • Internationalization and Translations
  • Forum Bugs and Suggestions
  • Forum Log In

Are You Using The WordPress Block Editor?

Genesis now offers plugins that help you build better sites faster with the WordPress block editor (Gutenberg). Try the feature-rich free versions of each plugin for yourself!

Genesis Blocks Genesis Custom Blocks

jdenning

Welcome!

These forums are for general discussion on WordPress and Genesis. Official support for StudioPress themes is offered exclusively at My StudioPress. Responses in this forum are not guaranteed. Please note that this forum will require a new username, separate from the one used for My.StudioPress.

Log In
Register Lost Password
  • Profile
  • Topics Started
  • Replies Created
  • Engagements
  • Favorites

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • March 2, 2017 at 2:00 pm in reply to: Genesis not currently fully compatible with PHP 7 (repost) #202366
    jdenning
    Participant

    ericzaat - This is a "software cultural" problem. Since browser technology often covers for poor coding practices and errors even, programmers today have become lazy. Well over a year ago I flagged a minor css error in Executive Pro (the width: 100 for the CTA was missing a semicolon which is why the CTA does not default to full width). I did this here and filed a bug report. I blew this off as I expected nothing would be changed as the stated policy is to never update a child theme. Well, guess what, this child theme was updated but the semicolon was NOT included in the repair. </vent>

    March 1, 2017 at 4:32 pm in reply to: Genesis not currently fully compatible with PHP 7 #202280
    jdenning
    Participant

    Sorry to post twice. I am a degreed BSEE engineer out of U.C. Berkeley '76. Once upon a time I was doing some consulting for National Cash Register (1989-1991) for a project that had in affiliation with Microsoft. I participated in the development of a LAN and WAN Automated Software Distribution System for OS/2 including SNA gateway communications software between LAN and Host. I was tasked with updating the comm stack to OS/2 from Unix and was told it was all there and that I just needed to do a sanity check. Guess what there was no LU0 which was a necessary portion. There was a Unix version though. I then began to port the Unix version to OS/2. There were a BOAT LOAD of warnings during the compile. I quickly scanned the output and determined that since these were warnings I could safely ignore them. Well in Unix one of the function prototypes required an 8 bit return but the OS/2 version required 16 bits. It was flagged only as a warning and was lost among the 100-200 other warnings. It crashed the program and it was like finding a needle in a haystack to sort out. FAST FORWARD Since then I will NEVER release any code that contains warnings. The problem is that at some point in the future this could get overlooked and give everyone a surprise. Since this only involves a handfull of lines of code THEY NEED TO BE FIXED!!!

    March 1, 2017 at 4:31 pm in reply to: Genesis not currently fully compatible with PHP 7 (repost) #202279
    jdenning
    Participant

    Victor, you actually look younger than I (I turn 70 shortly). I am a degreed BSEE engineer out of U.C. Berkeley '76. Once upon a time I was doing some consulting for National Cash Register (1989-1991) for a project that had in affiliation with Microsoft. I participated in the development of a LAN and WAN Automated Software Distribution System for OS/2 including SNA gateway communications software between LAN and Host. I was tasked with updating the comm stack to OS/2 from Unix and was told it was all there and that I just needed to do a sanity check. Guess what there was no LU0 which was a necessary portion. There was a Unix version though. I then began to port the Unix version to OS/2. There were a BOAT LOAD of warnings during the compile. I quickly scanned the output and determined that since these were warnings I could safely ignore them. Well in Unix one of the function prototypes required an 8 bit return but the OS/2 version required 16 bits. It was flagged only as a warning and was lost among the 100-200 other warnings. It crashed the program and it was like finding a needle in a haystack to sort out. FAST FORWARD Since then I will NEVER release any code that contains warnings. The problem is that at some point in the future this could get overlooked and give everyone a surprise. Since this only involves a handfull of lines of code THEY NEED TO BE FIXED!!!

    February 16, 2017 at 12:19 pm in reply to: Executive Pro BUG first reported version 3.1.2 NOT FIXED #201329
    jdenning
    Participant

    Yep. So I thought I would try something different... It's not a big deal if you were to be using and restyling the CTA anyway.

    February 9, 2017 at 4:55 pm in reply to: Executive Pro BUG first reported version 3.1.2 NOT FIXED #200874
    jdenning
    Participant

    It effects the 'width' style. It does matter if you leave out the last semicolon. It doesn't break the entire block, just the last entry. You get a default of whatever is declared elsewhere. It it were working the CTA width would be the entire window width. Try for yourself with and without the semicolon. Also as a graduate software engineer UC Berkeley '76 and someone who wrote C/C++/assembly code and drivers (including Windows mobile drivers for FDA approved medical equipment) I can tell you this. Coding errors happen but when not dealt with after reported for multiple code iterations it begs the question "Am I a beta site for this code??"

    December 4, 2016 at 6:55 pm in reply to: Best approach to implement Schema.org markup! #197024
    jdenning
    Participant

    I have added address schema by hand only to have them removed by the text editor when I switch between the visual and text tabs. If I reload after each tab switch I am OK but if I forget, the address schema is gone for good. My work around is to keep a copy in a local text editor just in case.

    November 23, 2016 at 8:23 pm in reply to: Executive Pro CTA Color Change #196538
    jdenning
    Participant

    I found an issue in ExecPro with a missing semicolon and it is right here on this page even... width: 100% missing semi...... I discovered this a while ago and reported it but there has been no update or follow up from Studio Press...

    November 23, 2015 at 6:54 pm in reply to: Executive Pro vs W3 Total Cache #171879
    jdenning
    Participant

    Yes and that makes some sense as what seems to be getting trashed is CSS stuff. I will turn it off and see what happens. Thanks...

    November 23, 2015 at 1:31 pm in reply to: Executive Pro vs W3 Total Cache #171852
    jdenning
    Participant

    <p>small-bad-cache-picture</p>

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)

CTA

Ready to get started? Create a site or shop for themes.

Create a site with WP EngineShop for Themes

Footer

StudioPress

© 2026 WPEngine, Inc.

Products
  • Create a Site with WP Engine
  • Shop for Themes
  • Theme Features
  • Get Started
  • Showcase
Company
  • Brand Assets
  • Terms of Service
  • Accptable Usse Policy
  • Privacy Policy
  • Refund Policy
  • Contact Us
Community
  • Find Developers
  • Forums
  • Facebook Group
  • #GenesisWP
  • Showcase
Resources
  • StudioPress Blog
  • Help & Documentation
  • FAQs
  • Code Snippets
  • Affiliates
Connect
  • StudioPress Live
  • StudioPress FM
  • Facebook
  • Twitter
  • Dribbble