Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter sogy91

    (@sogy91)

    Hello back all, have a nice time
    All the items mentioned above were completely corrected and the problem was solved, but only the following error is shown at the top of the page:
    Notice
    : Function add_theme_support( ‘html5’ ) was called
    incorrectly
    . You must pass an array of view types. For more information, please
    Debugging in WordPress
    see that. (This message was added in version 3.6.1.) in
    /home/journal9/domains/journalofcoms.com/public_html/wp-includes/functions.php
    online
    5833

    How can I fix these problems?
    Thank you very much

    Thread Starter sogy91

    (@sogy91)

    Hello buddies
    Thank you for your reply and help
    I updated WordPress manually and kept the previous wp-content folder and wp-config.php file for theme and plugins and upload files.
    After the update, it shows the following error on the main page of the site and WordPress dashboard:
    : Function add_theme_support( ‘html5’ ) was called
    incorrectly
    . You must pass an array of view types. For more information, please
    Debugging in WordPress
    see that. (This message was added in version 3.6.1.) in
    /home/journal9/domains/journalofcoms.com/public_html/wp-includes/functions.php
    online
    5833

    The site template is also displayed in a mess and the plugins are not displayed in the dashboard.

    On the other hand, other pages of the site also give the following error:
    Not found
    The requested URL was not found on this server.
    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

    How can I fix these problems?
    Thank you very much

    Thread Starter sogy91

    (@sogy91)

    Thanks for your response.
    When PHP is 7.4 or 8 displays the above error.

    Also, PHP 8.1, shows the following error:
    “Service Unavailable
    The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.”

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