[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4781: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3916)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4783: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3916)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4784: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3916)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4785: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3916)
Chuck Baker's Firefox Extension Forum • View topic - FECT apparently random behaviours with one profile
Page 2 of 2

FECT fix, and compatibility with e10s

PostPosted: Sun Jul 29, 2018 10:32 pm
by grahamperrin
Hi, a gentle nudge, are you any closer to a fix for ' in names of extensions?

Also re: https://addons.mozilla.org/compatibilit ... arebychuck is it recommended to have multi-process disabled whilst using the extension to troubleshoot conflicts? I ask because recent versions of Waterfox do not disable e10s when an incompatible extension is enabled.

Re: FECT apparently random behaviours with one profile

PostPosted: Mon Jul 30, 2018 5:42 pm
by cbaker_admin
I've never tried to make any of my extensions with e10s because shortly after Mozilla required it, they announce the 'Legacy' extension debacle so it seemed pointless to address it.

I have, however, updated FECT to v10.1 to address the single quote issue. It should work with Pale Moon, Waterfox and Firefox Developer Edition (FECT 10.1 is not signed, so it will not install in current Fx versions.)

Please give it a try to see if it works for you.

(Attachment removed)

FECT targeting an extension with ' in its name

PostPosted: Mon Jul 30, 2018 8:27 pm
by grahamperrin
Thanks!

First test run: not intended to be comprehensive, I ended it after one or two iterations. The automated restart had the required number of extensions enabled. A crash occurred, around the time of the restart, whilst I was out of the room, but I'm inclined to treat that as a one-off (not an issue with FECT).

Subsequent test run: I made an extension with ' in its name the target of the troubleshooting routine. With that particular extension targeted, the Continue button seemed to have no effect … later, other peculiarities (e.g. after a reset of the database, the main FECT menu continued to show the option to end a session, and so on) that were worked around only by a manual quit of the browser (Waterfox).

Re: FECT apparently random behaviours with one profile

PostPosted: Tue Jul 31, 2018 3:06 pm
by cbaker_admin
Ok ... I've fixed the issue with the target extension having single quotes in the name. Please see if this works for you.

FECT10.1.xpi
Extension Conflict Troubleshooter (unsigned)
(110.46 KiB) Downloaded 441 times

FECT 10.1 OK

PostPosted: Wed Aug 01, 2018 5:08 am
by grahamperrin
Thanks!

10.1 tested OK for me (139 extensions enabled, 337 disabled before the test session began).

Re: FECT apparently random behaviours with one profile

PostPosted: Wed Aug 01, 2018 4:59 pm
by cbaker_admin
Great! Thanks for testing. I've uploaded this version to the and am in the process of posting it to the .