Community Forums › Forums › Archived Forums › General Discussion › Genesis not currently fully compatible with PHP 7
Tagged: compatible with php 7, php 7, php7
- This topic has 3 replies, 2 voices, and was last updated 9 years ago by
Victor Font.
-
AuthorPosts
-
March 1, 2017 at 12:20 pm #202258
jdenning
ParticipantPHP 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.
March 1, 2017 at 2:09 pm #202266Victor Font
ModeratorI answered your question here: https://www.studiopress.community/topic/genesis-not-currently-fully-compatible-with-php-7-repost/#post-202265
Regards,
Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?March 1, 2017 at 4:32 pm #202280jdenning
ParticipantSorry 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 6:02 pm #202289Victor Font
ModeratorThis forum can't help you with that. We are all community volunteers and have no affiliation with Studio Press. You need to raise your concerns directly with Studio Press by opening a ticket at https://my.studiopress.com/help
Regards,
Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet? -
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.