Sorry, I thought this question would be helpful for others as I thought I had seen this question go unanswered in another question.

I appreciate the example of the code that might be needed.

I had not realized the situation regarding using this forum.

Thanks again for your help.

Thanks for the reply… Umm, so seems having made some adjustments to the standard theme thought the settings it might be difficult to match the main website to the mobile version with your theme.

Not sure I know how or even if it is possible to use inspector browser functionality with a mobile. Shame you could not give an example of the coding that might be required.

I give the problem some thought to see if there is another way to get around this problem.

replied via email…

Two emails sent…

Yes using plugin version. Turned caching off. Still same problem…

In UK English this sounds just a little bit strange (suggestive?)… “so I can take a closer look at your backend”!

Thanks for clearing that up. 🙂

Thanks

Thanks – any reason why it was not in the change log?

Hi Chris

Don’t see “updated for PHP7 compatiblity…” in the change log. That is for this theme and Newspaper. Yet TagDiv say yes tested their Newspaper theme and all ok.

Running a code checker relating to PHP 7 both produce three errors (all three the same, down from four). Visual Composer has one error reported (as above). That said, we have been running both themes with PHP 7 for months now with no obvious problems.

Be good if TagDiv could confirm they have also tested Newsmag for running under PHP 7 to remove any running doubt.

Thanks

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.

Any update on how PHP 7 compatibility is going?

Thanks

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.

I have checked over that latest version found only 5 instances which could be classified as errors for php 7.

Surely this would be worth looking at to be able to claim php7 ready!

Many other themes seem to now have managed this…

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!

The tagdiv team obviously have been adjusting the code over time and that is much appreciated.

If I understand correctly there are a core of php 7 / php 5.6 / php 5.5 / php 5.4 commands that work with all versions. I guess the tagdiv are avoiding using new commands added in php 7 and replacing commands that had been deleted (i.e. not supported). Ideally this would also includes commands that are deprecated but still present.

I did a quick check and found only 5 instances which could be classified as errors for php 7 (this nicely less than a 2015 version of the theme I looked at).

The speed improvements (double) and less resource requirements of php 7 are significant improvements. Any chance I could encourage a further review of the code?

Thanks.

We are currently using php7 with this theme, seems to work. However php7 compatability checker finds a few errors.

What plans are the to make the theme fully comparable?

I realize you have to do the checks but if it is just changing two bits of code in a minor part of separate plugin that may or may not be used… for which the advantages or using may no longer be valid (especially with http/2)?

Just a thought.

Thanks

FYI

FILE: /wp-content/themes/Newsmag/includes/wp_booster/wp-admin/external/wpalchemy/MetaBox.php

FOUND 2 ERRORS AFFECTING 2 LINES
532 | ERROR | preg_replace() – /e modifier is forbidden in PHP 7.0
2147 | ERROR | Deprecated PHP4 style constructor are not supported since PHP7

Hi All

Given the significant benefits of PHP 7 (over double in speed and less demand on server) I would agree with Orlando and urge TAGDIV to relook at this.

I have run a PHP Compatibility Checker on my php 7 setup and it only reports 2 errors in the NewsMag theme!

The only plugin I am using with errors was WP Super Cache which had 3 errors.

Yes that worked.

Thanks 🙂

PS With out adjusting the Speed Booster php file I am getting:-

v4.2 – Disabled – incompatible plugin detected: disqus-conditional-load/disqus-conditional-load.php

Hi Lucian

After the latest update 2.3.1 this solution to allowing Disqus seems not to be working.

I have several attempts and I keep crashing the site. Can you re-check this?

Thanks

Understand your discouraging too many plugins. I am myself in the process of removing some system demanding ones such as NextGen Gallery. However I have 10 your system objects to that my site currently depends on until I can adjust the various many posts.

I can’t see me removing Disqus… It also objects to your “tagDiv Visual Composer Shim”…

Can you explain more what your hoping to do?

Thanks – I take that it is unlikely.

We add videos anyway but can’t take advantage of the Post template style setting when clicking ‘video’ format (to get the display on there home page). Feels somewhat untidy.

Can you suggest how I might modify the themes code?