• Resolved j1mm1nycr1cket

    (@j1mm1nycr1cket)


    Hello,
    I’m using the premium plugin and the gsap__premium_only.js returns this error in the Chrome console:
    Invalid property image set to 0 Missing plugin? gsap.registerPlugin()
    gsap__premium_only.js?ver=3.6.0:10

    What does this mean and how do I fix it.?

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Scrollsequence

    (@scrollsequence)

    Hi,

    Could you please let me know the URL of your site so I can have a look?

    Thank you,

    Ales

    Thread Starter j1mm1nycr1cket

    (@j1mm1nycr1cket)

    I’m running it on my localhost at the moment. Do you want the full output of the error message.?

    Plugin Author Scrollsequence

    (@scrollsequence)

    Try disabling other plugins. I suspect a conflict between plugins.

    – Also what theme are you using?
    – Have you added images to each scene?
    – Are the images displayed?
    – Does the (content) animation play correctly?
    – Does the error occur on each Scrollsequence you create, or is it just isolated to a specific one?

    Thank you for information!

    Thread Starter j1mm1nycr1cket

    (@j1mm1nycr1cket)

    – I’m not using a commercial theme, I’m intentionally using a custom-made, blank theme, just enough to get WordPress running and displaying something. It’s as bare-bones as I can get it so that I can focus on the output of your plugin.
    – I’ve got one scene with images added, yes
    – Images are displayed properly
    – The animation runs fine
    – Same error occurs on every scrollsequence I make.

    !

    *edit: I say “error”, but it’s a warning, strictly speaking. I just don’t know why it occurs.

    Plugin Author Scrollsequence

    (@scrollsequence)

    Okay, I can see that warning now. It has no effect on the user or performance. This warning will be removed in the next version.

    If you want to get rid of it now, you can add following code at the end of line 674 in “ssq-lib__premium_only.js”

    ssqCur.image=0;

    Root cause was that a variable that was not set, but it should have been, to prevent the warning.

    I will close this as resolved because the warning does not cause any issues as far as I know and won’t be displayed in the next versions.

    For me the warning was not important, so I left it there, but ideally things like that should not happen. Thank you very much for pointing things out and helping us to make the code better!

    😎

    Ales

    Thread Starter j1mm1nycr1cket

    (@j1mm1nycr1cket)

    Ok, I’ll add that line – thanks for the prompt reply πŸ™‚

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

The topic ‘gsap invalid property error’ is closed to new replies.