Skip Navigation

[Resolved] Since Toolset Update not possible to show anymore RFG in View Block

This support ticket is created 4 years, 1 month ago. 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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 3 replies, has 2 voices.

Last updated by Waqar 4 years, 1 month ago.

Assisted by: Waqar.

Author
Posts
#1790313
Screenshot 2020-09-25 at 17.52.34.png

I am trying to:
Continue Use Views to show RFG - worked just fine until today when updated

Link to a page where the issue can be seen:
Anywhere a view lists RFG

I expected to see:
Working View

Instead, I got:
Broken View (if already existing), not able to create new view (no results, cannot set RFG filters, freezes page, JS errors)

1. Try to add a View in this CT here hidden link on the package (fresh) here:
hidden link

Keep the console open.

- Warning: React does not recognize the `isLarge` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `islarge` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
- Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See hidden link for details.

2. Then try to add a view for the RFG, and see the third error appear:
- Warning: React does not recognize the `popoverProps` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `popoverprops` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

3. Now try to add a Custom Field in the view for the RFG (DATE), I already provided it, it will pile up to 5 errors:
- Uncaught (in promise) TypeError: Cannot read property 'categories' of null
- Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of t which is inside StrictMode. Instead, add a ref directly to the element you want to reference.
- Warning: Legacy context API has been detected within a strict-mode tree:

And so on.

Now, on existing sites this makes the views not render their preview, and it shows "this view returns no results", even before it did, and you can't successfully edit them anymore.
On fresh sites, you can edit, but the errors are still piling and sooner or later, things freeze.

Please use the duplicate of fresh site to see.
All plugins of toolset are fresh downloads from the toolset download area.

This is closely connected to other update issues reported to luo, but additional to those.

Additional these PHP errors happen:
( ! ) Notice: Undefined index: #options in /Applications/MAMP/htdocs/cleanup/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/lib/enlimbo.forms.class.php on line 708
( ! ) Warning: Invalid argument supplied for foreach() in /Applications/MAMP/htdocs/cleanup/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/lib/enlimbo.forms.class.php on line 708

#1792737

Hi Beda,

Thank you for contacting us and I'd be happy to assist.

During testing on my test website as well as on your website's duplicator package, I was able to see these warnings, only with "SCRIPT_DEBUG" set to "true", in "wp-config.php" file:


define( 'SCRIPT_DEBUG', true );

Can you please confirm if removing this line fixes the warnings and the page freeze issues on your server too.

I'll be able to report this to the concerned team accordingly.

regards,
Waqar

#1794097

Hi Waqar

I had that debug on because of the issues like update not working and later CRED error

And hence I probably fooled myself later trying views which failed but as you correctly say it seems solved when we disable script error logging.

Strange. I had that debug on at times before and it didn’t really break any views. Did it freeze on your end too? Or did you only get the warnings?
(Ps this is again also a safari issue probably, I didn’t yet even test in chrome)

#1795485

Hi Beda,

Thanks for confirming that.

For me, the edit screen doesn't freeze, even though, these warnings are logged in the console.
( that is true for a new test install as well as your website's clone, using Google Chrome )

I'm going to share information about these warnings to the concerned team and as always, you're welcome to share any further observations or notes.

regards,
Waqar