• Resolved JoyceD6

    (@joyced6)


    I think it happened after upgrading the OS to latest earlier this week and then I was also able to upgrade the plugins. I was logged in at the time, so downloaded a plugin to troubleshoot and I thought it was telling me that the top version of PHP I could use was 8.0. The server was telling me that I was using 7.4 and it was no longer supported & they wanted to charge & after I quit the support chat & before I could communicate to the site owner, they changed the PHP to 8.4. It now has 8.0. I moved all my plugins to a defunct folder one by one deleting my cache and refreshing the site homepage and admin page but it’s still broken. I also changed the favicon to make sure I’m on the current site. What do I do now?

    I also get a white screen on?https://brandywinemd.com/history/historic-william-w-early-house/the-early-family-photos/?but not on other pages in the same folder such as?https://brandywinemd.com/history/historic-william-w-early-house/william-w-early-house-photos/

    • This topic was modified 2 months, 1 week ago by JoyceD6.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter JoyceD6

    (@joyced6)

    The reason for the error should be visible in the error log. You can find it in your hosting area. If necessary, the support of your hosting can help you.

    Alternatively, you could also enable debugging in WordPress. How to do this is described here: https://www.ads-software.com/support/article/debugging-in-wordpress/ – also here the support of your hosting can help you if necessary to edit the file accordingly.

    In both cases you should be able to see what the cause is in the logfile.

    Thread Starter JoyceD6

    (@joyced6)

    The debug.log says: PHP Fatal error: 

    Uncaught ArgumentCountError: Too few arguments to function WP_Widget:

    and then lists line errors.

    wp-includes/class-wp-widget-factory.php on line 62 and at least 2 expected in wp-includes/class-wp-widget.php:163

    Is this something the server should be expected to help with? Is this something I can fix in the code of the file?

    • This reply was modified 2 months, 1 week ago by JoyceD6.

    No, you should never customize files yourself. Not from the WordPress core (as in this case), not even from plugins and themes that you didn’t create.

    The reason for the message is probably the incorrect handling of a plugin or (more likely) your theme with the widget functions of WordPress. I see that you are using the “Weaver II” theme. This is extremely outdated, which is why I see this as the cause. It used to be in the www.ads-software.com repository, but was removed a long time ago. Only 8 year old reviews are still visible: https://www.ads-software.com/support/theme/weaver-ii/reviews/

    I would therefore recommend that you look for a new theme. First you can try out whether it is really the theme by activating a different theme. Since your content was written with a classic theme, I would recommend installing and activating the TwentyTwentyOne theme. This is the last classic standard theme. If you no longer have any error messages with it, you need to see whether you want to continue using the theme or look for a new theme.

    Thread Starter JoyceD6

    (@joyced6)

    I have the TwentyTwentyOne theme on the site, but how do I activate it when I can’t log in? I’m sure the site won’t look right and I’ll have to find something else probably, I can do that after I’m logged in. I’m currently using Webspace Explorer to edit the files.

    It should be sufficient to delete the Weaver II theme directory via FTP (make a backup beforehand). Then WordPress should automatically recognize and use the other theme. If not, you should at least be able to log in again in the backend.

    Thread Starter JoyceD6

    (@joyced6)

    I’m logged into it now, so hopefully I’ll be able to figure it out from here. Thank you!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.