When I update Plugin to Latest 2.0.30 , History page is not loading

  • Resolved shanrocks666

    (@shanrocks666)


    4 years ago

    Getting Below error after updating to latest version 2.0.30

    Also please use tags , so that if any issue appears we can rollback to older version

    TypeError: (0 , Object(...)(...).isVisible) is not a function
    at b (npm-topefekt.3db1ae111ba1f3008563.bundle.js:1)
    at eo (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at Wi (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at Eu (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at ku (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at wu (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at du (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at iu (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at $u (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17
ai @ npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17
npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17 Uncaught TypeError: (0 , Object(...)(...).isVisible) is not a function
    at b (npm-topefekt.3db1ae111ba1f3008563.bundle.js:1)
    at eo (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at Wi (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at Eu (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at ku (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at wu (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at du (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at iu (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at $u (npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17)
    at npm-react-dom.7f54aef76d1dd14569fb.bundle.js:17
Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Author BulkGate

    (@woosms)

    We are aware of this problem. We apologize for all the inconvenience. We’re working hard to fix the issue asap.

    Plugin Author BulkGate

    (@woosms)

    @shanrocks666 Could you please tell us which browser and what version do you use?

    Thank you!

    Thread Starter shanrocks666

    (@shanrocks666)

    Hi

    I use Google Chrome version 88.0.4324.182 (Official Build) (64-bit)

    Thanks

    Plugin Author BulkGate

    (@woosms)

    If you try to open page from another browser the problem still remains?

    pluggedinelectricians

    (@pluggedinelectricians)

    Hi,
    The same problem has occurred for me. UI is not loading in Chrome, but is loading in MSedge.

    Also, there is a layout conflict: the woocommerce orders page is kicked out of alignment on mobile devices with names and links crashing into each other (also on some other pages – plugins etc). this problem rectifies upon deactivation of woosms.

    Please could you provide a rollback option? We use the Woosms all day and is too good to deactivate completely ??

    thanks
    C

    Plugin Author BulkGate

    (@woosms)

    @pluggedinelectricians We’re sorry for the inconvenience it has caused you. However, now it should be fixed. Please, let us know, so I can close the issue.

    @shanrocks666 The same for you.

    Thank you

    pluggedinelectricians

    (@pluggedinelectricians)

    thank you for your reply.

    The update hasn’t pushed out to me yet. Is there meant to be an update?

    Plugin Author BulkGate

    (@woosms)

    Hi @pluggedinelectricians,

    Could you please send here the application id? We’ll check it out and fix it for you.

    Thread Starter shanrocks666

    (@shanrocks666)

    Same for me also , not working still.

    Plugin Author BulkGate

    (@woosms)

    @shanrocks666 Give us your application id too.

    The application ID can be found in the menu in the last item “About module”

    Thread Starter shanrocks666

    (@shanrocks666)

    Here is my Application ID: 15275

    Plugin Author BulkGate

    (@woosms)

    @shanrocks666 Try to open it in Chrome now.

    Thread Starter shanrocks666

    (@shanrocks666)

    yes in cognito mode it is working. It looks i have clear cache Thank

    Plugin Author BulkGate

    (@woosms)

    Perfect. Once again, we’re sorry for the inconvenience

    pluggedinelectricians

    (@pluggedinelectricians)

    Cleared cache and it works now. Thanks for all the help. Great job.

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘When I update Plugin to Latest 2.0.30 , History page is not loading’ is closed to new replies.