Uncaught ValueError

Resolved

(@hojabra)

My website is working fine in Frontend but in the backend every time I try to open any URL related to WPForms it’ll give me error. Please update the plugin. I cannot downgrade WordPress or PHP version, before upgrading them to the newer version it was fine.
WordPress: 6.1.1
Theme: The7 11.6.0.1
PHP: 8.1.17
WPForms Lite: 1.8.0.2

Error Detail:

An error of type E_ERROR occurred on line 121 of file /home2/ojdogemy/public_html/gfxcraft/wp-content/plugins/wpforms-lite/src/Admin/Education/Core.php. Error message: Uncaught ValueError: Unknown format specifier " " in /home2/ojdogemy/public_html/gfxcraft/wp-content/plugins/wpforms-lite/src/Admin/Education/Core.php:121
Stack trace:
#0 /home2/ojdogemy/public_html/gfxcraft/wp-content/plugins/wpforms-lite/src/Admin/Education/Core.php(121): sprintf('\xD9\x85\xD8\xAA\xD8\xA7\ xD8\xB3\xD9\x81\xDB\x8C\xD9\x85\xD8...', '%name%')
#1 /home2/ojdogemy/public_html/gfxcraft/wp-content/plugins/wpforms-lite/src/Admin/Education/Core.php(75): WPForms\Admin\Education\Core->get_js_strings()
#2 /home2/ojdogemy/public_html/gfxcraft/wp-content/plugins/wpforms-lite/src/Lite/Admin/Education/Core.php(31): WPForms\Admin\Education\Core->enqueues()
#3 /home2/ojdogemy/public_html/gfxcraft/wp-includes/class-wp-hook.php(308): WPForms\Lite\Admin\Education\Core->enqueues('toplevel_page_w...')
#4 /home2/ojdogemy/public_html/gfxcraft/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#5 /home2/ojdogemy/public_html/gfxcraft/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#6 /home2/ojdogemy/public_html/gfxcraft/wp-admin/admin-header.php(118): do_action('admin_enqueue_s...', 'toplevel_page_w...')
#7 /home2/ojdogemy/public_html/gfxcraft/wp-admin/admin.php(239): require_once('/home2/ojdogemy...')
#8
   thrown

Viewing 9 replies - 1 through 9 (of 9 total)

Nik Sebastian
(@niksebastian)

3 years, 2 months ago

Hey @hojabra – This likely seems to be a translation issue.

Please check if your Site Language strings are updated here

Also, please check if the Site translation is updated the latest.

Thanks,

Thread Starter hojabra
(@hojabra)

3 years, 2 months ago

Site language (Persian) strings are 95% stable, my website translation is updated.
but the problem still exists.

Nik Sebastian
(@niksebastian)

3 years, 2 months ago

Hi @hojabra – Sorry about the trouble you are facing here!

To begin with, Could you please go ahead and update the plugin to the current latest version that is Version 1.8.1.1 ?

When you get the chance, would you mind helping me with the exact steps to replicate the issue?

I tried to replicate the issue on my fresh install with WP version with fa_IR-6.1.1 and could not replicate any errors. In case it helps, here is a reference screencast recorded.

Please review and let me know and we’ll be happy to help!

Thanks 🙂
Thread Starter hojabra
(@hojabra)

3 years, 2 months ago
Before I got your message, I updated to the latest version, no fix there…
Here’s what I did so far:
Removed the plugin.
Cleared the cache.
Cleaned up database.
Cleaned up wp-plugins.
Removed some translator plugins that might be in conflict with WPForms.
Disabled all the plugins.
Re-installed WPForms.

But, the problem still exists.

In the video the menu of the plugin is still English for you, mine is in Persian.
- This reply was modified 3 years, 2 months ago by hojabra.
Nik Sebastian
(@niksebastian)

3 years, 2 months ago

Hi @hojabra – Thank you for your patience here!

As you can see in the screencast that it indicates that the Site Language is set to fa_IR — Please see the reference screenshot

I just translated the page to English using the Safari Browser Translate.

However, I was not able to replicate the issue. Would you mind sharing any specific steps to replicate the issue? Or a screencast? So that we can take a closer look.

Thanks, and please let me know 🙂

Nik Sebastian
(@niksebastian)

3 years, 2 months ago

Hi @hojabra

We haven’t heard back from you in a while, so I’m going to go ahead and close this thread for now. But if you’d like us to assist further, please feel welcome to continue the conversation.

Thanks!

Thread Starter hojabra
(@hojabra)

3 years, 2 months ago

Wow! you couldn’t have just wait 48 hours, you’ve just marked the topic resolved after a short 24 hours!! What a support! I’ve waited 3 days for an answer you’ve just repeating what you’ve said at first and you don’t have the courage to say you don’t know how to fix it.
I’ve fixed the problem myself: SOLUTION: DONT’T USE THIS USELESS PLUGIN.
for the WordPress team: this problem hasn’t been resolved, not by this kind of support.

Nik Sebastian
(@niksebastian)

3 years, 2 months ago

Hi @hojabra

I apologize for incorrectly marking this issue as resolved before receiving a response from you. While we would like to assist you, however, it is impossible to provide a solution if we cannot replicate the errors you are experiencing. Is there any additional information you can provide about your environment that may aid us in reproducing the issue? Our goal is to provide you with a quick resolution.

Sincerely,

Nik Sebastian
(@niksebastian)

3 years, 1 month ago

Hi @hojabra,

I wanted to follow up with you regarding our previous conversation. Unfortunately, we haven’t received any response from you in a while, and as a result, we are closing this thread.

Please don’t hesitate to reach out to us if you need further assistance. We value you, and we want to ensure that you have the best possible experience with us. We are always here to help, and we will be happy to address any questions or concerns you may have.

Thank you for your understanding, and we look forward to hearing from you soon.

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Uncaught ValueError’ is closed to new replies.