After copying my website from production to staging server, pages with wpDisCuz crash on load. There is a server error message attached indicating that some corner of wpDisCuz is looking for the comment-form.php file on the production server (which is inaccessible from staging). Any ideas on a workaround and/or fix? It's pretty inconvenient not to be able to work in staging although production wpDisCuz is just fine.
IN the attached "futureai" is production while "futureai1stg" is staging.
It looks like the attachment didn't get attached... there error message is:
[Sat Nov 11 15:31:15.577644 2023] [php:error] [pid 13355] [client 69.63.109.139:0] PHP Fatal error: Uncaught Error: Failed opening required '/nas/content/live/futureai/wp-content/plugins/wpdiscuz/themes/default/comment-form.php' (include_path='.:/usr/share/pear/php:/usr/share/php') in /nas/content/live/futureai1stg/wp-includes/comment-template.php:1618\nStack trace:\n#0 /nas/content/live/futureai1stg/wp-content/themes/salient-child/functions.php(19): comments_template()\n#1 /nas/content/live/futureai1stg/wp-includes/class-wp-hook.php(324): salient_child_page_comments('')\n#2 /nas/content/live/futureai1stg/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)\n#3 /nas/content/live/futureai1stg/wp-includes/plugin.php(517): WP_Hook->do_action(Array)\n#4 /nas/content/live/futureai1stg/wp-content/themes/salient/nectar/hooks/hooks.php(48): do_action('nectar_hook_aft...')\n#5 /nas/content/live/futureai1stg/wp-content/themes/salient/page.php(35): nectar_hook_after_content()\n#6 /nas/content/live/futureai1stg/wp-includes/template-loader.php(106): include('/nas/content/li...')\n#7 /nas/content/live/futureai1stg/wp-blog-header.php(19): require_once('/nas/content/li...')\n#8 /nas/content/live/futureai1stg/index.php(17): require('/nas/content/li...')\n#9 {main}\n thrown in /nas/content/live/futureai1stg/wp-includes/comment-template.php on line 1618
Please follow the steps mentioned in this FAQ: https://wpdiscuz.com/community/f-a-q/if-design-of-the-wpdiscuz-comment-form-is-broken/#post-10629
That works... thanks a lot,
Charles
