karlemilnikka

Excellent! Thanks a lot.

Unfortunately, it didn’t fix the issue. I do however have some good news since I’ve found a consistent way to replicate the bug.

1. Set up a fresh WordPress site. Install the latest version of LearnDash and any old version of Pods 2.8 (I’ve tested with 2.8.5 and 2.8.6).
2. Enable Shared Course Steps in LearnDash.
3. Extend the course post type (sfwd-courses) with a field.
4. Create a course called Course A. Its relative URL will be /courses/course-a/.
5. Update Pods 2.8 to the latest version and check what happened to the courses. The title of the course listing page has been changed to sfwd-courses (previously Courses) and Course A’s relative URL has become /sfwd-courses/course-a/.

If you would like to see this in action, I’ve installed a fresh WordPress site with only LearnDash and Pods running. I’ve also made a screen recording demonstrating the issue. I can send you the video together with the demo sites’s admin credentials through any private channel.

Sounds amazing. I still haven’t figured out what’s triggering the issue after the last update. I’ll install the update tomorrow, test it for a week and then mark this support ticket as solved.

Unfortunately, the update just solved the way I triggered the bug, not the underlying issue. I keep investigating.

Thanks for your quick reply. The 2.8.5 update seems to have fixed the issue. Thank you very much.

• This reply was modified 3 years ago by karlemilnikka.

Just to chime in, we have the same issue with console errors.

@bsfherman I can confirm that the new version solved the issue. Thanks!

Best regards
Karl Emil Nikka

@bsfherman Always happy to help the developers of my favourite WordPress theme. Do you want me to install a demo-site showing the issue (like I did with the previous bug-reports)?

Best regards
Karl Emil Nikka

Hi @bsfherman. I’ve now done some further investigation. It seems like it’s the combination of Custom Fonts and Updraft Plus that triggers the console error.

Best regards
Karl Emil Nikka

@bsfherman I haven’t done any further research since we are phasing out the plugin. I just wanted to chip in with a confirmation and tell you that the issue isn’t solely related to Jetpack. I can look into it further later this week if it would be of help.

I haven’t noticed any negative affects on the site because of the error.

Best regards
Karl Emil Nikka

Just FYI, I can confirm that we have the same issue on one of our sites (not running Jetpack).

Best regards
Karl Emil Nikka

@brainstormteam Thanks. We’re almost done replacing this plugin, but I’m glad for all other users that you’ve added this feature.

(We’re sticking to your Astra Theme and your core Astra Pro plugin, which both are amazing. For planning and production reasons, we cannot rely on other Brainstorm Force addons.)

It is the same plugin. I’m an Astra Pro customer as well. I really love the Astra theme for its developer hooks, SEO mark-up, WCAG compatibility and CSS file generation, but I stay away from their addons.

Just to chime in (and in case new users see this thread), we’re running this plugin on WordPress 5.7 without any issues or error messages in the console.

Here are the historical ETAs for this feature.

1. July 2020: “Probably by next month”
2. August 2020: “Probably by the end of this month”
3. September 2020: “By the end of next month”
4. November 2020: “Probably by the next week or month-end”
5. December 2020: “Early next week”
6. December 2020: “First week of January”
7. February 2021: “Mid-February or a week after that”
8. March 2021: “Stay tuned!”