Skip Navigation

[Resolved] Events Calendar content not displaying but shows in Beaver Builder edit mode

This support ticket is created 5 years, 2 months 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 – 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 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 9 replies, has 3 voices.

Last updated by Shane 4 years, 12 months ago.

Assisted by: Shane.

Author
Posts
#1516379

I have created a powerpoint with four slides that demonstrate the issue hidden link
This is the page this appears on hidden link
This is a test site so you can do whatever you want on it, login details are in powerpoint.

Additionally, and perhaps related, I am getting a critical error on the Toolset settings page and this is what WordPress automatically emailed me:
Error Details
=============
An error of type E_ERROR was caused in line 105 of the file /nas/content/live/aetherius1/wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php. Error message: Uncaught TypeError: Argument 1 passed to Google\Site_Kit\Core\REST_API\REST_Routes::register_routes() must be an instance of WP_REST_Server, string given, called in /nas/content/live/aetherius1/wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php on line 93 and defined in /nas/content/live/aetherius1/wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php:105
Stack trace:
#0 /nas/content/live/aetherius1/wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php(93): Google\Site_Kit\Core\REST_API\REST_Routes->register_routes('')
#1 /nas/content/live/aetherius1/wp-includes/class-wp-hook.php(288): Google\Site_Kit\Core\REST_API\REST_Routes->Google\Site_Kit\Core\REST_API\{closure}('')
#2 /nas/content/live/aetherius1/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(NULL, Array)
#3 /nas/content/live/aetherius1/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#4 /nas/content/live/aetherius1/wp-content/plugins/wp-views/vendor/toolset/common-es/php/B

#1516453

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Julian,

Thank you for getting in touch.

Could you download the latest version of views and see if it resolves the issue for you.
https://toolset.com/download/toolset-views/

Thanks,
Shane

#1516723

Thanks, I've done this but the issues still persist.

#1516995

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Julian,

I've added your ticket to the Toolset settings page issue as this is a known issue escalated to our compatibility team.

Also for your, the problem is that your page is a taxonomy, because of this the shortcodes that you are using to get the post parent information in the breadcrumbs wont work. The shortcodes are expecting to be on a post page template like here hidden link

If you were to add it to a section that is actually listing out the events then you will see that it should work since the post objects are being listed out there.

Hopefully this clears things up for you.

Thanks,
Shane

#1522325

Regarding the shortcodes, these are now working again after The Events Calendar has made an update. However, it sounds like I am using them incorrectly and that its kind of accidental that they are working. Are you able to advise how I can get the same result a more correct way please?

#1525731

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Julian,

Usually the shortcodes that you are using are used in the post templates themselves.

From what I see your breadcrumbs isn't necessarily linked to each other. This means your format from what I see isn't Grandparent->Parent->Child.

I'm not able to go to the parent and then navigate back to the child from the parent page. Your parent pages are completely different slugs in the browser.

I hope I was able to clear this up for you.

Thanks,
Shane

#1525791

Thanks Shane. Our breadcrumb is exactly how we want it to be and there's a long boring reason for it. We're able to use the Toolset code to display things that way. But what you've said is that it shouldn't really work this way. So I'm asking, is there another 'correct' way to get the breadcrumb on that page to display exactly as it is?

Essentially, we want this archive page to be related to a post. It seems your plugin can relate one post type to another, or a post type to a taxonomy, but we're wanting to relate a specific taxonomy archive page to a single post. Is that possible? Or is there another way to achieve the same result?

#1529251

Hi, Shane is out today for a national holiday and will return tomorrow to continue assisting you.

#1530651

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Julian,

The only reason why i said it shouldn't work like this is because you're using the [wpv-post-link] shortcode on a taxonomy.

So in an ideal case for your taxonomy archive page when the shortcode is used in the area that you've used it then it wouldn't render anything.

The only way that it is rendering correctly right now is because there seems to be some post data rendering where the shortcode can grab the information from.

If this is the case then there wouldn't be anything to worry about because post data is being provided.

Thanks,
Shane

#1617403

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Julian,

Our Latest series of updates have resolved this issue with a permanent fix.

You can update your plugins by going to Plugins Add New and click on the commercial tab.

Finally just click on "Check for Updates" and your page should refresh showing the updates.

This should now resolve the issue.

Thanks,
Shane