Component Corruption After Push To Live

Support
#1

Hi,

I seem to have several problems with components nt behaving once the website has been migrated from development to the live environment. All was working properly on the development host. Migration, as with dozens of other websites was done using All In One WP Migration Unlimited.

The two main issues I have are:

  • Off canvas with a WPForm component will not submit the form and gives an error.
  • List, where the color of the icon does not show.

The list error show as the following in the Console:

Style tracker could not locate existing style tag style[id^=cs-theme-options-generated]
(anonymous) @ app.react18.7.7.11.js?ver=7.7.11:98Understand this warning
7cs-classic.7.7.11.js?ver=7.7.11:1 Unable to locate content template TypeError: Cannot read properties of null (reading 'textContent')
    at cs-classic.7.7.11.js?ver=7.7.11:1:46098
    at cs-classic.7.7.11.js?ver=7.7.11:1:33879
    at cs-classic.7.7.11.js?ver=7.7.11:1:34380
    at cs-classic.7.7.11.js?ver=7.7.11:1:35148
    at Array.map (<anonymous>)
    at An (cs-classic.7.7.11.js?ver=7.7.11:1:35136)
    at cs-classic.7.7.11.js?ver=7.7.11:1:36906
    at Oe (cs-classic.7.7.11.js?ver=7.7.11:1:36116)
    at e (cs-classic.7.7.11.js?ver=7.7.11:1:36898)
    at e (cs-classic.7.7.11.js?ver=7.7.11:1:36874)
(anonymous) @ cs-classic.7.7.11.js?ver=7.7.11:1Understand this warning
7app.react18.7.7.11.js?ver=7.7.11:5 Unable to locate content template TypeError: Cannot read properties of null (reading 'textContent')
    at Gp.defaultOption (app.react18.7.7.11.js?ver=7.7.11:5:218069)
    at app.react18.7.7.11.js?ver=7.7.11:5:205518
    at app.react18.7.7.11.js?ver=7.7.11:5:205238
    at app.react18.7.7.11.js?ver=7.7.11:5:206379
    at Array.map (<anonymous>)
    at eI (app.react18.7.7.11.js?ver=7.7.11:5:206367)
    at app.react18.7.7.11.js?ver=7.7.11:5:208247
    at qC (app.react18.7.7.11.js?ver=7.7.11:5:207339)
    at t (app.react18.7.7.11.js?ver=7.7.11:5:208239)
    at t (app.react18.7.7.11.js?ver=7.7.11:5:208215)
app.react18.7.7.11.js?ver=7.7.11:19 Unable to resolve color: # | Under Dev Toolkit > Tools > Data Store > Colors, it can manually be repaired by inserting a new color item with the id (#)
CAe @ app.react18.7.7.11.js?ver=7.7.11:19Understand this warning
app.react18.7.7.11.js?ver=7.7.11:19 Unable to resolve color: #f | Under Dev Toolkit > Tools > Data Store > Colors, it can manually be repaired by inserting a new color item with the id (#f)
CAe @ app.react18.7.7.11.js?ver=7.7.11:19Understand this warning
app.react18.7.7.11.js?ver=7.7.11:19 Unable to resolve color: #ff | Under Dev Toolkit > Tools > Data Store > Colors, it can manually be repaired by inserting a new color item with the id (#ff)
CAe @ app.react18.7.7.11.js?ver=7.7.11:19Understand this warning
app.react18.7.7.11.js?ver=7.7.11:19 Unable to resolve color: #fffff | Under Dev Toolkit > Tools > Data Store > Colors, it can manually be repaired by inserting a new color item with the id (#fffff)

I have been into Dev Tools > Colors and all colors look fine. I have even clicked “Run” and resaved them, but the error persists.

The off canvas with WPForms throws the following on-screen error and reloads the same page, rather than redirecting to the thank you page, as it should: Attempt to submit corrupted post data

Any ideas what could be going on?

Thanks,
Christopher

#2

Hey Christopher,

Please test your WP Forms if it’s Cornerstone causing the issue or not by adding the form in a normal page not built with Cornerstone.

If it’s Cornerstone causing the issue, try rebuilding the Component in your live site.

Also, please try clearing the Style Cache.

#3

Hi Christian,

If I add a WPForm to the same page using the form integration element, the form works normally.

In this instance, it is the components which are not functioning as expected, as described above. They were all working perfectly before migration and this is the first migration where I have ever had mis-performing components.

Thanks,
Christopher

#4

Hey Christopher,

Have you tried rebuilding the Components and clearing the Style Cache as mentioned previously?

#5

Hi,

Yes, I have cleared the style cache and it makes no difference. I have not yet rebuilt any of the components - a good many components have been used across the website. I have just discovered several more, which have been badly affected (Service pages, for example).
It seems that all components are broken on the new site and their settings are not being respected. @charlie, any ideas what might be happening?

Thanks,
Christopher

#6

Hey @whitemedia,

Charlie is not around at the moment but I’ll forward this case to him when he gets back. Please stay tuned.

Thanks.

#7

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.