Ps is not defined

Rodriguez pro commented 6 years ago

Hi,

Yes, plus another small changes, but the configuration is almost the same, the problem come when I include the mdb.js using the file directly on the web, I can see the window variable hold Ps property(window.Ps), but if I include the file using require or import, the window variable does not contain Ps object.

Here is an example of my code.

//Jquery library
import 'jquery';
//Bootstrap
import 'bootstrap';

//Common js for all pages
import './common'

import '../../vendors/mdb/js/mdb';

// SideNav Button Initialization
$(".button-collapse").sideNav();
var sideNavScrollbar = document.querySelector('.custom-scrollbar');
Ps.initialize(sideNavScrollbar);

Everythings works fine until Ps.Initialize(sideNavScrollbart) line.

Piotr Glejzer staff commented 6 years ago

hmm well maybe it will be not so much clever idea but did you try to use path without ../ like that :

import '../vendors/mdb/js/mdb';

cageq pro commented 6 years ago

laravel with the mdb pro also have the problem : 

using the webpack 

//require("mdbootstrap-pro");

so , mdb pro can't be required into ? 

Piotr Glejzer staff commented 6 years ago

Well, it should be work. We will check it and fix it as soon as possbile. We are very sorry about that bugs. 

morgoth pro commented 6 years ago

Hi, have you fixed the "Ps" bug? I'm a Pro user using webpack (MDB Pro 4.5.14). Everything works like a charm. When I try to use the double-nav with Ps.initialize(...) I get that reference error.

If there is a way to get it to work, it should be appreciated a lot. Even with hardcoded solution for now is good enough because this is blocking deployment tasks.

thanks a lot

Piotr Glejzer staff commented 6 years ago

Hi.

we are very sorry but we didn't fix that problem yet. We have that problem in our 'bug list' but I recently moved it to 'priority bugs' so we will think more about that in next week. We are sorry again. Have a nice day.

Best,

Piotr

artur.karczmarczyk commented 6 years ago

Hello, has the problem been solved? I recently purchased the Pro licence and I'm extremely dissatisfied with the quality of the software. On saturday I configured everything according to webpack tutorial, which disappeared on Monday only to appear again today. So now I followed the new tutorial from scratch only to learn that Ps bug exists still. When I follow the hint from below with using PerfectScrollbar(sideNavScrollbar) instead of Ps.initialize(), I still get just grayish overlay instead of the menu bar.

Piotr Glejzer staff commented 6 years ago

Did you try that workaround below? 

Piotr Glejzer staff commented 6 years ago

We upload perfect scrollbar to the latest version. Did you try this? Errors still the same?

kylescousin pro commented 6 years ago

I have the same issue

MD Pro 4.8.0

Bartłomiej Malanowski staff pro premium commented 6 years ago

@kylescousin, did you try to install perfect scrollbar as a separated node module? Here's the guide: https://github.com/utatti/perfect-scrollbar#install