[Resolved] View block UI not loading

[Author]

Posts

[logicelf]

I am trying to: Edit a View block I have just created. The UI will not load. This occurs in multiple browsers.

Link to a page where the issue can be seen: (screenshot) hidden link

The first block is a related posts block - a View with a query filter for a relationship. The UI refuses to load. The second block is another View block, just created and editable.

There is no caching active, and no configuration has changed (to my knowledge). I am just trying to edit a single CPT template and add two lists of related CPTs.

I can't see anything in the forums about common causes for this type of thing. Is it a resource issue? A Views beta issue?

In addition - when trying to edit the query filter for the second View block - I do not see the Topic-Specialties relationship (which definitely exists): hidden link

I need to do a fair bit of work on this site in the next few days - am I better off abandoning the Views beta altogether?

Thanks in advance,

James

[Beda]

I am not sure what you mean, because I can see the settings of the View in the Blocks settings to the right of the editor, in your screenshot.
What UI do you not see but expect?

Related to the missing relationship, if it exists and has posts it generally appears in the Views Query Settings.

Now - the current Beta as you can download it from your account on Toolset, is stable enough to be used without risking breaks in future, but if you started this with the original "Blocks" plugin then things will break, this means, what you created in the (old) Blocks Plugin will not entirely work in the current Beta Views or any future Views.
That was however communicated when it was published (to not use it on production sites) and I hence assume, this is not the case on your site.

I would need to take a closer look at this, I think - if you can confirm that even without other Plugins and another theme, this still happens.

Locally, I can setup views and relationship filters correctly, using the Blocks Builder, however there are so many factors at play here that I impossibly can consider them all in a test.
Having insight to the page/website, or a staging site, or a duplicate, can help me to rebuild exactly what you have and see the issue, or update you with a solution.

I enable private replies so you can provide me with such data.

Thank you

[Beda]

I see what you mean now, yes.

The first View is not loading its content (preview) or any UI at all, this should be due to repeating JS errors in the console.

Failed to load resource: the server responded with a status of 500 ()

and

Uncaught (in promise)

The errors occur on hidden link
==> Are you using the REST API of Toolset?

To see if I could somehow replicate this I've duplicated that Content Template and removed the broken View, which solved the issue (errors) but threw others:

Block validation: Block validation failed for `toolset-views/view-pagination-block`

That seems due to differences of the saved and expected structure of the Block. This could be due to many reasons, inclusive bugs in Views, however I suspect some 3rd party interference here.

Note, I can also select the topic/specialties now (in the new view).
I can't see how the second View has a Filter yet (in your original template), so there is no input for the relationship filter too, you would have to add a search for that - like I did in the example
hidden link
Also note that for each filter you add (relationship) that filter won't be available again for the same search, as used already.

Now, to resolve all this, I need to know how you reached the situation.
I would need the steps you followed, then I can try to replicate that and see if it is a consistent bug.

In case you don't know how this precisely happened, (as I understand from your opening comment) the best here actually could be if you can provide me with a copy of the site.
I can then send that to the developers, for analysis, because I see some more issues than just the mentioned ones:
- So for example it seems you can not add new search queries at all to the *existing* template, and even worse, you cannot edit those views in a *native* way (which is a known limitation, but...) it makes it impossible to debug, or analyze what is happening since all we see is a "preload" - this is not useful for neither production or debug.
It needs to be adjusted IMHO and I would like to show this to the Developers so I have an example - and ask for improvements.

