Category: WordPress Troubleshooting

  • SFTP FileZilla “No Supported Authentication Methods”

    SFTP is a secure file transfer method, that is supported by FileZilla and many other FTP programs.

    When your ISP changes your IP address, and you try to connect the way that used to work, you get this in the FileZilla command section:

    Status: Connecting to yourserver.com:18765...
    Response: fzSftp started
    Command: keyfile "F:\path\to\keyfile.ppk"
    Command: open "username@servername.com" 18765
    Error: Disconnected: No supported authentication methods available (server sent: publickey)

    (more…)

  • BackWPup – Trying to get property of non-object

    BackWPup version 3.1.2 – error message with Debugging mode on “Trying to get property of non-object”

    in class-job.php
    in public static function get_jobrun_url( $starttype, $jobid = 0 )

    Change

    $wp_admin_user = get_users( array( ‘role’ => ‘administrator’, ‘number’ => 1 ) ); //get a user for cookie auth

    to

    $wp_admin_user = get_users( array( ‘role’ => ‘backwpup_admin’, ‘number’ => 1) ); //get a user for cookie auth

    (probably better to test for either? On my system, only one Administrator, but the role is set to backwpup_admin, there are None with ‘administrator’)

    BackWPup uses (or at some earlier time used?) a different Role for the backup administrator, ‘backwpup_admin’ instead of the default Role ‘administrator’.

    This is on BackWPup version 3.1.2 on WordPress 3.9.2

  • Debugging WordPress Problems (for Only You)

    How do you figure out what is wrong in WordPress?

    WordPress has some good diagnosing and troubleshooting information available to you, but the default is it is turned off. (For good reasons, including it is visually very distracting on screen, and it has candy for hackers.)

    Most of what you might see are PHP errors, PHP warnings, MySQL errors. If you don’t understand what they mean, even emailing the messages to the plugin author or your technical support person can be extremely helpful.

    Normally you can turn debugging on or turn it off, in your wp-config.php file.

    I have a page that shows you exactly how to turn on WordPress Debugging for Only you, and only when you want it. Work normally most of the time, and when something is not working you can see what error messages you are getting.

    Without debugging, you might get a message like this:
    Download failed. Destination directory for file streaming does not exist or is not writable.

    This specific message I got trying to update a plugin. Okay, which directory is the problem?

    Turn on debugging, and you get this instead:
    Warning: touch() [function.touch]: Unable to create file /home/USERNAME/public_html/wp-content/temp/plugin-name.tmp because No such file or directory in /home/USERNAME/public_html/wp-admin/includes/file.php on line 155
    Warning: unlink(/home/USERNAME/public_html/wp-content/temp/plugin-name.tmp) [function.unlink]: No such file or directory in /home/USERNAME/public_html/wp-admin/includes/file.php on line 500
    Download failed. Destination directory for file streaming does not exist or is not writable.

    Ah, something with /wp-content/temp/.

    And if you notice it affects all plugin updates, you might search for

    wordpress "Download failed. Destination directory for file streaming does not exist or is not writable." and the first page when I searched, gives the correct answer. In this case, it’s add to your wp-config.php this: /* Setup a temporary folder for uploading and updating */
    define( 'WP_TEMP_DIR', ABSPATH . 'wp-content/temp/') ;

    and of course create that folder on your server.

    If it only affected a single plugin, search that plugin’s support board. (I obviously changed the actual plugin file name to ‘plugin-name’, since the plugin wasn’t the problem. Normally you get the folder name of the plugin as part of the error message.)

  • Tracking Down Deprecated Functions

    You may be seeing warnings like this if you have WordPress Debug mode enabled:

    “Notice: wpdb::escape is deprecated since version 3.6! Use wpdb::prepare() or esc_sql() instead. in /home/USERNAME/public_html/wp-includes/functions.php on line 2913”

    I am getting this with WordPress version 3.8.1, and the Domain Mapping plugin wordpress-mu-domain-mapping version 0.5.4.3 but “deprecated” messages happen with many, many plugins.

    The wp-includes/functions.php is a WordPress core file. The function at the line mentioned is reporting the error, not the line with the error. To fix the error, you need to know where the error originates. I’m going to show you how to find that. (more…)

  • WordPress 3 (or 4) Multi-Site Installation, on Shared Hosting, Even with Existing Web Sites

    WordPress 3 (or 4) Multi-Site Installation, on Shared Hosting, Even with Existing Web Sites

    Here’s how to Install WordPress 3 with the New Multi-Site Capabilities — Even if you Already Have a Website in your Hosting Account. [Updated, works on WordPress 4 through at least WP 4.5)

    WordPress multi-site features let you very easily create blogs (now officially called “sites”).

    You can now have multiple blogs in WordPress with much less administration of WordPress updates, plug-in updates and settings, theme updates, etc. Multiple blogs, for each domain you are hosting, can be managed by a single installation of WordPress. (more…)