Jason Crouse

Dear @saf0,

you may want to start here:

Common WordPress Errors

and if you can’t solve the issue, please post a support request here:

https://wordpress.org/support/forum/how-to-and-troubleshooting/

Someone seems to have encountered a similar issue a few years ago:

https://wordpress.org/support/topic/warning-mysqli_num_fields-error-with-w3-cache-plugin-on-my-site/page/2/

Best,
Jason

• This reply was modified 6 years, 7 months ago by Jason Crouse.

Hi @nextstep99

thank you for your kind words, I’m glad you find Slimstat useful!

First things first: DO NOT UNINSTALL Slimstat, or you will lose all your data.

These errors you’re getting seem to be related to inability of the plugin to save the new version number in the database, which stops the attempts to update the database. If you look at phpMyAdmin, there’s a table called wp_options, and inside there’s a row called slimstat_options:

SELECT * FROM wp_options WHERE option_name = ‘slimstat_options’

At the very beginning of the value string, there should be something that says:

a:81:{s:7:”version”;s:7:”4.8.7.2″;s…

Please make sure that the version number in that string matches your Slimstat version. Noticed that number s:7 before the version itself? That’s the number of characters in the following string, so if your version number is 4.8.7, change s:7 to s:5 as well.

I hope this helps. If it doesn’t don’t hesitate to send me a message via https://support.wp-slimstat.com/ and we will dig deeper into your issue.

Jason.

Hi @51nullacht

thank you for pointing it out. The syntax we use is indeed correct, as the => operator assigns an unnamed function to the filter, as you can see in:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/filter

This is valid ECMAScript 6 syntax, however it looks like IE11 doesn’t accept it. A way to solve this issue is to turn that declaration into a separate named function:

https://alligator.io/js/filter-array-method/#targetText=filter()%20Array%20Method%20in%20JavaScript&targetText=The%20item%20argument%20is%20a,sent%20to%20the%20new%20array.

We will add a fix for this issue to our next release.

Best,
Jason

We discussed this with the developer, and decided to cautiously reintroduce this feature. Hopefully this time around it won’t cause any major troubles.

Hi @anniest,

this is currently not possible via the Settings interface. We removed this feature because people were resetting their options by mistake more than what we thought it was normal. However, you can connect to phpMyAdmin, and inside the wp_options table, find a row that has key ‘slimstat_options’, and delete it. This will reset your settings. Please let me know if you need step-by-step instructions.

Best,
Jason

Sorry, one last thing. The German localization team is asking me on Slack to share this link with you to learn more about certain rules they have when translating technical terms:

https://slack-files.com/T02TLC6BA-F9VR33F1V-42c2fd2c07

They said that you can definitely join their Slack community, if you want to learn more and have any questions about the process of becoming an approver for Slimstat/German.

Jason

Thank you so much! The threshold for the repo to start pushing the file to all the active installs out there is currently set to 95%, which in our case means reducing the number of untranslated strings to less than 50. Do you think you could submit a translation for another 60-70 strings or so? This way I can submit a request to approve them and that will take care of adding the new German localization to our package!

https://translate.wordpress.org/projects/wp-plugins/wp-slimstat/stable/de/default/?filters%5Bstatus%5D=untranslated&sort%5Bby%5D=priority&sort%5Bhow%5D=desc

Again, thank you for you hard work so far!
Jason

• This reply was modified 6 years, 8 months ago by Jason Crouse.