Hi, my host asked me if I want to upgrade from php 5.6 to php 7.
Will this work or cause problems?
I read PHP 7 will make the site more secure and faster. So I want to do it.
I am running the latest version of WP 4.6.1 and Newspaper 7.4. I did a compability test with all plugins and it passed all green and good.
Does Newspaper support this?
Thanks!
-
This topic was modified 9 years by
libtetto.
The theme is not 100% compatible with php7. However I have site running Newspaper with php7 and seems ok. I did check the code and ideally Tagdiv need to re-write 5 items which fail php7 compatibility.
They seem strangely reluctant. Even they they where among the first pushing how good their code was such it would run a faster site! Also it is only 5 items!!
Maybe more of us need to encourage them!
@ShowbizCool
you should consider making a post:
[TUTORIAL] Early Adopters for PHP 7x
and detail the items which need changing for those running PHP7.
Funnily enough a *lot* of folks only recently finally got off php 5.4 to 5.6, and “not quite” ready for 7.
Luckily in our case we can switch back and forth between the two. We’re still on 5.6x here, but getting ready to move to PHP7 for January 2017, so pointers would be good (we’re using Newsmag, but some similar stuff there methinks).
Anyway — if you make that a [TUTORIAL] they can add it to the ‘best of user forums’ section.
Hi Chris
I give the [TUTORIAL] some thought.
Actually I think you might know about the Speed Boaster plugin. Am I right is thinking with some of the modern browsers it is redundant? I seem to remember it’s when the site is running SSL. I think I saw you said you did not use it anymore?
The reason for mentioning it is that 3 of the compatibility errors where in that plugin!
Like you we can just switch php version on will. It may be on my test of Newsmag theme (can’t remember for sure) I found it was only really fully compatible up to 5.4 (caused by one error).
It is possible to write php so it will work with versions of php 5 AND php 7! They are not mutually exclusive.
Yeah … I’ve been moving all our news network sites to https with “Let’s Encrypt” and we’re going to be beta testing http/2 on our server for the speed-demon-who-needs-CDN-not-me-buddy effect :-).
I don’t use the speedbooster anymore since I tend to manually hack stuff to move to footer anyway, merge files, and then put critical css in header. SO, I’m more into doing that vs the plugin. Also been cheating a bit with the simple “scripts to footer” plugin which plays nice with our sites at the moment.
Also it turned out finally going from Newsmag 1.7 (ahem!) to 3.1 made huge difference in being able to use the tagdiv beta composer. So, with the 3x, scripts to footer, basic house cleaning, and the tagdiv composer, that is one huge giant jumpstart right there … newspaper a bit more clunky but serves more masters!
Right now I’m still embroiled in the nightmare that is working with google for http > https, notifying Google News, mysql search/replace crap, etc. — WAAAH!
Anyway — have not myself yet gotten to playing with php 7. Just switched on new server Aug 5, so still doing house cleaning on stuff in prep for new version of mod_pagespeed (we crashed last version due to some issue where it didn’t like missing images, and with server crash we borked some stuff, so now need to add stupid htacess rule to redirect missing jpeg to default jpeg just to get mod_pagespeed to work …)
but I digress … as per usual :-0
tagDiv, what’s your position on this?
We get these errors/warnings:
FILE: wp-content/themes/Newspaper/includes/wp_booster/td_translate.php
---------------------------------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
---------------------------------------------------------------------------------------------------------------------------------------
258 | WARNING | Function name "__td" is discouraged; PHP has reserved all method names with a double underscore prefix for future use
---------------------------------------------------------------------------------------------------------------------------------------
FILE: wp-content/themes/Newspaper/includes/wp_booster/external/less.php-master/lib/Less/SourceMap/Base64VLQ.php
-----------------------------------------------------------------------------------------------------------------------------------------------------------
FOUND 3 ERRORS AFFECTING 1 LINE
-----------------------------------------------------------------------------------------------------------------------------------------------------------
156 | ERROR | Bitwise shifts by negative number will throw an ArithmeticError in PHP 7.0
156 | ERROR | Bitwise shifts by negative number will throw an ArithmeticError in PHP 7.0
156 | ERROR | Bitwise shifts by negative number will throw an ArithmeticError in PHP 7.0
-----------------------------------------------------------------------------------------------------------------------------------------------------------
FILE: wp-content/themes/Newspaper/includes/wp_booster/external/less.php-master/lib/Less/Parser.php
----------------------------------------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
----------------------------------------------------------------------------------------------------------------------------------------------
470 | WARNING | INI directive 'mbstring.internal_encoding' is deprecated from PHP 5.6.
471 | WARNING | INI directive 'mbstring.internal_encoding' is deprecated from PHP 5.6.
478 | WARNING | INI directive 'mbstring.internal_encoding' is deprecated from PHP 5.6.
----------------------------------------------------------------------------------------------------------------------------------------------
FILE: wp-content/themes/Newspaper/includes/wp_booster/wp-admin/external/wpalchemy/MetaBox.php
-----------------------------------------------------------------------------------------------------------------------------------------
FOUND 2 ERRORS AFFECTING 2 LINES
-----------------------------------------------------------------------------------------------------------------------------------------
451 | ERROR | Use of deprecated PHP4 style class constructor is not supported since PHP 7
532 | ERROR | preg_replace() - /e modifier is forbidden since PHP 7.0
-----------------------------------------------------------------------------------------------------------------------------------------
It’s really not a lot of changes, wonder why you’re reluctant to implement them.
Cheers
Hello,
We are not reluctant to implement these fixes. I already stated in multiple threads that we are working on this as we speak. I’m not sure where people are getting this idea. We are working on a fix and we will add PHP 7 support. It just needs to be tested thoroughly though and this take time. Please be patient and wait for future updates where we will announce the compatibility for PHP 7. I would like to say it will be out in the next update but unfortunately if something happens and we will not be able to release it by then, it will not be ok so I cannot say for certain it will be in the next update or not but we will do our best to implement it as soon as we can.
Thank you!
Any chance, from those at TagDiv, of an update on how PHP 7 support is going?
I guessing you may not had chance to check yet?
-
This reply was modified 9 years by
ShowbizCool.