Fix #1080 Materialize Upgrade

[guido97]

Closes #1080

Description

Change use for modals methods, fix calls to toast, use AutoInit(),
The automatic initialization has been removed in Materialize Version 1

In general, update according to official guide and test changes
https://github.com/Dogfalo/materialize/blob/v1-dev/v1-upgrade-guide.md

[brylie]

@guido97, I'm having difficulty reviewing these changes since there are a lot of changed lines in the template files. Are there some particular aspects of the templates that needed to change?

@gorkemarslan just merged a similar pull request. Were the changes similar to this one that fixes the Materialize errors?

[guido97]

Hi @brylie, my changes are for finish update to the version 1.0.0 of materialize (Latest release), the most of these changes are for calls to toast. The version 0.97.6 is from April 1, 2016, perhaps works, but is oldest.
In this new version automatic initialization was removed, but we can use Materialize.AutoInit (), therefore some initializations I commented. in the image below you can see modal and toast working

[gorkemarslan]

@guido97, as @brylie says, it is going to a bit difficult to follow changes in templates and JS codes.

Issue #1080 appeared after we removed dependencies folder and change the static Django template tags with related CDN, as can be seen in issue #1051. So our initial purpose here should be to fix the problem on the similar base and should be simple as in PR #1080, Upgrading materialize framework from 0.97.6 to 1.0 can be considered as a further step after PR #1080. But we try to give weight to using Django templates if possible and reducing code dependencies on JS. (See similar discussion in #1129).

I am skeptical to upgrade Materialize here. You notice upgrading from 0.100.2 to 1.0. That's nice. However, there should be some changes from 0.97.6 to 0.100.2. As far as I see, there is lack of tutorials for the older versions of materialize on the Internet. So upgrading can cause further side effects that can be detected harder because someone has to check all pages and JS codes to make sure there is no problem. This needs some time and energy, of course.

Keeping simple and focusing on fixing opened issues should be our strategy.

Could you check current develop branch work well with PR #1080? If you find new issues, could you report them by creating a new Issue?

[gorkemarslan]

Fixed by #1158