Robert Calhoun

Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Forum: Fixing WordPress
    In reply to: Website ok, Backend toast
    Thread Starter Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    No body interested in helping me with this issue?

    Forum: Fixing WordPress
    In reply to: Website ok, Backend toast
    Thread Starter Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    I tried to temporarily change permissions on the wp-admin folder and that 404’d the entire site. I was able to 766 the images folder and try to run the update again.

    Ok, so if I have the images/ folder as 755 (rwx-rx-rx) it fails to install the about-texture.png, now if I change that to 766, it will say it fails to install stars.png.

    Also I changed my theme to the default 2021 theme and it changed the website without issue and that works fine. Back end still snafu’d and update still fails exactly the same.

    Here is a link to what the back end currently looks like:
    back end snafu

    Forum: Fixing WordPress
    In reply to: Up and Running, How to Verify Everything is good to go?
    Thread Starter Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    Thank you Corrina and Steve,

    I did in fact delete all 3 extra themes only for WP to tell me to have a default theme as a backup in case the installed theme blows up, lol

    I am excited, it was alot of work and long hours to get the site up and working correctly. All via SSH and command line interface, it was such a joy to be able to log into the admin page, yay a gui interface! My user name is indicative of the install process..lol

    Robert

    Forum: Fixing WordPress
    In reply to: Critical error on my site
    Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    To the original poster, locate your wp-config.php file in your wordpress root directory, open in a text editor like notepad and find the line that says DEBUG=false, change that to true. Refresh your webpage and you will get a read out of errors that it is encountering. A critical error could be anything, but it most likely comes from the 8.1 error in the way it connects to mysql. I posted a link to a fix for that with example code. Then after that you will probably get another error telling you that there are no tables present in the database, you will need to pass the flag mysql_native_password in MySQL. The latest versions of both PHP8.1 and MySQL8 made code change that seems to conflict with latest version WordPress. Again these are just simple one line modifications that is part of any server administration.

    I have heard several times that the latest version of WP is not compatible with php8.1. I am running it without errors, although I will admit there was the one modification that had to be addressed. This was a change in reporting with mysql database, a single line of code fixed the problem. So its not even that PHP is compatible with wordpress, its simply the way it interacts with Mysql.

    Forum: Fixing WordPress
    In reply to: webite domain correction
    Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    This situation would have been clearly explained under installation instructions. Since this is such a basic error it might be worth reviewing the basic install documentation again before proceeding further.

    Review the following article that may help resolve your situation.

    Moving WordPress

    Perhaps someone more experienced will have a better solution.

    Forum: Fixing WordPress
    In reply to: ImageMagick restricting upload size
    Thread Starter Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    Doh, I got it. I was restarting the nginx server thinking it would refresh the php.ini file. Good Times! 🙂

    sudo systemctl restart php8.1-php

    
File uploads	Enabled
Max size of post data allowed	25M
Max size of an uploaded file	25M
Max effective file size	25 MB
Max number of files allowed	20

    As a note I reduced the size of file uploads to 25mb and can go bigger as needed. My thought being it could limit potential abuse if hacked. Either way I am trying to keep things tight and tidy on my first outing.

    Thanks,
    Robert

    Forum: Fixing WordPress
    In reply to: Found a strange file in WordPress root
    Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    I think the bigger question is how did someone gain access to the root folder of your installation? I think that is where you need to start working from.

    Can you post a text copy of the php script you copied so it can be analyzed?

    Are you really looking for help?

    Also your link to the example.com site in itself is risky at best.

    `URL Scanning Details for https://www.example.com/wp-code.php

    Suspicious
    Indicates reputation issues and potentially malicious activity. Suspicious Activity
    Domain
    Domain name of the final URL after all redirections. example.com
    IP Address
    The corresponding IP address for the URL’s web server. 93.184.216.34

    Risk Score
    Overall threat score from 0 (clean) to 100 (high risk). 78 – Risky

    Spamming Domain
    Is this domain recently sending SPAM? Recent SPAM

    Forum: Fixing WordPress
    In reply to: PHP 8.1
    Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    Also as a future note on a very similar subject, I also use MySQL 8 and I ran into a problem with errors in that there where no tables created in the database.

    Again simple fix after hours of hairpulling, (hence my username)this is due to again changes in the core code of mysql 8.

    When creating the database user you must use the flag ‘mysql_native_password’ when creating the wp_db user. If not wordpress will not be able to authenticate and will not be able to create tables on the database.

    No explicit errors to tell you this, you just end up falling down the rabbit hole chasing leads until viola, you nail it!

    Forum: Fixing WordPress
    In reply to: PHP 8.1
    Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    https://core.trac.wordpress.org/ticket/52825
    https://php.watch/versions/8.1/mysqli-error-mode

    File to Modify:
    wp-includes/wp-db.php

    // Set the MySQLi error reporting off because WordPress handles
    // its own. This is due to default value change in PHP 8.1.
    mysqli_report( MYSQLI_REPORT_OFF );

    Direct from my config file:

    1631             /*
1632              * Set the MySQLi error reporting off becuase WordPress handles its own.
1633              * This is due to the defualt value change from 'MYSQLI_REPORT_OFF'
1634              * to 'MYSQLI_REPORT_ERROR|MYSQLI_REPORT_STRICT' in PHP 8.1
1635              */
1636             mysqli_report( MYSQLI_REPORT_OFF );
    Forum: Fixing WordPress
    In reply to: PHP 8.1
    Robert Calhoun

    (@hairpuller)

    4 years, 2 months ago

    I just got done rolling my own wp server from scratch and had to battle with php8.1, It was a battle for sure tracking down all my issues on a brand new install from scratch via ssh and command line only.

    Anyways the issues stems from a change in error reporting. It uses a new strict error reporting format. You can change the line of code to force it to prior version format. I think it had to do with mysql connection as from my understanding wp now handles that. It was 6 hours yesterday and 2 more this morning so I am a little fuzzy.

    It comes done to one simple line of code I think on line 1635. It is in a wp changelog and also on the php documentation site.

    I am trying to find the issue, but if you turn on debugging in the your wp-config.php file it will give you some information. I will respond back when I find the 411.

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