• Resolved Roger Correia

    (@correiar)


    Hi Frank,

    You posted a comment to my issue under Fileaway, when I experienced a conflict with Autoptimize. Disabling JS optimization got rid of the conflict.

    You suggested putting in an EXCLUSION.

    I specified the following exclusion as a new comma delimited item:
    “plugins/autoptimize”

    It had no effect on the issue. The only way to make the issue in Fileaway go away is disable JS optimization.

    What am I missing?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Frank Goossens

    (@futtta)

    well, you’d have to exclude the fileaway JS, so the exclusion would rather be something like plugins/fileway.

    Thread Starter Roger Correia

    (@correiar)

    Sorry, that’s what I meant… was thinking FileAway but typing Autoptimize.

    I had used the exclusion /plugins/fileaway but when I looked closer at the directory on the server, I should have really typed /plugins/file-away.

    Once I fixed the typo, it worked fine. Wasn’t able to get the GTMetrix report back to 88% from 82%, but it now sits at 85%.

    Thanks for your prompt response and making me stop and think!

    Plugin Author Frank Goossens

    (@futtta)

    you’re welcome @correiar 🙂

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Fileaway & Autoptimize conflict’ is closed to new replies.