The effects of alcohol on sustanon 250 leucine for – real weight loss & bodybuilding benefits?
Search
Close
AI Search
Classic Search
 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

AI Assistant
Fatal Error: Class ...
 
Notifications
Clear all

Bug Fatal Error: Class “WpdiscuzHelper” Not Found

11 Posts
2 Users
1 Reactions
675 Views
Posts: 6
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@mehdi)
Active Member
Joined: 10 months ago
[#10344]

Dear wpDiscuz Support Team,

After i update wordpress to 6.7 and above, i have faced several bugs from wpdiscuz. I am writing to report a fatal error I encountered on my WordPress website after a recent update or installation of the wpDiscuz plugin. I am receiving the following error:

Fatal error: Uncaught Error: Class “WpdiscuzHelper” not found in /var/www/html/blog/wp-content/plugins/wpdiscuz/themes/default/comment-form.php:6 Stack trace: #0 /var/www/html/blog/wp-content/plugins/wpcodebox2/src/Runner/QueryRunner.php(126) : eval()’d code(12): include() #1 /var/www/html/blog/wp-includes/shortcodes.php(434): my_wpdiscuz_shortcode(Array, ”, ‘wpdiscuz_commen…’) #2 [internal function]: do_shortcode_tag(Array) #3 /var/www/html/blog/wp-includes/shortcodes.php(273): preg_replace_callback(‘/\[(\[?)(wpdisc…’, ‘do_shortcode_ta…’, ‘[wpdiscuz_comme…’) #4 /var/www/html/blog/wp-content/themes/bricks/includes/elements/shortcode.php(96): do_shortcode(‘[wpdiscuz_comme…’) #5 /var/www/html/blog/wp-content/themes/bricks/includes/elements/base.php(2630): Bricks\Element_Shortcode->render() #6 /var/www/html/blog/wp-content/themes/bricks/includes/frontend.php(623): Bricks\Element->init() #7 /var/www/html/blog/wp-content/themes/bricks/includes/elements/container.php(968): Bricks\Frontend::render_element(Array) #8 /var/www/html/blog/wp-content/themes/bricks/includes/elements/base.php(2630): Bricks\Element_Container->render() #9 /var/www/html/blog/wp-content/themes/bricks/includes/frontend.php(623): Bricks\Element->init() #10 /var/www/html/blog/wp-content/themes/bricks/includes/elements/container.php(968): Bricks\Frontend::render_element(Array) #11 /var/www/html/blog/wp-content/themes/bricks/includes/elements/base.php(2630): Bricks\Element_Container->render() #12 /var/www/html/blog/wp-content/themes/bricks/includes/frontend.php(623): Bricks\Element->init() #13 /var/www/html/blog/wp-content/themes/bricks/includes/elements/container.php(968): Bricks\Frontend::render_element(Array) #14 /var/www/html/blog/wp-content/themes/bricks/includes/elements/base.php(2630): Bricks\Element_Container->render() #15 /var/www/html/blog/wp-content/themes/bricks/includes/frontend.php(623): Bricks\Element->init() #16 /var/www/html/blog/wp-content/themes/bricks/includes/frontend.php(758): Bricks\Frontend::render_element(Array) #17 /var/www/html/blog/wp-content/themes/bricks/includes/frontend.php(1005): Bricks\Frontend::render_data(Array) #18 /var/www/html/blog/wp-content/themes/bricks/single.php(15): Bricks\Frontend::render_content(Array) #19 /var/www/html/blog/wp-includes/template-loader.php(106): include(‘/var/www/html/b…’) #20 /var/www/html/blog/wp-blog-header.php(19): require_once(‘/var/www/html/b…’) #21 /var/www/html/blog/index.php(17): require(‘/var/www/html/b…’) #22 {main} thrown in /var/www/html/blog/wp-content/plugins/wpdiscuz/themes/default/comment-form.php on line 6


10 Replies
Asti
Posts: 8211
 Asti
Support
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@asti)
Illustrious Member
Joined: 8 years ago

Hi,

Please confirm that you're using the [wpdiscuz_comments] shortcode to enable wpDiscuz on your posts/pages.


Reply
Posts: 6
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@mehdi)
Active Member
Joined: 10 months ago

I confirm that. im using [wpdiscuz_comments]


Reply
2 Replies
Asti
 Asti
Support
(@asti)
Joined: 8 years ago

Illustrious Member
Posts: 8211
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian

@mehdi 

This issue will be fixed in the next update. 


Reply
(@mehdi)
Joined: 10 months ago

Active Member
Posts: 6
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian

@asti 
We still have this issue: 

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpdiscuz domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/blog/staging/wp-includes/functions.php on line 6114


Reply
Posts: 6
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@mehdi)
Active Member
Joined: 10 months ago

ok thank you. i also update the wordpress in a staging site and i face this error:

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpdiscuz domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/blog/staging/wp-includes/functions.php on line 6114


Reply
1 Reply
Asti
 Asti
Support
(@asti)
Joined: 8 years ago

Illustrious Member
Posts: 8211
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian

@mehdi 

Please let us know which addons you are using and their versions.


Reply
Posts: 6
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@mehdi)
Active Member
Joined: 10 months ago

i just use the free version of wpdiscuz and i deactivated all other plugins and when i activate wpdiscuz i get this error: 

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpdiscuz domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/blog/staging/wp-includes/functions.php on line 6114 Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blog/staging/wp-includes/functions.php:6114) in /var/www/html/blog/staging/wp-admin/includes/misc.php on line 1438 Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blog/staging/wp-includes/functions.php:6114) in /var/www/html/blog/staging/wp-includes/functions.php on line 7137 Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blog/staging/wp-includes/functions.php:6114) in /var/www/html/blog/staging/wp-admin/admin-header.php on line 9


Reply
3 Replies
Asti
 Asti
Support
(@asti)
Joined: 8 years ago

Illustrious Member
Posts: 8211
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian

@mehdi 

We'll check and get back to you soon. 


Reply
(@mehdi)
Joined: 10 months ago

Active Member
Posts: 6
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian

@asti hey guys, any news on this issue?


Reply
Asti
 Asti
Support
(@asti)
Joined: 8 years ago

Illustrious Member
Posts: 8211
Asti
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian

@mehdi 

We don't find such an issue on our test websites. Could you please send the admin login details to info[at]gvectors.com email address? I'll ask the developers to check the issue for you.


Reply
Share: