Support » Plugin: SG Optimizer » Issue with 5.0.13

  • Resolved lauradiaz

    (@lauradiaz)


    Hello!

    I am detecting errors in the developer console since I upgraded from 5.0.12 to 5.0.13.

    The backend has become unusable because when trying to select a configuration I get a red box with a cross in the upper left and the following error appears in the console every time I click on a configuration.

    POST https://www.mydomain.com/wp-json/siteground-optimizer/v1/enable-option 401 ()
    (anonymous) @ mainApi.js:18
    (anonymous) @ proc.js:507
    N @ proc.js:518
    B @ proc.js:316
    e @ proc.js:255
    X @ proc.js:551
    N @ proc.js:540
    B @ proc.js:316
    g @ proc.js:387
    a @ proc.js:467
    put @ channel.js:85
    (anonymous) @ channel.js:173
    (anonymous) @ channel.js:198
    a @ scheduler.js:5
    c @ scheduler.js:62
    t.asap @ scheduler.js:3
    (anonymous) @ channel.js:197
    emit @ channel.js:38
    (anonymous) @ middleware.js:73
    enableOption @ index.jsx:75
    n.changeOption @ index.jsx:38
    onChange @ index.jsx:200
    (anonymous) @ react-dom.production.min.js:14
    d @ react-dom.production.min.js:15
    (anonymous) @ react-dom.production.min.js:15
    v @ react-dom.production.min.js:17
    w @ react-dom.production.min.js:18
    R @ react-dom.production.min.js:18
    W @ react-dom.production.min.js:18
    T @ react-dom.production.min.js:21
    qn @ react-dom.production.min.js:84
    fi @ react-dom.production.min.js:216
    Pe @ react-dom.production.min.js:39
    wn @ react-dom.production.min.js:86
    zi @ react-dom.production.min.js:216
    xn @ react-dom.production.min.js:85
    mainApi.js:27 Response {type: "basic", url: "https://www.mydomain.com/wp-json/siteground-optimizer/v1/enable-option", redirected: false, status: 401, ok: false, …}

    I have tried with different versions of PHP and in several webs and those errors keep appearing, not being able to use the plugin and also slowing down the load times of the web.

    Why can this be happening? When doing a backward movement to 5.0.12 everything works fine.

    Thank you!

Viewing 5 replies - 1 through 5 (of 5 total)
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Issue with 5.0.13’ is closed to new replies.