FS Poster, generates error when accessing the Logs page

  • Resolved Radovan

    (@radovand)


    1 month ago

    FS Poster, paid version, generates error when accessing the Logs page.

    Error in debug.log:
    PHP Warning: Undefined array array key “username” in …. /wp-content/plugins/fs-poster/App/Pages/Logs/Logs/Controllers/Ajax.php on line 299

    Error in Query -> Browser Console:

    PHP Errors in Ajax Response
    query-monitor.js?ver=3.16.4:400
    Object component:
    “Plugin: fs-poster”
    file: “wp-content/plugins/fs-poster/App/Pages/Logs/Controllers/Ajax.php”
    key: “baa70694332630179dc507e26a24b167”
    line: 299
    message: “Undefined array array key \”username\””
    stack: (3) [ ‘FSPoster->report3_data()’, ‘FSPoster->report3_data()’, ‘do_action(‘wp_ajax_report3_data’)’]
    type: “warning”

    Note that, I tried:

    • installing the plugin from scratch;
    • setting accounts from scratch;
    • importing the accounts;
    • using different “Item Purchase Code” (I have 6 purchased licenses);
    • etc.
      Nothing eliminp the error.


Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Radovan

    (@radovand)

    Full error log.

    load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:5 JQMIGRATE: Migrate is installed, version 3.4.1
    query-monitor.js?ver=3.16.4:390 PHP Errors in Ajax Response
    query-monitor.js?ver=3.16.4:400 {key: ‘baa70694332630179dc507e26a24b167’, type: ‘warning’, message: ‘Undefined array key “username”‘, file: ‘wp-content/plugins/fs-poster/App/Pages/Logs/Controllers/Ajax.php’, line: 299,?…}
    (anonymous) @ query-monitor.js?ver=3.16.4:400
    dispatch @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    v.handle @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    trigger @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    l @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    (anonymous) @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    load
    send @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    ajax @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    (anonymous) @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:5
    e. @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:5
    ajax @ fsp.js?version=6.6.5:449
    FSPLoadLogs @ fsp-logs.js?version=6.6.5:196
    (anonymous) @ fsp-logs.js?version=6.6.5:167
    e @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    t @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    setTimeout
    (anonymous) @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    c @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    add @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    (anonymous) @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    (anonymous) @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:5
    e. @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:5
    then @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    ce.fn.ready @ load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.2:2
    (anonymous) @ fsp-logs.js?version=6.6.5:6
    (anonymous) @ fsp-logs.js?version=6.6.5:180

    Thread Starter Radovan

    (@radovand)

    BUG REPORT – FS POSTER

    Issue: PHP Warning in Logs section – “Undefined array key username”
    File: App/Pages/Logs/Controllers/Ajax.php:299

    Current behavior:

    • Direct access to $node[‘username’] without verification
    • Error occurs after adding multiple accounts
    • Clearing logs temporarily fixes the issue

    Root cause:

    • In report3_data() function, $node[‘username’] is accessed directly
    • Some social networks don’t provide username field
    • No fallback for missing username values

    Impact:

    • Logs section becomes unusable
    • Post operations continue to work
    • Error reappears after new posts

    Steps to reproduce:

    1. Add multiple social accounts (FB, LinkedIn)
    2. Make successful posts
    3. Try to view logs
    4. Clear logs – error disappears
    5. Make new posts – error returns

    Environment:

    • WordPress 6.x
    • PHP 8.3
    • Latest FS Poster version
    Plugin Author FS Code

    (@fscode)

    Hi there!

    To get support for the Paid version, please create a ticket at https://support.fs-code.com.? Our support team will help you as soon as possible.

    Also, you can create a free support ticket on FS Poster’s Discord server for support and guidance from our dedicated team and community: https://www.fs-poster.com/discord-community

    Best Regards,

    FS Poster Team

    • This reply was modified 1 month ago by FS Code.
    Thread Starter Radovan

    (@radovand)

    My support for the paid version has expired. So it doesn’t help if I open a new ticket on https://support.fs-code.com.

    I have informed you that the plugin has this problem in the hope that you will fix it.

    And one more thing, I’m constantly getting warnings from regarding Solid Security, related to:

    Known Vulnerabilities

    WordPress FS FS Poster plugin <= 6.5.8 – Cross Site Request Forgery (CSRF) vulnerability

    Plugin Author FS Code

    (@fscode)

    The vulnerability has been fixed in version 6.0.0

    You can create a free support ticket in Discord as well.

    Best Regards,

    FS Poster Team

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.