New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Versions #68

Closed
felipesega opened this Issue Aug 23, 2018 · 9 comments

Comments

Projects
None yet
2 participants
@felipesega

felipesega commented Aug 23, 2018

Please describe the behavior you are expecting

How can I migrate version 1.2 to 1.3 since for example in version 1.2 the container can be wide but in version 1.3 this is not possible.

Thank you

@EINazare

This comment has been minimized.

Collaborator

EINazare commented Aug 23, 2018

Hello @felipesega ,

And thank you for your interest in using our product.
Can you please provide a screenshot with the difference, i really do not understand what container can't be wide, and what wide means in your question?
Also, is this link helpful for upgrading the product?

Best,
Manu

@felipesega

This comment has been minimized.

felipesega commented Aug 23, 2018

Thanks for answering
Containers overflow on the navbar and the footer, it is also not possible to make them 100% wide in version 1.3 but in version 1.2 they work perfectly

On the other hand, thanks for the change.log, I'm already doing the migration.
error

@EINazare

This comment has been minimized.

Collaborator

EINazare commented Aug 24, 2018

Hello again @felipesega ,

Actually you can make them 100% wide.
Look at this example:
screen shot 2018-08-24 at 9 04 03 am 2

The footer is 100% wide.
Inside src/layouts/Pages.jsx you just need to change <Footer white /> to <Footer white fluid/> and it will be 100% wide.
For the navbar you need to change our jss inside src/assets/jss/material-dashboard-pro-react/components/pagesHeaderStyle.jsx change line 6 from container to containerFluid and also line 38 from ...container, to ...containerFluid,.

Hope this information helps you.

Best,
Manu

@felipesega

This comment has been minimized.

felipesega commented Sep 27, 2018

Hello Manu,

First of all I apologize for the delay in responding but I was assigned to another project while we finished the first one with Material Pro React, now that I am back in this project, I thank you very much for the tips that you have given me, they have worked for me.

Now the main problem is with the containers in the middle as they surpass other elements at the top and bottom, I send you some images, if you need more information please let me know.

Thank you very much
2018-09-27
2018-09-28

@EINazare

This comment has been minimized.

Collaborator

EINazare commented Sep 28, 2018

Hello again @felipesega ,

If you go on this page does it appear like on your project? Can you make me a screenshot?

Best,
Manu

@felipesega

This comment has been minimized.

felipesega commented Sep 28, 2018

Hello again @felipesega ,

If you go on this page does it appear like on your project? Can you make me a screenshot?

Best,
Manu

Hello Manu,

Let's say for example if you want to have content larger than what fits in the container, the container does not push everything down as it should be. This was done in version 1.2, but in 1.3 it does not, for now it is the main problem we have.

@EINazare

This comment has been minimized.

Collaborator

EINazare commented Sep 29, 2018

Hello again @felipesega ,

Now I understand the problem. Sorry for this.
I am going to search for a solution and be back with the fix.

Best,
Manu

@EINazare EINazare added bug and removed help wanted question labels Sep 29, 2018

@EINazare

This comment has been minimized.

Collaborator

EINazare commented Sep 29, 2018

Hello again @felipesega ,

The problem is that we set a maxHeight property inside the pages layout jss.
To solve this issue, go inside src/assets/jss/material-dashboard-pro-react/layouts/pagesStyle.jsx and delete line 12, the one with maxHeight.
By the end of today (29.09.2018), at around 10 pm CET, I will try to make an update on this product that will feature this fix as well.

Hope this information helps you.

Best,
Manu

@EINazare EINazare closed this Oct 5, 2018

@felipesega

This comment has been minimized.

felipesega commented Oct 5, 2018

Hello again Manu,

The problem has been solved thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment