Filebot Node - Safari on macOS Mojave

[hot22shot]

Hello,

I'm using filebot (4.8.2) and Filebot Node (0.2.8.2) on my Synology DS916 with Safari as a browser on my macbook, I have a problem with Filebot Node :


I can't do anything and must use another browser like FF.

Is there anyone with the same problem ?

Regards

[rednoah]

What exactly seems to be the problem here? You can try to open the IFRAME directly in a new tab. That might help Safari to render correctly.

The Output Folder from field (highlighted in red) must be filled out with a valid output folder path. The Execute button is enabled / disabled depending on whether or not the form is filled out correctly or not.

[hot22shot]

Another side by side pic with Safari and Firefox :


On the foreground Firefox displays File Filter, Custom Format, etc.
On the background the same page opened in Safari : it does not display the text and buttons.

Same behavior with an iframe on a new tab.

Regards

[rednoah]

I see. No idea. Maybe ExtJS framework is just broken on Safari. Unfortunately, not something that can be fixed easily. Just use Firefox or Chrome in the meanwhile.

[hot22shot]

OK, thanks I installed the full Filebot client for macOS.

[hot22shot]

Hi, just tested with Filebot Node version 0.2.9 on Catalina and it now works (don't know at which point in time it was resolved though !).

Thanks rednoah.

[Vaxter]

Will FileBot Node 0.2.9 be available on QNAP repo soon, or should I update manually?

[rednoah]

Soon-ish. I recommend updating manually though. Just takes a minute.

[Vaxter]

Manual update it was.
Works perfectly!

[Vaxter]

Actually, it doesn’t work perfectly...
Update has fixed UI issues, but now, whatever I try to do, I get errors that something is not a valid option.
This is on QNAP,
Would you need some logs and maybe I should open another thread, since this is a different issue?

[rednoah]

Depending on what the error message says, it could indicate that you might need the latest FileBot beta as well.

[Vaxter]

—apply is not a valid option is the most often one.

[rednoah]

I see. Yes, the latest FileBot beta package should work then.

[Vaxter]

Already tried when you first insinuated.
[~] # filebot --version
Unrecognized option: --illegal-access=permit
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
[~] #

[rednoah]

This error message means you're using some outded default Synology Java 8.

FileBot generally assumes that you have installed Java via our package from our repository, which will give you Java 13 at the time of writing.

[Vaxter]

I am on qNap and I did install with your package.
4.8.5 worked fine, and then I updated to 4.9.0 beta.
I’ll check it out, maybe I do have an older version.

[rednoah]

You'll need to latest Java installed via our community repository:
viewtopic.php?f=13&t=1802

The official Synology repository also has a Java package, but it's plagued by many issues and very outdated. So we've made our own to work around that.