Skip to main content
N
NikJohnson.art
Participant
November 7, 2018
Answered

Text presets not working in AE cc19

  • November 7, 2018
  • 7 replies
  • 10282 views

is anyone else having an issue using text presets bought on the internet? the ones I have worked perfect on cc18 but not in cc19. When I go to apply them in 19 I get message saying there is an "expression error"

"After effects warning : expression disabled

error at line 1 in property "amount of later 1 (friends) in comp 'silver and gold'

syntaxError: invalid or unexpected token

any one  any solutions or know what that means?

      This topic has been closed for replies.
      Correct answer Rick Gerard

      It is probably punctuation in the expressions. Extended Script was pretty forgiving. There is a possible solution. Try changing the expression engine in the Project Settings>Expressions tab from JavaScript to Legacy Extended Script. You can find Project Settings at the bottom of the File menu.

      7 replies

      E
      eternalm8397671
      Participant
      October 30, 2020

      awesome, the problem is same as me and now it fixed. Great support

      borysp37226394
      borysp37226394
      Participant
      May 3, 2020

      Thanks

      P
      Permeal
      Participant
      April 6, 2020

      Wow. Thank you so much sir.

      A
      awesome001x
      Participant
      September 13, 2019

      If you have not found help until now, maybe this would do,

      Go to File > Scripts |>

      Click on Update Legacy Expression.jsx

      A little dialog box should open,

      Simply click on Update

       

      Choose Yes to all warnings

      That's all, the expression errors should be corrected.

      Rameez_Khan
      Rameez_Khan
      Legend
      November 14, 2018

      +1 for Rick's suggestion.

      Read Tim Kurkoski's post here for more information: https://www.reddit.com/r/AfterEffects/comments/9uzu0z/tip_solution_to_3rd_party_script_expression/

      Thanks,

      Rameez

      R
      Community Expert
      Rick GerardCommunity ExpertCorrect answer
      Community Expert
      November 9, 2018

      It is probably punctuation in the expressions. Extended Script was pretty forgiving. There is a possible solution. Try changing the expression engine in the Project Settings>Expressions tab from JavaScript to Legacy Extended Script. You can find Project Settings at the bottom of the File menu.

        J
        Jeffrey_K_
        Participant
        July 16, 2019

        100% .... when copy and pasting code off the web the inverted comma's were switched to opening and closing ones, great for a word processor, not so good for the code engine. Thanks for pointing this out, perhaps Adobe could consider a parser for items pasted into code fields.

          P.M.B
          P.M.B
          Legend
          November 9, 2018

          Bumpin this

          ~Gutterfish
          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices