[Resuelto] Some pages went blank after updating Toolset Views
This support ticket is created hace 1 año, 6 meses. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
After updating Toolset Views from version 3.4.0 to version 3.6.3 the content of some pages in the frontend went blank (only the content part; site header, site footer and page title still appeared).
We did some debugging and we found that the error starts occurring on version 3.5
Please note that the pages are using WPBakery (Modified Version, it's the version that comes with Jupiter theme).
The pages start working again if we rollback to version 3.4.2 and start failing again if we update to 3.5 or later.
This is one of the pages that are blank: hidden link If you go to Edit Page you will see that there's a lot of content that should be displaying. You can downgrade to 3.4.2 and will see that the content is back in the front-end.
I can get you the PHP debug logs... but let me know from what date, or after what action:
- For when I load that page in the front-end?
- For when I load the edit page?
- For when I update / downgrade the plugin?
Thank you for sharing the link to the affected page.
Luo is on vacation, so I'll be following up on this ticket.
To troubleshoot this further, I'll need your permission to download a clone/snapshot of this staging website. This will help in investigating this on a different server, without affecting the actual website.
( I'll not need the debug logs unless the issue turns out to be specific to your website's server environment )
Thank you for waiting, as this investigation turned out to be more complicated than I initially expected.
During troubleshooting, I was able to narrow down the issue with the content of the page disappearing, to the following part of the HTML in the text block of the second row:
( screenshot: hidden link )
<li><span data-ccp-props="{"134233279":true,"201341983":0,"335551550":1,"335551620":1,"335559737":0,"335559739":160,"335559740":240}"><strong><span class="TextRun MacChromeBold SCXW42899244 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW42899244 BCX0">Michigan</span><span class="NormalTextRun SCXW42899244 BCX0">'s</span></span></strong><span class="TextRun SCXW42899244 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW42899244 BCX0"> PFAS Action Response Team (</span></span><a class="Hyperlink SCXW42899244 BCX0" href="<em><u>hidden link</u></em>" target="_blank" rel="noreferrer noopener"><span class="TextRun Underlined SCXW42899244 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="none"><span class="NormalTextRun SCXW42899244 BCX0" data-ccp-charstyle="Hyperlink">MPART</span></span></a><span class="TextRun SCXW42899244 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW42899244 BCX0">) </span><span class="NormalTextRun ContextualSpellingAndGrammarErrorV2 SCXW42899244 BCX0">consists</span><span class="NormalTextRun SCXW42899244 BCX0"> of officials from 10 different state departments. MPART research</span><span class="NormalTextRun SCXW42899244 BCX0">es sources and locations of PFAS contamination to protect drinking water and alert the public of high levels of PFAS.</span><span class="NormalTextRun SCXW42899244 BCX0"> MPART was </span><span class="NormalTextRun SCXW42899244 BCX0">permanently </span><span class="NormalTextRun SCXW42899244 BCX0">established through </span></span><a class="Hyperlink SCXW42899244 BCX0" href="<em><u>hidden link</u></em>" target="_blank" rel="noreferrer noopener"><span class="TextRun Underlined SCXW42899244 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="none"><span class="NormalTextRun SCXW42899244 BCX0" data-ccp-charstyle="Hyperlink">Executive Order 2019-3</span></span></a><span class="TextRun SCXW42899244 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW42899244 BCX0"> by Governor Whitmer </span><span class="NormalTextRun SCXW42899244 BCX0">in 2019. </span><span class="NormalTextRun SCXW42899244 BCX0">In 2020, Michigan Department of Environment, Great Lakes, and Energy (EGLE) adopted a </span></span><a class="Hyperlink SCXW42899244 BCX0" href="<em><u>hidden link</u></em>" target="_blank" rel="noreferrer noopener"><span class="TextRun Underlined SCXW42899244 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="none"><span class="NormalTextRun SCXW42899244 BCX0" data-ccp-charstyle="Hyperlink">ruleset</span></span></a><span class="TextRun SCXW42899244 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW42899244 BCX0"> limiting seven PFAS chemicals in drinking water. </span><span class="NormalTextRun SCXW42899244 BCX0">The levels are set at 6 ppt for PFNA, 8 ppt for PFOA, and 16 ppt for PFOS.</span></span><span class="EOP SCXW42899244 BCX0" data-ccp-props="{"134233279":true,"201341983":0,"335551550":1,"335551620":1,"335559737":0,"335559739":160,"335559740":240}"> </span> The <a href="<em><u>hidden link</u></em>">Great Lakes PFAS Action Network</a> (GLPAN), a coalition of impacted communities and environmental and conservation organizations developed a <a href="<em><u>hidden link</u></em>">policy agenda</a> of administrative and legislative actions to take. </span></li>
If this specific part of the HTML lines is removed from the page's content, it starts showing correctly on the front end, even with the latest Toolset Blocks/Views plugin activated.
This content/text seems to have been copied from some third-party page builder or tool, as it contains many extra tags and inline attributes. You can clean and narrow it down only to the text, to avoid this issue.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
