Possible conflict between CF7 with DIV and WPSSO. plugin

Have you read the sticky post? https://www.ads-software.com/support/topic/must-read-before-posting/

What is the URL to an example post/page on your site?

Please describe the issue on that post/page so we know what to look for. ??

Thanks,

js.

Thank you. I do not understand what you require but bare with me as I detail the problem.
As with all plugin tests I purge all caches [including all page caches ] first before checking the plugin operation.

I discovered this problem by accident within 24 hrs when a Spanish retailer complained the site was not working. He could not place his online order. The obvious move was to deactivate plugin’s to find the problem. We had activated the plugin some 24 hours before and were quite chuffed. I however did not,do a complete test run to point of sale but stopped at Saving to cart. It was only after the telephonic complaint that we looked at all pages.

It is important that it is accepted we have employed various methodologies trying to disprove CSSO plugin fault looking for a possible other plugin conflict sadly time and again when CSSO was deactivated the site rectified. Eventually we had stripped the site to the barest operational components, Sadly when CSSO is activated to removes CF7 fields from the named pages.

If I activate WPSSO then any page using div and contactform7 to construct a page reverts to html. If you visit the site now with the CSSO plugin disabled you will see what is required in Contact us, shopping cart, checkout, retailer application shopping, exotic swimwear header link which open an age restriction. The latter also problematic in as much that the hyperlink disappears.

NOTE: The examples below required me to activate CSSO.

NOTE:The plugin has been deactivated in the meantime while we discuss the problem discovered.

An example, the contact us page which is built using DIV and form7 contains the usual fields, Name, type of enquiry, input/post fields.
You will see the designed state if you visit the https://www.oceanswardrobe.xen.co./za now.
Selecting the relevant links from the footer and header or placing a faux order to see the Cart and check out working format.

When the WPSSO plugin is activated.

THE following is direct copy and paste of what appears on the respective pages ONLY when WPSSO plugin is activated.

Home / Contact us
Contact us

For general inquiries, please use the form below and ensure all form fields marked with “*” are provided before submitting and we will get back to you as soon as possible.
[one_half][contact-form-7 id=”23″ title=”Contact form 1″][/one_half] [one_half_last]

[box]
Contact details

Postal Inquiries: Xen International, counter Montclair Post office, Durban, South Africa, 4061

Telephone: +27 (0) 31 469 1958

Fax: +27 (0) 31 469 1958

Skype: Xenswimwear

Email address: [email protected]

[/box]
[/one_half_last]

For retailer page appears like this.

Home / Retailers application
Retailers application

Please ensure all form fields marked with “*” are provided before submitting.
[contact-form-7 id=”24″ title=”Retailer application”]

checkout appears thus:
Home / Checkout
Checkout
[box] Please complete the form below, making sure all the fields with the “*” are provided.

NOTE: Payment will be processed through the secured SagePay.com gateway. In keeping with our customer first policy for your superior protection our gateway utilises the MasterCard and Visa 3D Security protocol, whereby a code will be sent to your mobile via SMS in order to complete the payment.[/box] [woocommerce_checkout]

The WPsso plug in disables the site inasmuch that if I activate it those pages do not work which means no contact or sales. If you are able and wish to see as live comparision please supply your time zone GMT. So that I can approximate the time of your viewing with CSSO activated limiting the order down time.

Hope the above is detailed enough.

Kind regards Hugh.

It sounds like there’s a bug in those plugins where their shortcodes are only being expanded once – a common issue with authors wanting to improve the speed of their code without knowing that filters can be applied more than once. ?? See here for a recent post about that: https://make.www.ads-software.com/plugins/2017/10/03/is-your-filter-going-to-break-the-layout/

If you hook the ‘wpsso_filter_content’ filter and return false, that should bypass that bug. Example for your functions.php file:

add_filter( 'wpsso_filter_content', '__return_false' );

Let me know if that fixes the issue. If it does, then you should report that problem to the plugin authors so they can fix their code. ??

js.

Thank You I will try that and revert accordingly.
Regards Hugh.

Let me know if that fixes the issue. ??

js.

Good morning J.S. Sorry but I must be blind or really Stupid. I cannot decide where this script should be placed. To start my knowledge of coding is limited. I find the function.php in Lib folder but cannot see where to place.

add_filter( ‘wpsso_filter_content’, ‘__return_false’ );

A little more help please.

kind regards Hugh

Generally, the functions.php file is located in the main theme (or child theme) folder. You would usually place new code at the end, before the ‘?>’ marker (which is optional, so may not be there). It’s a fairly common thing to do, so there’s lots of How-Tos on Google. ??

https://www.google.com/search?q=wordpress+how+to+edit+functions.php

js.