- This topic has 6 replies, 4 voices, and was last updated 9 years ago by
.
-
Posts
-
PHP 7 Compatibility Checker plugin gives 6 warnings for Genesis. An example: "510 | WARNING | Function name "__genesis_return_content_sidebar" is discouraged; PHP has reserved all method names with a double underscore prefix for future use". Is this going to be fixed sometime soon??? Genesis Layout Extras also has this issue. While these are currently 'warnings' they could be official problems in the future.
You can ignore the warnings. PHP will never use a function starting with __genesis. All of the sites I support are running on PHP 7. There are no issues whatsoever.
Regards,
Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?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!!!
Since this only involves a handfull of lines of code THEY NEED TO BE FIXED!!!
As a IT-professional with 40 years experience under my belt as well, I completely agree with jdenning. Saying that something doesn't need to be fixed since it will never be used is a very poor excuse. This is easy to correct and it just should be done, since leaving messages, even warnings, which can be fixed without much effort is just bad practise.
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>
I've moved this from "forum bugs" to "General Discussion" as this post is not related to a bug with this community forum.
The PHP developers with never create a core function starting with the name __genesis. If you've ever walked through WordPress or WooCommerce code, there are functions everywhere starting with a double underscore. This is really nothing to worry about.
Regards,
Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?
- The forum ‘General Discussion’ is closed to new topics and replies.