Support Forum

I realize the notice is not harmful indication of the plugin. And the plugin will run perfectly with the notice. As you know, the notice is for the developer to check existence of that variable.

I could turn off the notices, by turning off the debug mode in wp-config.php file.

define('WP_DEBUG', false);

Or something like this could be applied in your user agent definitions PHP:

if(isset($_SERVER['HTTP_USER_AGENT'])) {
        //WordPress for iOS
        if ( stripos( $_SERVER['HTTP_USER_AGENT'], 'wp-iphone' ) !== false ) {
            return true;
        }
        //WordPress for Android
        elseif ( stripos( $_SERVER['HTTP_USER_AGENT'], 'wp-android' ) !== false ) {
            return true;
        }
        //WordPress for Windows Phone 7
        elseif ( stripos( $_SERVER['HTTP_USER_AGENT'], 'wp-windowsphone' ) !== false ) {
            return true;
        }
        //WordPress for Nokia
        elseif ( stripos( $_SERVER['HTTP_USER_AGENT'], 'wp-nokia' ) !== false ) {
            return true;
        }
        //WordPress for Blackberry
        elseif ( stripos( $_SERVER['HTTP_USER_AGENT'], 'wp-blackberry' ) !== false ) {
            return true;
        }
    }

Jetpack provides the whole list: https://github.com/xwp/wp-jetpack/blob/master/class.jetpack-user-agent.php

Yeah.. well, that's beyond me I suppose I need to disable the debug mode then?

"confusing too what kind of browser you would be running that does not identify itself…"

The error log is on the server, not my computer. The errors are related to any number of browsers accessing the blog, not only one. Therefore my IE11 browser is not the issue. Is it is identifying 1000's of users, resulting in the error.

The only report is the same line repeated 1,000's of times:

Undefined index: HTTP_USER_AGENT in /problem-with-post-edit-buttonome/account/public_html/wp-content/plugins/simple-press/sp-api/sp-api-device.php on line 36

Since there is no way to perfectly identify the unknown anomaly, the next option would to make sure the HTTP exceptions listed all the primary browser types. Thus my suggesting looking at the github link, reviewing Jetpacks itemization compared to your own.

I looked at your predefined, $ua = $_SERVER['HTTP_USER_AGENT'] and noted a comprehensive list via Categorizr Version 1.1 which is two years out of date, and missing some of the prominent devices like Nokia.

What about appending a dumb_agents array?

var $dumb_agents = array(

  'nokia', 'blackberry', 'philips', 'samsung', 'sanyo', 'sony', 'panasonic', 'webos',

  'ericsson', 'alcatel', 'palm',

  'windows ce', 'opera mini', 'series60', 'series40',

  'au-mic,', 'audiovox', 'avantgo', 'blazer',

  'danger', 'docomo', 'epoc',

  'ericy', 'i-mode', 'ipaq',  'midp-',

  'mot-', 'netfront', 'nitro',

  'palmsource',  'pocketpc', 'portalmmm',

  'rover', 'sie-',

  'symbian', 'cldc-', 'j2me',

  'smartphone', 'up.browser', 'up.link',

   'up.link', 'vodafone/', 'wap1.', 'wap2.', 'mobile', 'googlebot-mobile',

 );

Whatever the case, the possibilities can be comprehensive, therefore I understand why a developer cannot include every possible device or agent.