[trackslayer]

This reply has been marked as private.

[trackslayer]

Hi Ed –

Thanks for your reply.

What is the ETA for the next update please?

The reason I ask is that this impacts when we are able to move our site to a PHP 7.0 server – which is on deck within teh week at WP Engine.

Thanks again for your help!

Barbara

[trackslayer]

Hi David –

We are running the latest version of Neighborhood Theme on our site.

Below is the output of the WP Engine PHP Compatibility Plugin – running a scan of the Neighborhood Theme with PHP 7.0.

Here are the errors & warnings below – please advise:

FILE: /nas/content/live/trackslayer/wp-content/themes/neighborhood/includes/swift-framework/page-builder/sf-page-builder.php
—————————————————————————————————————————-
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
—————————————————————————————————————————-
1 | WARNING | File has mixed line endings; this may cause incorrect results
—————————————————————————————————————————-

FILE: /nas/content/live/trackslayer/wp-content/themes/neighborhood/includes/swift-framework/options/validation/preg_replace/validation_preg_replace.php
——————————————————————————————————————————————————-
FOUND 1 ERROR AFFECTING 1 LINE
——————————————————————————————————————————————————-
27 | ERROR | preg_replace() – /e modifier is deprecated since PHP 5.5 and removed since PHP 7.0
——————————————————————————————————————————————————-

FILE: /nas/content/live/trackslayer/wp-content/themes/neighborhood/includes/widgets/phpFlickr/phpFlickr.php
—————————————————————————————————————–
FOUND 18 ERRORS AND 2 WARNINGS AFFECTING 18 LINES
—————————————————————————————————————–
58 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
82 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
83 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
89 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
98 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
99 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
101 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
102 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
141 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
142 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
143 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
174 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
175 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
178 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
181 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0 – use mysqli instead.
492 | ERROR | Function ereg() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_match instead
492 | ERROR | Extension ‘ereg’ is deprecated since PHP 5.3 and removed since PHP 7.0 – use pcre instead.
501 | ERROR | Function ereg() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_match instead
501 | ERROR | Extension ‘ereg’ is deprecated since PHP 5.3 and removed since PHP 7.0 – use pcre instead.
1689 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
—————————————————————————————————————–

[trackslayer]

Thanks, David –

So be be clear – the Neighborhood theme is fully compliant with PHP 7.0? I will run the scan again & provide your with the details of the warnings.

[trackslayer]

Hi David –

Thanks for your reply.

1) The errors were in the error logs of our install – please advise.

2) The 2nd child theme is not active, btw – spoke with WP Engine tech support to clarify this – so it seems a non issue – they think it was somehow duplicated when they migrated our site.

[trackslayer]

Again – we are having similar issues – this time the outdated WooCommerce file is: neighborhood-child/woocommerce/loop/orderby.php version 2.0.0 is out of date. The core version is 2.2.0,

We have just applied the most recent theme update – and we have no WooCommerce files in the Child theme – all is inherited from the parent theme.

Thanks in advance for your swift response 🙂

[trackslayer]

This reply has been marked as private.

[trackslayer]

This reply has been marked as private.

[trackslayer]

This reply has been marked as private.

[trackslayer]

Hi Ed –

I’ve installed the solid code plugin & edited the code as per above – however the fields are still not updating.

There seems to be two problems:

a) custom fields lose data AND/OR
b) custom fields do not retain formatting

Example (formatting):

Under “Products” – A Hard Day’s Night
http://trackslayer.staging.wpengine.com/wp-admin/post.php?post=198&action=edit

Formatting for this product in the admin panel in the CUSTOM FIELD shows a line of capital “L’s (LLLLLLLLLLLL) in a separate paragraph as a test.

However – in the “View Product” view (also accessible from the “Song Catalog” link in the top nav this listing for “A Hard Day’s Night” shows the line of “LLLLLLLLLLLL”s all in one paragraph.

http://trackslayer.staging.wpengine.com/product/a-hard-days-night/

Pleaze let me know your thoughts.

Best,

Barbara

[trackslayer]

This reply has been marked as private.

[trackslayer]

This reply has been marked as private.

[trackslayer]

Hi –

I cannot upload the .php files for you review as the file types are disallowed.

I would put them in a dropbox but need a private reply to do so – do not wish our dropbox folder to be public.

Please reply privately with an email addy for the DB.

Thanks.

[trackslayer]

Hi –

Our developer from WPML/Custom Types Views looked at Fatal Error code string.

She says it relates directly to the functions.php file of the Neighborhood theme and NOT the plugin updates.
——————————————-
Here’s what she said:

Apparently on lines 767, 777, 787 of this file there is an issue with a function is_array.

She corrected this in our staging site however I think you should talk to the theme developer.

See attached the original file from the theme and the one I’ve edited (my_version).

——————–
I’ve uploaded the corrected code for you to look at.

Please advise.

Thanks.

[trackslayer]

Hi Ed –

Having a similar issue – please see my post here:

http://support.swiftideas.net/forums/topic/default-sidebar-config-and-page-options/#post-31711

Thank you,

Barbara