Visual Editor Conflict

Just sent Contact Form with FTP Credentials!

Sent you FTP Credentials via Contact Form:

See Correction here from Roger:

Oops… Sorry port 21 should be entered, my bad ( I was changing FTP config on another server).

I tested Jeremy’s login credentials as working: https://ftptest.net/

Hi Jeremy – let me know if you need anything else to proceed with FTP Access.

I just replied to your email. Check your inbox, you got mail! ?? ??

Thank you Jeremy. I’ve responded to your email regarding our Server Admin/Hosting Provider (Roger Wheatley).

Hi Jeremy:

Roger reached out to you directly via eMail on 20 May as follows:

Hi Jeremy,

When we add the following to wp-config.php:

define( 'WP_DEBUG', true );

if ( WP_DEBUG ) {

@error_reporting( E_ALL );
@ini_set( 'log_errors', true );
@ini_set( 'log_errors_max_len', '0' );

define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'CONCATENATE_SCRIPTS', false );
define( 'SAVEQUERIES', true );}

We get this error message displayed to website visitors:

Parse error: syntax error, unexpected ‘if’ (T_IF) in /home/bizcatal/public_html/wp-config.php on line 28

Attached is the complete wp-config.php file that contains your additions as above.

Roger Wheatley…

Hi Jeremy:

Roger has responded to you directly by eMail:

Hi Jeremy,

I uploaded your version. Please go ahead with what you need to do.
Where is the error log now going to be stored?

Appreciated! ??

Thank you,
Roger

Roger has now responded by eMail to you with the information you requested:

From: Roger Wheatley <[email protected]>
Subject: Re: [#3219802]: [Jetpack] Post-9146 VISUAL EDITOR CONFLICT | ATTN: JEREMY
Date: May 24, 2017 at 12:37:38 PM EDT
To: [email protected]
Cc: [email protected]

Hi Jeremy,

Please find the link for the bizcatalyst360.com debug.log below. It is a large file so can avoid clogging up email by using the below access…

I’ve linked 1 file to this email:
debug.log(17.1 MB)Dropbox
https://db.tt/a7MoqdJgRf

Appreciate your remarkable diligence here (and that of Roger) in trying to resolve this issue, Jeremy. We’ve decided to retreat at this stage, as the time invested in seeking a solution can be best spent elsewhere. We’re going to deactivate JetPack for now in hopes that the next Update will bring with it a resolution. Meanwhile, we’ll simply seek some of the key functionality (e.g. Publicize, etc.) via an alternative plugin.

Thanks again for your great support!

OK TO CLOSE THIS TICKET

Happy to help! Deactivating Jetpack may not solve all your problems though, as we’ve seen together in our last email exchange. On the long run, it may be worth reviewing the different plugins currently in use in your post editor, and removing those you can live without to avoid the database issues you’ve been having.

Hopefully you can find a solution!