Uncaught TypeError: Cannot read property 'tram' of undefined
I used webflow. Now there is a conflict when loading webflow.js.
What is the reason? How to fix?
http://s90009lu.beget.tech/teete/
https://i.stack.imgur.com/gx8sz.png
javascript webflow
asked Nov 22 '18 at 15:19
Tony starkTony stark
31
add a comment |
I used webflow. Now there is a conflict when loading webflow.js.
What is the reason? How to fix?
http://s90009lu.beget.tech/teete/
https://i.stack.imgur.com/gx8sz.png
javascript webflow
asked Nov 22 '18 at 15:19
Tony starkTony stark
31
2
please provide some snippets of code. So it can give a solution to the question.
– DILEEP THOMAS
Nov 22 '18 at 15:20
@DILEEPTHOMAS The page loads a full file webflow.js. It contains too much code, so I can't paste it here.
– Tony stark
Nov 22 '18 at 15:25
Hi Tony, please try if you can find the cause of the issue. Remove any bits of code that don't cause any issues. Also, it looks like the website uses some kind of processing to generate webflow.js. Debuggein this kind of code is hard. Try to work with the raw sources instead.
– Sven van de Scheur
Nov 22 '18 at 15:28
add a comment |
I used webflow. Now there is a conflict when loading webflow.js.
What is the reason? How to fix?
http://s90009lu.beget.tech/teete/
https://i.stack.imgur.com/gx8sz.png
javascript webflow
asked Nov 22 '18 at 15:19
Tony starkTony stark
31
I used webflow. Now there is a conflict when loading webflow.js.
What is the reason? How to fix?
http://s90009lu.beget.tech/teete/
https://i.stack.imgur.com/gx8sz.png
javascript webflow
javascript webflow
asked Nov 22 '18 at 15:19
Tony starkTony stark
31
asked Nov 22 '18 at 15:19
Tony starkTony stark
31
asked Nov 22 '18 at 15:19
Tony starkTony stark
31
asked Nov 22 '18 at 15:19
Tony starkTony stark
31
asked Nov 22 '18 at 15:19
Tony starkTony stark
31
31
2
please provide some snippets of code. So it can give a solution to the question.
– DILEEP THOMAS
Nov 22 '18 at 15:20
@DILEEPTHOMAS The page loads a full file webflow.js. It contains too much code, so I can't paste it here.
– Tony stark
Nov 22 '18 at 15:25
Hi Tony, please try if you can find the cause of the issue. Remove any bits of code that don't cause any issues. Also, it looks like the website uses some kind of processing to generate webflow.js. Debuggein this kind of code is hard. Try to work with the raw sources instead.
– Sven van de Scheur
Nov 22 '18 at 15:28
add a comment |
2
please provide some snippets of code. So it can give a solution to the question.
– DILEEP THOMAS
Nov 22 '18 at 15:20
@DILEEPTHOMAS The page loads a full file webflow.js. It contains too much code, so I can't paste it here.
– Tony stark
Nov 22 '18 at 15:25
Hi Tony, please try if you can find the cause of the issue. Remove any bits of code that don't cause any issues. Also, it looks like the website uses some kind of processing to generate webflow.js. Debuggein this kind of code is hard. Try to work with the raw sources instead.
– Sven van de Scheur
Nov 22 '18 at 15:28
2
2
please provide some snippets of code. So it can give a solution to the question.
– DILEEP THOMAS
Nov 22 '18 at 15:20
please provide some snippets of code. So it can give a solution to the question.
– DILEEP THOMAS
Nov 22 '18 at 15:20
@DILEEPTHOMAS The page loads a full file webflow.js. It contains too much code, so I can't paste it here.
– Tony stark
Nov 22 '18 at 15:25
@DILEEPTHOMAS The page loads a full file webflow.js. It contains too much code, so I can't paste it here.
– Tony stark
Nov 22 '18 at 15:25
Hi Tony, please try if you can find the cause of the issue. Remove any bits of code that don't cause any issues. Also, it looks like the website uses some kind of processing to generate webflow.js. Debuggein this kind of code is hard. Try to work with the raw sources instead.
– Sven van de Scheur
Nov 22 '18 at 15:28
Hi Tony, please try if you can find the cause of the issue. Remove any bits of code that don't cause any issues. Also, it looks like the website uses some kind of processing to generate webflow.js. Debuggein this kind of code is hard. Try to work with the raw sources instead.
– Sven van de Scheur
Nov 22 '18 at 15:28
add a comment |
1 Answer
1
active
oldest
votes
So even though the provided information is minimal i'm going to give it a shot:
As there is no actual sourcecode (code given seems to be packaged) i'm assuming this is some kind of a plugin. Which leads me to believe that this might not be the only case. Let just look at the exact error:
Uncaught TypeError: Cannot read property 'tram' of undefined
What this means is dat the browser tries to ook for a property called "tram" in an undefined variable. As undefined is something that is... wel... undefined. There can't be any properties. This produces this error.
A good practice to start of with some context might be just using a Google search of the exact problem. Let's search for "Uncaught TypeError: Cannot read property 'tram' of undefined".
Some results points up, al indicating stuff with webflow. Let's look at this result: https://forum.webflow.com/t/how-to-trigger-webflow-js-slider/11268.
The third post states that adding the line var $ = jQuery; got the user a step further. This provides some very clear context.
var $ = jQuery; assigns $ refer to the place in memory of the variable jQuery, a popular library. This basically creates an alias. Remarkable: $ tends to be a default (shipped) alias of jQuery. Something is off here.
Opening the browser (Chrome) developer tools shows the error shown in the screenshot. We can get some more precise information here by utilizing the debugger.
- Open the devtools.
- Click on a link to webflow.js to open it the sources tab.
- Check the break on exceptions button (shaped like a stop sign).
- Use the "{}" on the lower left to format the code.
- Reload the page.
We can now see the code stop a certain point where it looks for tram. Just in front of that we see that it's looking in a newly created alias for window.$ (!).
The last thing makes to believe that indeed, jQuery is not properly installed. Either by the plugin or by a conflict in other modules. The suggested var $ = jQuery; line might work to fix this, but please keep in mind that jQuery should be made available first for this to work.
This last thing requires it to be bundled correctly or installed using a different method. As we don't know your exact situation you might need to look into this yourself.
answered Nov 22 '18 at 15:54
Sven van de ScheurSven van de Scheur
9031921
It really helped to get rid of the conflict, but it did not solve the problem. webflow.js contains scrollintoview animations but for some reason animations are missing. Anyway, thanks a lot
– Tony stark
Nov 22 '18 at 16:33
I jumped to conclusions. This did not help, unfortunately
– Tony stark
Nov 22 '18 at 17:14
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433967%2funcaught-typeerror-cannot-read-property-tram-of-undefined%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
So even though the provided information is minimal i'm going to give it a shot:
As there is no actual sourcecode (code given seems to be packaged) i'm assuming this is some kind of a plugin. Which leads me to believe that this might not be the only case. Let just look at the exact error:
Uncaught TypeError: Cannot read property 'tram' of undefined
What this means is dat the browser tries to ook for a property called "tram" in an undefined variable. As undefined is something that is... wel... undefined. There can't be any properties. This produces this error.
A good practice to start of with some context might be just using a Google search of the exact problem. Let's search for "Uncaught TypeError: Cannot read property 'tram' of undefined".
Some results points up, al indicating stuff with webflow. Let's look at this result: https://forum.webflow.com/t/how-to-trigger-webflow-js-slider/11268.
The third post states that adding the line var $ = jQuery; got the user a step further. This provides some very clear context.
var $ = jQuery; assigns $ refer to the place in memory of the variable jQuery, a popular library. This basically creates an alias. Remarkable: $ tends to be a default (shipped) alias of jQuery. Something is off here.
Opening the browser (Chrome) developer tools shows the error shown in the screenshot. We can get some more precise information here by utilizing the debugger.
- Open the devtools.
- Click on a link to webflow.js to open it the sources tab.
- Check the break on exceptions button (shaped like a stop sign).
- Use the "{}" on the lower left to format the code.
- Reload the page.
We can now see the code stop a certain point where it looks for tram. Just in front of that we see that it's looking in a newly created alias for window.$ (!).
The last thing makes to believe that indeed, jQuery is not properly installed. Either by the plugin or by a conflict in other modules. The suggested var $ = jQuery; line might work to fix this, but please keep in mind that jQuery should be made available first for this to work.
This last thing requires it to be bundled correctly or installed using a different method. As we don't know your exact situation you might need to look into this yourself.
answered Nov 22 '18 at 15:54
Sven van de ScheurSven van de Scheur
9031921
It really helped to get rid of the conflict, but it did not solve the problem. webflow.js contains scrollintoview animations but for some reason animations are missing. Anyway, thanks a lot
– Tony stark
Nov 22 '18 at 16:33
I jumped to conclusions. This did not help, unfortunately
– Tony stark
Nov 22 '18 at 17:14
add a comment |
So even though the provided information is minimal i'm going to give it a shot:
As there is no actual sourcecode (code given seems to be packaged) i'm assuming this is some kind of a plugin. Which leads me to believe that this might not be the only case. Let just look at the exact error:
Uncaught TypeError: Cannot read property 'tram' of undefined
What this means is dat the browser tries to ook for a property called "tram" in an undefined variable. As undefined is something that is... wel... undefined. There can't be any properties. This produces this error.
A good practice to start of with some context might be just using a Google search of the exact problem. Let's search for "Uncaught TypeError: Cannot read property 'tram' of undefined".
Some results points up, al indicating stuff with webflow. Let's look at this result: https://forum.webflow.com/t/how-to-trigger-webflow-js-slider/11268.
The third post states that adding the line var $ = jQuery; got the user a step further. This provides some very clear context.
var $ = jQuery; assigns $ refer to the place in memory of the variable jQuery, a popular library. This basically creates an alias. Remarkable: $ tends to be a default (shipped) alias of jQuery. Something is off here.
Opening the browser (Chrome) developer tools shows the error shown in the screenshot. We can get some more precise information here by utilizing the debugger.
- Open the devtools.
- Click on a link to webflow.js to open it the sources tab.
- Check the break on exceptions button (shaped like a stop sign).
- Use the "{}" on the lower left to format the code.
- Reload the page.
We can now see the code stop a certain point where it looks for tram. Just in front of that we see that it's looking in a newly created alias for window.$ (!).
The last thing makes to believe that indeed, jQuery is not properly installed. Either by the plugin or by a conflict in other modules. The suggested var $ = jQuery; line might work to fix this, but please keep in mind that jQuery should be made available first for this to work.
This last thing requires it to be bundled correctly or installed using a different method. As we don't know your exact situation you might need to look into this yourself.
answered Nov 22 '18 at 15:54
Sven van de ScheurSven van de Scheur
9031921
It really helped to get rid of the conflict, but it did not solve the problem. webflow.js contains scrollintoview animations but for some reason animations are missing. Anyway, thanks a lot
– Tony stark
Nov 22 '18 at 16:33
I jumped to conclusions. This did not help, unfortunately
– Tony stark
Nov 22 '18 at 17:14
add a comment |
So even though the provided information is minimal i'm going to give it a shot:
As there is no actual sourcecode (code given seems to be packaged) i'm assuming this is some kind of a plugin. Which leads me to believe that this might not be the only case. Let just look at the exact error:
Uncaught TypeError: Cannot read property 'tram' of undefined
What this means is dat the browser tries to ook for a property called "tram" in an undefined variable. As undefined is something that is... wel... undefined. There can't be any properties. This produces this error.
A good practice to start of with some context might be just using a Google search of the exact problem. Let's search for "Uncaught TypeError: Cannot read property 'tram' of undefined".
Some results points up, al indicating stuff with webflow. Let's look at this result: https://forum.webflow.com/t/how-to-trigger-webflow-js-slider/11268.
The third post states that adding the line var $ = jQuery; got the user a step further. This provides some very clear context.
var $ = jQuery; assigns $ refer to the place in memory of the variable jQuery, a popular library. This basically creates an alias. Remarkable: $ tends to be a default (shipped) alias of jQuery. Something is off here.
Opening the browser (Chrome) developer tools shows the error shown in the screenshot. We can get some more precise information here by utilizing the debugger.
- Open the devtools.
- Click on a link to webflow.js to open it the sources tab.
- Check the break on exceptions button (shaped like a stop sign).
- Use the "{}" on the lower left to format the code.
- Reload the page.
We can now see the code stop a certain point where it looks for tram. Just in front of that we see that it's looking in a newly created alias for window.$ (!).
The last thing makes to believe that indeed, jQuery is not properly installed. Either by the plugin or by a conflict in other modules. The suggested var $ = jQuery; line might work to fix this, but please keep in mind that jQuery should be made available first for this to work.
This last thing requires it to be bundled correctly or installed using a different method. As we don't know your exact situation you might need to look into this yourself.
answered Nov 22 '18 at 15:54
Sven van de ScheurSven van de Scheur
9031921
So even though the provided information is minimal i'm going to give it a shot:
As there is no actual sourcecode (code given seems to be packaged) i'm assuming this is some kind of a plugin. Which leads me to believe that this might not be the only case. Let just look at the exact error:
Uncaught TypeError: Cannot read property 'tram' of undefined
What this means is dat the browser tries to ook for a property called "tram" in an undefined variable. As undefined is something that is... wel... undefined. There can't be any properties. This produces this error.
A good practice to start of with some context might be just using a Google search of the exact problem. Let's search for "Uncaught TypeError: Cannot read property 'tram' of undefined".
Some results points up, al indicating stuff with webflow. Let's look at this result: https://forum.webflow.com/t/how-to-trigger-webflow-js-slider/11268.
The third post states that adding the line var $ = jQuery; got the user a step further. This provides some very clear context.
var $ = jQuery; assigns $ refer to the place in memory of the variable jQuery, a popular library. This basically creates an alias. Remarkable: $ tends to be a default (shipped) alias of jQuery. Something is off here.
Opening the browser (Chrome) developer tools shows the error shown in the screenshot. We can get some more precise information here by utilizing the debugger.
- Open the devtools.
- Click on a link to webflow.js to open it the sources tab.
- Check the break on exceptions button (shaped like a stop sign).
- Use the "{}" on the lower left to format the code.
- Reload the page.
We can now see the code stop a certain point where it looks for tram. Just in front of that we see that it's looking in a newly created alias for window.$ (!).
The last thing makes to believe that indeed, jQuery is not properly installed. Either by the plugin or by a conflict in other modules. The suggested var $ = jQuery; line might work to fix this, but please keep in mind that jQuery should be made available first for this to work.
This last thing requires it to be bundled correctly or installed using a different method. As we don't know your exact situation you might need to look into this yourself.
answered Nov 22 '18 at 15:54
Sven van de ScheurSven van de Scheur
9031921
answered Nov 22 '18 at 15:54
Sven van de ScheurSven van de Scheur
9031921
answered Nov 22 '18 at 15:54
Sven van de ScheurSven van de Scheur
9031921
answered Nov 22 '18 at 15:54
Sven van de ScheurSven van de Scheur
9031921
9031921
It really helped to get rid of the conflict, but it did not solve the problem. webflow.js contains scrollintoview animations but for some reason animations are missing. Anyway, thanks a lot
– Tony stark
Nov 22 '18 at 16:33
I jumped to conclusions. This did not help, unfortunately
– Tony stark
Nov 22 '18 at 17:14
add a comment |
It really helped to get rid of the conflict, but it did not solve the problem. webflow.js contains scrollintoview animations but for some reason animations are missing. Anyway, thanks a lot
– Tony stark
Nov 22 '18 at 16:33
I jumped to conclusions. This did not help, unfortunately
– Tony stark
Nov 22 '18 at 17:14
It really helped to get rid of the conflict, but it did not solve the problem. webflow.js contains scrollintoview animations but for some reason animations are missing. Anyway, thanks a lot
– Tony stark
Nov 22 '18 at 16:33
It really helped to get rid of the conflict, but it did not solve the problem. webflow.js contains scrollintoview animations but for some reason animations are missing. Anyway, thanks a lot
– Tony stark
Nov 22 '18 at 16:33
I jumped to conclusions. This did not help, unfortunately
– Tony stark
Nov 22 '18 at 17:14
I jumped to conclusions. This did not help, unfortunately
– Tony stark
Nov 22 '18 at 17:14
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433967%2funcaught-typeerror-cannot-read-property-tram-of-undefined%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
please provide some snippets of code. So it can give a solution to the question.
– DILEEP THOMAS
Nov 22 '18 at 15:20
@DILEEPTHOMAS The page loads a full file webflow.js. It contains too much code, so I can't paste it here.
– Tony stark
Nov 22 '18 at 15:25
Hi Tony, please try if you can find the cause of the issue. Remove any bits of code that don't cause any issues. Also, it looks like the website uses some kind of processing to generate webflow.js. Debuggein this kind of code is hard. Try to work with the raw sources instead.
– Sven van de Scheur
Nov 22 '18 at 15:28