• Resolved jturet

    (@jturet)


    This plugin just recently began causing the following output in my error logs. I believe it may be a compatibility issue with another plugin. Thoughts? I’ll keep you updated as I test more.

    (
        [action] =>
        [base] => plugins
        [columns:WP_Screen:private] => 0
        [id] => plugins
        [in_admin:protected] => site
        [is_network] =>
        [is_user] =>
        [parent_base] => plugins
        [parent_file] => plugins.php
        [post_type] =>
        [taxonomy] =>
        [_help_tabs:WP_Screen:private] => Array
            (
                [overview] => Array
                    (
                        [title] => Overview
                        [id] => overview
                        [content] => <p>Plugins extend and expand the functionality of WordPress. Once a plugin is installed, you may activate it or deactivate it here.</p><p>You can find additional plugins for your site by using the <a href="plugin-install.php">Plugin Browser/Installer</a> functionality or by browsing the <a href="https://www.ads-software.com/plugins/" target="_blank">WordPress Plugin Directory</a> directly and installing new plugins manually. To manually install a plugin you generally just need to upload the plugin file into your <code>/wp-content/plugins</code> directory. Once a plugin has been installed, you can activate it here.</p>
                        [callback] =>
                    )
    
                [compatibility-problems] => Array
                    (
                        [title] => Troubleshooting
                        [id] => compatibility-problems
                        [content] => <p>Most of the time, plugins play nicely with the core of WordPress and with other plugins. Sometimes, though, a plugin’s code will get in the way of another plugin, causing compatibility issues. If your site starts doing strange things, this may be the problem. Try deactivating all your plugins and re-activating them in various combinations until you isolate which one(s) caused the issue.</p><p>If something goes wrong with a plugin and you can’t use WordPress, delete or rename that file in the <code>/srv/users/serverpilot/apps/mainsite/public/wp-content/plugins</code> directory and it will be automatically deactivated.</p>
                        [callback] =>
                    )
    
            )
    
        [_help_sidebar:WP_Screen:private] => <p><strong>For more information:</strong></p><p><a href="https://codex.www.ads-software.com/Managing_Plugins#Plugin_Management" target="_blank">Documentation on Managing Plugins</a></p><p><a href="https://www.ads-software.com/support/" target="_blank">Support Forums</a></p>
        [_options:WP_Screen:private] => Array
            (
                [per_page] => Array
                    (
                        [label] => Plugins
                        [default] => 999
                    )
    
            )
    
        [_show_screen_options:WP_Screen:private] => 1
        [_screen_settings:WP_Screen:private] =>
    )

    https://www.ads-software.com/plugins/wpgform/

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

    (@jturet)

    Does not look like a plugin incompatibility, the problem persisted with all other plugins deactivated. The issue seems to be that the plugin causes “WP_Screen Object” to print to error logs from admin pages.

    Plugin Author Mike Walsh

    (@mpwalsh8)

    This is a leftover from some debug code which I had output being sent to the PHP Error Log. While it shouldn’t technically be there, it doesn’t adversely affect the plugin functionality.

    I have updated the plugin and removed the debug code.

    Thread Starter jturet

    (@jturet)

    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Apache Error Log Output’ is closed to new replies.