Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author erolsk8

    (@erolsk8)

    Hi @igestalten, did you try turning on debugging in Settings -> Media Sync?

    I’m not sure what’s the actual problem.

    Thread Starter igestalten

    (@igestalten)

    Debug after Scan:

    Debugging before uploads directory scan:
    Peak memory usage: 18 MB / 18432 KB
    Memory usage: 15 MB / 15498 KB (3% of the available memory: 512 MB / 524288 KB)
    Time since start: 0.031409025192261 seconds

    Debugging after uploads directory scan:
    Peak memory usage: 18 MB / 18432 KB
    Memory usage: 15 MB / 15499 KB (3% of the available memory: 512 MB / 524288 KB)
    Time since start: 0.031425952911377 seconds

    Debugging after table render:
    Peak memory usage: 18 MB / 18432 KB
    Memory usage: 15 MB / 15509 KB (3% of the available memory: 512 MB / 524288 KB)
    Time since start: 1.0372700691223 seconds

    Error es described appears after trying to import any folder (also on dry run).
    Tested in different Browsers (FF,Chrome,Egde), WP 5.5.1, PHP 7.3

    Error disappears when reverting to 1.2.0

    Plugin Author erolsk8

    (@erolsk8)

    Thank you, but don’t you maybe get more detailed error message while trying to import?
    Because just “500 (Internal Server Error)” is a generic error message which doesn’t tell much.

    I’m sorry it stoped working for you, but looks like 1.2.2 solved issues for some people, but created new issues for others.

    So I’ll see if I can combine something blindly (since I can’t replicate in on my end), and I’ll update this topic.

    Plugin Author erolsk8

    (@erolsk8)

    Hi @igestalten, I just pushed version 1.2.3 which might solve your problem, or at least show us a more useful error message so I can fix it.

    Please let me know if you get to try it out.

    Thanks
    Erol

    Thread Starter igestalten

    (@igestalten)

    1.2.3 fixed it for me!
    Thanks a lot

    Plugin Author erolsk8

    (@erolsk8)

    Nice! I’m glad it worked.

    Thanks for letting me know.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Import error in 1.2.2’ is closed to new replies.