Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

Learn More

On OS X, from the terminal, how do i set allow and remember flash for specific sites.

  • 1 답장
  • 2 이 문제를 만남
  • 4 보기
  • 최종 답변자: cor-el

more options

After I mass update my computer labs, the allow and remember settings get reset for websites which I need flash to run. (about 40 computers per lab). I'm updating flash and firefox using Apple Remote Desktop.

What terminal command, or configuration file can I push out on El Cap to keep this setting?

After I mass update my computer labs, the allow and remember settings get reset for websites which I need flash to run. (about 40 computers per lab). I'm updating flash and firefox using Apple Remote Desktop. What terminal command, or configuration file can I push out on El Cap to keep this setting?

모든 댓글 (1)

more options

That is not possible AFAIK.

Such site specific settings are stored in the permissions.sqlite database. You can check this database with an SQL viewing application to see how this works because current Firefox releases no longer support Legacy extensions like SQLite Manager to inspect SQLite database files.

Easiest would be to set Flash to always activate (plugin.state.flash = 2) via the mozilla.cfg file via pref() or lockPref().

//
pref("plugin.state.flash", 2);

You can use the mozilla.cfg file in the Firefox program folder to set or lock preferences and run privileged JavaScript code.

The mozilla.cfg file needs to be in the main Firefox program folder.

These functions can be used in the mozilla.cfg file:

defaultPref();	// set new default value
pref();	// set pref, allow changes in current session
lockPref();	// lock pref, disallow changes

This requires a local-settings.js file in the "defaults/pref" folder where the channel-prefs.js file is located that specifies to use mozilla.cfg.

//
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);

The mozilla.cfg and local-settings.js files need to start with a comment line (//).

See Configuration:

See also: