PHP Main Menu error with Pro Theme

Support
#1

Hey folks, randomly today I got this error popping up above my main menu on my website. I had not run any updates that I’m away of that led to this, and my hosting company says the problem is with the theme. Can someone please help me troubleshoot this to get it fixed asap?

The error occurs on www.kyleandrew.com

***EDIT I should note that I had my server companies tech support switch the theme to a standard one and the error message went away

Thank you,

PHP by - Version 2.6.6dev - August 28th 2003

#2

Can anyone confirm if this support forum is still active or not?

#3

Hello @Kyle_Andrew,

Thanks for writing in! Just for future topics, self responding or bumping your post pushes it back in our Queue system so it takes longer to respond to.

Meanwhile, please make sure that you have meet the requirements to run the latest WordPress version. That is the basis to run X theme and Cornerstone plugin. You can check out the following links:

You can go to X > Status, copy the results and paste it in your next reply so that we will have an idea of your server settings.

Best Regards.

#4

Thank you. I’d love to be able to do that but as of whatever this problem is, I can no longer log into my wordpress dashboard.

Also, from the wp-login.php page I attempted to do a password reset, clicked the link in the email, and then was taken to a page that simple showed that PHP error from my above screen shot and nothing to actually reset a password.

#5

Hey @Kyle_Andrew,

The issue in your site is you’re using a very old version of PHP. 2.6.6. Can you confirm that with your host? Because if that is the case, WordPress does not support that and in turn, we do not support that too.

Please tell your host to upgrade PHP to at-least version 5.6+

Thanks.

#6

My site/server was using PHP 7.2 until this morning at which point I upgraded it to PHP 7.3 to see if that helped/fixed it. Which it didn’t. Also, the site was completely fine until recently so that cannot be the issue or it wouldn’t have worked before. It has been eons since I had a PHP version older than 5.6

#7

Hi @Kyle_Andrew,

Do you think your site was compromised? I have not seen that table error before and there is little to no information about it on Google. Would you mind reinstalling your Wordpress and Pro theme?

How to Reinstall WordPress: 5 Different Methods Depending On Your Needs

You can download a fresh copy of Pro here, and upload that via FTP or cPanel File Manager.

You can also try deactivating your plugins via FTP and see if that resolves the issue.

Deactivate (disable) Wordpress plugin via FTP

Let us know how it goes,
Cheers!

#8

Okay so I’m beginning to go through this process and after reinstalling Wordpress as per the above instructions nothing has changed, I am still unable to log in to the back end of the site. However when I went to reinstall/upload the PRO files, I noticed there were three directories in the themes folder:

Pro
TwentyTwenty
vnbvmbmvnbmvs

I have no idea what that last directory is, and it was created on Feb 3rd 2020 (I had not looked at this site to discover this problem since then until I posted my original support message)

Within that directory there is only a index.php file and a style.css file

I am tempted to remove it but do not want to do so until someone gives me their interpretation of this.

#9

Hello @Kyle_Andrew,

Please remove vnbvmbmvnbmvs folder. This could be malware or something. For safety reasons, please do scan your server first for any other malicous files that could also be causing the issue.

Kindly let us know how it goes.

#10

I thought I would circle back and post the outcome of this. I contacted my host and they ran a Malware scan. They found the problem in the file at:

/wp-content/themes/pro/framework/load/roman.php

They switched my theme to 2020, I went into the FTP and deleted the file, then switched back to pro and the problem was fixed. I additionally changed all admin passwords, and my database password. That file was dated Feb 4th and there is no clear answer as to how it got there, so keep a look out.

#11

Hello @Kyle_Andrew,

It’s good to know that the issue has been resolved.
Please don’t hesitate to open another thread if you need anything else we can help you with.

Regards.

#12

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.