If you can add a Duplicate (https://toolset.com/faq/provide-supporters-copy-site/) *and* if possible outline the steps you took to reach this issue, I can then analyze each issue in depth and ask as well for improvements along of fixes.

Note, I think I can already say this issue will not be solved in a very short time - if you need this website online in less than a few weeks (which is the approximate schedule for the stable Views 3.0 official release) I would suggest to use the current stable Views instead, for production, because this will require some time (even if it is no BUG in Toolset, I would need at least until next Tuesday to analyze and provide eventual solutions (my weekend is in the way).

I have enabled a private form for a duplicate to be added.
I will try my best to find the core cause as soon as possible and let you work on - however this may take as said until next week.

Thank you for understanding and your patience!

PS:
If Duplicator for some reason fails, a Database Dump could be fine as well.

[Beda]

Thank you very much for this, and I am also glad you could switch to a fresh site - I truly hope you will not stumble over issues there, and of course we are here in case you do - it is very helpful to us when users report us the issues now, so we can fix them before a official release is made.

That said I escalated this ticket at first to myself in Second Tier Support where I will dissect the issues and prepare them for analysis by DEV.
Then, I will feedback here at least with causes, if not solutions.

Thank you for your patience in the meantime.

[logicelf]

Hi Beda (or anyone else who can help),

This appears to be a major issue for some reason. I have the exact same problem on a fresh install. All I have done is spin up a new WP installation, added Types and Views 3 and the Astra theme, and created some CPTs and relationships. Once again, having created a View in a content template with the block editor where I display related posts, that view block is now refusing to load in the Gutenberg UI. I've added two View blocks, and neither of them load when I come back to the content template:

hidden link

This may be extremely relevant: I have noticed that, when on the Toolset > Views page, the [Edit in the "Template for XXX"] links are not working - they all link back to the Toolset > Views page that I am already on. See this screenshot - the mouse cursor is hovering over the [Edit in the "Template for Topics"] link - now look at the URL at the bottom of the browser window:

hidden link

Is the Toolset UI in the content template perhaps attempting to load the assets from a location which doesn't exist? Something looks very broken here.

Again - this is a *brand new install* with the latest versions of Types, Views and Astra (with an empty child theme). There is no caching enabled.

I'd really, really appreciate some urgent assistance here - as I said to Beda, I need to have this site ready for content editors in a few days (Tuesday morning, actually!), and while I could certainly understand odd issues on a site where I'd tried a number of plugins to achieve different things, I was not expecting such a serious issue on a fresh install.

Thanks,

James

[Beda]

Is this working with another theme?
I am getting a fresh version of Astra as we speak to test this, but it's the first that comes to mind.

Also, can you explain the steps you take? I can then immediately try to replicate them locally.

I am also working on the issue as we speak

[Beda]

I've got it.
It's strange I could not see that before, as it seems so pretty straight forward to replicate!

1. Create a CT and add a new View
2. Choose pagination, filter and ordering
3. Choose a CPT
4. See the errors piling up in the console

I'm prioritizing now, thank you for the report.

[logicelf]

Thanks Beda. Glad you could replicate so easily - seems like quite a bad one! NB: I've reverted to the 2.9.x branch for now, as I needed to get a few Views built quickly. Once you've located and fixed the issue at that end, I may attempt to recreate with 3.0 beta - although I'm understandably nervous about doing that now. I know it's a beta, but it's been out a while - so I (perhaps mistakenly) assumed more stability at this point.

[logicelf]

Hi Beda,

To be honest, I'm too nervous at this point given the serious nature of this bug. Thanks for your support on this, and I'm glad you've isolated the root cause, but I'll stick with the 2.9.x branch for this project. May I ask what the plans are in terms of migration of data from 2.9.x to 3.x when Views 3 is out of beta? I assume there will be a lot of 'classic block' issues to deal with?

James

[Beda]

What I wanted to ask you is if you could test the beta I sent on the site you had sent me just to be sure we caught every detail.

I tested (and since I was able to replicate the issue you reported I am confident it is solved) - but 4 eyes see more than 2.

Now, I understand I cannot outsource testing to you, on the contrary 🙂 and do not insist neither expect you to do that, of course.
I unterstand you have your priorities, and respect this of course.

Related to "May I ask what the plans are in terms of migration of data from 2.9.x to 3.x when Views 3 is out of beta? I assume there will be a lot of 'classic block' issues to deal with?"
...

So, you will basically (as used to) just update. Of course, existing Views won't be editable in GutenBerg like "new" Views.
But you will be able to use them (as you can already see you can either create new or use existing views)
Errors should of course not happen, but there will be no "migration" of the Views to new edit modes. Old Views will stay like that, and there is a major reason for it too:
It's required for power users, because the Gutenberg, as you may already have experienced, is nowhere close what you can do right now in a native View.
You can for example not nest Views in the Gutenberg edition yet. You can not edit it's HTML as you can in a native View, and that is often required for "specific" usage cases.
That is also the reason the old edit method will stay, it will not be removed.

Please let me know if there is anything remaining unclear.

Thank you!

[logicelf]

If I get some time later this week, I will test.

Thanks for confirming - I'll stick with 2.9.x for the foreseeable future, I think.

[Beda]

OK, thank you for the report, the patience and persistence.

[logicelf]

No problem - thanks for your support, Beda. 🙂

[Beda]

I'm just setting this back to "I think it's resolved"
Please let me know if anything pops up

[logicelf]

My issue is resolved now. Thank you!