Skip Navigation

[Escalated to 2nd Tier] Views error with ClassicPress

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 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Sao_Paulo (GMT-03:00)

This topic contains 7 replies, has 2 voices.

Last updated by Mateus Getulio 3 weeks, 1 day ago.

Assisted by: Mateus Getulio.

Author
Posts
#2778303

Hi,

I'm trying to use Views with ClassicPress which is a pre-Gutenberg fork of WordPress.

hidden link

It should work but I am getting a Gutenberg block-related error.

Fatal error: Uncaught Error: Class "WP_Block_Parser" not found in C:\Users\test\Local Sites\classic-test\app\public\wp-content\plugins\wp-views\backend\Services\ViewParsingService.php:330 Stack trace:

#0 C:\Users\test\Local Sites\classic-test\app\public\wp-content\plugins\wp-views\backend\Services\Bootstrap.php(197): OTGS\Toolset\Views\Services\ViewParsingService->find_block_in_text('<!-- wp:paragra...', 'toolset/view')

#1 C:\Users\test\Local Sites\classic-test\app\public\wp-includes\class-wp-hook.php(310): OTGS\Toolset\Views\Services\Bootstrap->convert_legacy_block_markup(Object(WP_Post))

#2 C:\Users\test\Local Sites\classic-test\app\public\wp-includes\class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)

#3 C:\Users\test\Local Sites\classic-test\app\public\wp-includes\plugin.php(565): WP_Hook->do_action(Array)

#4 C:\Users\test\Local Sites\classic-test\app\public\wp-includes\class-wp-query.php(4697): do_action_ref_array('the_post', Array)

#5 C:\Users\test\Local Sites\classic-test\app\public\wp-includes\class-wp-query.php(3657): WP_Query->setup_postdata(Object(WP_Post))

#6 C:\Users\test\Local Sites\classic-test\app\public\wp-admin\includes\dashboard.php(1020): WP_Query->the_post()

#7 C:\Users\test\Local Sites\classic-test\app\public\wp-admin\includes\dashboard.php(953): wp_dashboard_recent_posts(Array)

#8 C:\Users\test\Local Sites\classic-test\app\public\wp-admin\includes\template.php(1338): wp_dashboard_site_activity('', Array)

#9 C:\Users\test\Local Sites\classic-test\app\public\wp-admin\includes\dashboard.php(279): do_meta_boxes(Object(WP_Screen), 'normal', '')

#10 C:\Users\test\Local Sites\classic-test\app\public\wp-admin\index.php(182): wp_dashboard() #11 {main} thrown in C:\Users\test\Local Sites\classic-test\app\public\wp-content\plugins\wp-views\backend\Services\ViewParsingService.php on line 330

#2778388

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello there,

Based on the debug log you shared I assume you only have a local version of this site, is that correct?

May I ask you to kindly replicate this issue to a sandbox containing a fresh version of WordPress and Toolset where we can understand and debug this issue?

Please use this link to login and reproduce the issue:

hidden link

Please give us a heads up once it is done so we can move forward with the next steps of the troubleshooting.

Thank you,
Mateus

#2778429

Hi, this is what I have done with the sandbox.

1. I migrated the site to ClassicPress 2.2.

2. I installed Views to the site.

3. I deactivated the other Toolset plugins.

The site now shows a critical error, which must be the same error I am getting.

However I cannot login at the moment because the link you sent no longer works, but I have now reproduced my error in the sandbox.

thanks

#2778697

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello Farrel,

I apologize for the delay due to the weekend.

I tried recovering the sandbox but I couldn't do it so far.

I'm sorry about the back and forth, but can we try a different approach?

Is it possible for you to share a package/zip version of the site that I can import locally and debug the issue? Since applying it to the sandbox causes it to crash, I'm afraid sharing the snapshot/package of your local site is the best way to debug it.

You can use the plugin Duplicator(hidden link) to create a full copy of your website so we can take a look at it and see what's causing the issues you're experiencing.

Please check this tutorial on how to create a Duplicator package here: https://wpml.org/faq/provide-supporters-copy-site/

If you come across problems while creating it, please feel free to ignore(exclude from the backup) both uploads and cache folders.

I'm enabling the proper field for your to share this copy, you'll see it on your next response.

Alternatively, you may use any file sharing service that you prefer and share the link in the ticket(your next response is being marked as private, only you and I have access to it).

Thank you, please let me know.

#2778717

Hi, the easiest way for you to do this is just setup a WordPress install and then use the ClassicPress plugin to convert the site to ClassicPress which is a fork of WordPress pre-Gutenberg.

hidden link

Then just install a copy of Views and you will see the error.

#2778894

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi Farrel,

I was able to recover the Sandbox login link:

hidden link

I added a post type and created a view with it. I inserted a view to a page and it doesn't seem to be working indeed, I get a nearly blank page in the front end. However, the error log I get is different from the one you reported so I'm unsure it is the same issue, I just want to double-check.

Can you please tell me what are the replication steps I can take in order to see the same issue you have locally, or is it now the same issue you have?

Thank you, please let me know and I'll go ahead and escalate it to our team for further review and fix.

#2780493

Hi, sorry for the delay.

The main issue here is that I need Toolset to work correctly with ClassicPress. So even if our errors are not identical, there seems to be a problem with Toolset running on ClassicPress.

#2781722

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi,

I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue and will try to find a solution.

I will get back to you as soon as I get an answer from them.

Best regards,
Mateus