I’m happy to help you find the issue. I would need the PHP error from the debug.log file. Please enable the WP_DEBUG constant and copy-paste the error from the resulting debug.log file. You can find more info about WP_DEBUG here: https://codex.wordpress.org/WP_DEBUG
Thanks,
js.
Oh, hold on – I thought you were reporting an error. It sounds like WPSSO is applying some WordPress filters that are badly coded (see here for more info: https://make.wordpress.org/plugins/2017/10/03/is-your-filter-going-to-break-the-layout/).
The “Apply WordPress Content Filters” option on the SSO > Advanced settings page should be disabled by default, for this very reason (too many badly coded filters out there). You should double-check to make sure that option is unchecked.
js.
“Apply WordPress Content Filters” is unchecked.
So I have the following set
define(‘WP_DEBUG’, true);
define( ‘WP_DEBUG_LOG’, true );
But there is no error displayed on screen at the offending page, and neither is there a debug.log file created in the wp-content directory. However the apparent clash and the malformed exists as mentionned.
Thanks for coming back to me so quickly, I am afraid it has not been possible for me to echo that however as we are in the process of domestic turmoil post moving home.
So disabling again for now.
When you feel inclined to work on this, I would suggest you disable WPSSO, reload the front-end webpage, save the webpage HTML as a file (File -> Save Page As…), then enable WPSSO, reload the webpage, and save it. Then open a ticket at http://support.surniaulula.com/support/tickets/new and attach both same webpages. I’ll check the differences and see what might be going on. There must be a filter or action being triggered by WordPress which is not coded properly and is messing up the webpage. It’ll probably help to know how the HTML is being affected.
js.
