mlazaru staff commented 2 months ago

How did you import MDB? Have you followed this installation guide?

marketingpayabletruckstop-com premium commented 2 months ago

I did a manual installation following the guide at the link provided.

mlazaru staff commented 1 month ago

I need more details to better understand the problem. Can you tell me when the error exactly occurs? It looks like it could be caused by incorrect imports. I could check it for you if you send me the code that would allow me to reproduce the problem.

marketingpayabletruckstop-com premium commented 1 month ago

The error occurs on page load.

I am calling the mdb.min.js from MDB4 4.20.0 near the bottom of the body.

That is all I needed to reproduce the issue.

I am assuming that the mdb.min.js file is referencing picker-date.js, but I don't know where in the file structure the js expects to find the file. I tried to review the js, but it is minified and compressed - not human-readable.

mlazaru staff commented 1 month ago

There is picker-date.js file in mdb4\src\js\pro\ but that should not be the case since you're using bundled code from mdb.min.js.

Are you using any bundler or framework? Does this problem occur after running index.html straight from the downloaded zip?

marketingpayabletruckstop-com premium commented 1 month ago

Thank you for your reply. The error does not occur when viewed from the index.html in the downloaded package.

Looking closer at the error, I see that the file path is webpack://src/js/vendor/pro/picker-date-time.js.

When I click through in the inspector I can see the source as you described. With this new information, I think my original ask is the wrong question. Instead, is there any insight you can give me on the error reported?

mlazaru staff commented 1 month ago

For building with webpack, the only way is to import all files from mdb/src/js in the webpack configuration.

marketingpayabletruckstop-com premium commented 1 month ago

The odd thing is, I do not build my project with webpack - this is just how it was arranged in the map file - so that is the source path that appears in the browser.

I am calling mdb.min.js without any build.

Any idea how to resolve the error considering it isn't being built with webpack?

mlazaru staff commented 1 month ago

Could you send me a code with the error reproduced?

marketingpayabletruckstop-com premium commented 1 month ago

I can't seem to reproduce it on a simple HTML page.

My implementation is in a Wordpress instance if that somehow helps.

marketingpayabletruckstop-com premium commented 3 weeks ago

I can't seem to reproduce it on a simple HTML page. My implementation is in a Wordpress instance.

Is there any additional insight you might offer into this error?

marketingpayabletruckstop-com premium commented 13 hours ago

I was finally able to determine that the "file" being referenced was not a file at all but a section of mdb.js that appears to be a file based on the way it is mapped. On line 18423, in $.extend($.fn.pickadate.defaults, "pickadate" is undefined. It looks like "pickadate" is referenced as l elsewhere in the file and when I update "pickadate" to be "l", I no longer received the error.

It would appear that the issue is in fact in the mdb.js file. I am not sure of the consequences of changing that variable name and would prefer that it be addressed by someone more familiar with the code base of your library. Would it be possible to have the bundle file corrected or could you provide some insight?

Thank you for your continuing assistance.