Database gone away is a timeout issue, a hosting issue. Also an out of memory or some other sql setting (like max allowed packet for example).
Also you still have js issues (Firefox).
Uncaught TypeError: $percyslider417560831.unslider is not a function
@dimalifragis Thanks for pointing that out man, thought i had got rid of them but i dont use firefox so didnt check there.
Do you know how I could fix this?
@percysgrowroom Funny thing is that with Chrome i see no issue like the above.
It seems to be a conflict between some "slider" and advanced ads, i would bet to the slider thing. Try to disable it for a while and see what is the causing plugin.
If advanced ads is doing that and if you do not have the paid version, there best for all kind of ads is https://wordpress.org/plugins/ad-inserter/ , nothing like it. You can even show ads within wpForo areas WITHOUT the wpForo plugin for ads (sorry gvectors for writing that).
I'll comment on the error logs later.
At the moment, I want to say your forum is not slow. It loads pages very fast. I didn't see any issues with the loading speed. Please logout and check your website as guest, it works like a rocket.
@robert yes robert, sometimes it does lol. Its as if over time itll get worse. It has been working fine since this morning, and maybe the issue is fixed now.
The host said there was a wordpress command that kept repeating or something? Too majny MySQL request for databases.
Too hot in my office so its hard to keep track of the info lol.
But it seems ot be working ok for now. I have optmised all databases. everything is on InnoDB except for likes and visits, they are on Mysam.
Hopefully we are good now, but we will see..... thanks for your help everyone
@robert yes robert, sometimes it does lol. Its as if over time itll get worse. It has been working fine since this morning, and maybe the issue is fixed now.
Apparently the issue happens under LOAD. Some bot, some attack or just many concurrent users.
@dimalifragis I am going to reinstall cloudlfare on my site hope it will prevent that happening again. Thanks for the info man
We could look deeper if you contact us via support[at]gvectors.com and provide appropriate access to the website.
@robert I would appreciate that. But right now everything is working fine i think, and Dimalfragis might be right with the bot/ attack/ thing.
Ill add cloudflare to my site after i have done a back up, and if the problem carries on ill take you up on that offer 🙂
But if you would like to take a look anyway to see the error logs, you guys already have an account at my site, so feel free to log in with that. It might help find any bugs.
Let me know if you would like to take a look.
yer there is still problems 🙁 Ill email youll at gvectors
Found all these:
- [21-Jul-2021 16:03:24 UTC] PHP Fatal error: Uncaught Error: Unsupported operand types in /home/percysgr/public_html/wp-content/plugins/wpforo/wpf-includes/functions.php:2112
- [21-Jul-2021 16:03:24 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/percysgr/public_html/wp-content/plugins/wpforo/wpf-includes/functions.php on line 2106
- [21-Jul-2021 16:03:24 UTC] PHP Warning: Illegal string offset 'attachment_sizes' in /home/percysgr/public_html/wp-content/plugins/wpforo-advanced-attachments/wpforoattach.php on line 716
- [21-Jul-2021 16:03:24 UTC] PHP Warning: Illegal string offset 'attachments' in /home/percysgr/public_html/wp-content/plugins/wpforo-advanced-attachments/wpforoattach.php on line 715
- [21-Jul-2021 16:03:24 UTC] PHP Warning: Illegal string offset 'newest_member_profile_url' in /home/percysgr/public_html/wp-content/plugins/wpforo/wpforo.php on line 715
- [21-Jul-2021 16:03:24 UTC] PHP Warning: Illegal string offset 'newest_member_dname' in /home/percysgr/public_html/wp-content/plugins/wpforo/wpforo.php on line 714
- [21-Jul-2021 16:03:24 UTC] PHP Warning: Illegal string offset 'newest_member' in /home/percysgr/public_html/wp-content/plugins/wpforo/wpforo.php on line 713
- [21-Jul-2021 16:03:24 UTC] PHP Warning: Illegal string offset 'online_members_count' in /home/percysgr/public_html/wp-content/plugins/wpforo/wpforo.php on line 708
- [21-Jul-2021 16:03:24 UTC] PHP Warning: Illegal string offset 'members' in /home/percysgr/public_html/wp-content/plugins/wpforo/wpforo.php on line 707
This error says the server is crashed. This is not wpForo issue for sure. Something wrong with your server. Your server doesn't work stable, it goes done and generates tons of errors by plugins and WordPress. You should contact the server support and ask then check the performance. They should find the file which cause this issue. This could be a spammer attack or even a virus in your WordPress files. In any case, we'll login and do a quick check today.
@robert My host says this mate:
As for the PHP-related logs, most of them are warning messages, you can ignore the warning message. However, I found the following error message for PHP:
----------
PHP Fatal error: Uncaught Error: Unsupported operand types in /home/percysgr/public_html/wp-content/plugins/wpforo/wpf-includes/functions.php:2112
-----------
This is related to coding and unfortunately, we have very limited knowledge of coding. This error is related to your plugin "WP Foro". You will need to contact the plugin provider to check this further. I hope this will help. If you still encounter slowness with your website, please share more details.
SO i have them telling me its wpforo, and i have telling me its them.......
All are wpForo errors, nobody says they are not wpForo errors. But why all these wForo error happens? The reason is not in wpForo. The problem is the server. When the server goes down, the values in the functions become null, and they generate Fatal errors and all other type of errors. So if the server works fine, the errors you're mentioning has no change to be generated.
So you're looking at the problem from reverse side. We should understand why your server goes down. Currently we're adding some hooks in the wpForo core to be able to do a deeper debug. The update comes very soon. Once you've updated, we'll ask you to use some hook codes to see the problem origin.
