• Resolved Abigailm

    (@abigailm)


    I am currently running Mantra Version: 2.6.1.1 on a site with a child theme.

    I can see from change log notes at https://themes.svn.www.ads-software.com/mantra/3.0.1/readme.txt the upgrade to version 3.0 is a major change, including changes to default styling throughout.

    I don’t want to break my existing site!

    Is the new update compatible with earlier versions? If so, what steps need to be taken to preserve existing look and feel of the site?

    I like to keep all my sites updated for security reasons, and I love the Mantra theme, but am concerned that the big changes with the update would require a major site redesign to preserve look-and-feel of existing sites.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Abigailm

    (@abigailm)

    I am going to mark this as resolved as I have upgraded the theme and made all needed corrections to theme settings and my child stylesheet.

    If anyone else is reading this, the Mantra 3.x upgrade includes major changes to the theme stylesheet including:

    * Changed default site width, default content, headings and meta font sizes and font families, some default colors
    * Updated all social images with new images
    * Replaced “under the menu” social locations with site absolute left/right
    * Entirely revamped mobile menu
    * Dropped text shadow and box shadow effect usage from different elements like site title, post titles, meta areas, images etc.
    * Increased padding and font size for inputs/selects/textareas
    * Increased padding for content, sidebars and article containers
    * Changed comments list appearance
    * New “back to top” button and animation
    * Removed single post top navigation (bottom navigation remains)
    * Removed footer widgets title background and padding
    * Edited main menu padding and switched to using relative font sizes
    * Added extra padding and margins to footer elements
    * Increased H1-H6 default headings sizes, made H5 and H6 uppercase

    These changes will change layout and appearance on already developed sites.

    It took me about 2-3 hours to make changes to my child theme stylesheet and to review pages on my site to correct display problems.

    So I would suggest that anyone who updates should work with a staging or cloned site first if possible.

    None of the changes were difficult to address – it was just a matter of adjusting very simple CSS — but I think that the Mantra team could have done a better job of documenting the changes, given the size of the theme user base.

    Hi Abigailm, it is my opinion, too, that the team could have made a much better job. I am working on three pages with the mantra theme and I spent lots of time to search for the changes. I am not a css or html pro, so it was very hard for me t find all the mistakes which suddenly appeared. Not all of them are solved yet. Especially the changes for the presentation page made me angry. I hate uppercases, but I didn’n find the word in the theme’s css code. Finally some of my translations (I use the plugin Loco translate) were re-translates without a chance to translate it again. I can see that the word is translated in the plugin, but on the page it appears in english (I am German) again.

    Herbert

    Thread Starter Abigailm

    (@abigailm)

    They’ve just pushed out another upgrade with even more style changes:

    = 3.0.2 =
    * Fixed magazine layout applying to single posts
    * Cleaned up theme generated styling code and moved custom-styles.php to includes/ subfolder
    * Rewritten theme styles enqeueing code to use current WordPress standards ***this can result in styles loading in incorrect order if you’re using a child theme with old code
    * Updated options-based CSS generated functions to use wp_add_inline_style()
    * Optimized meta viewport code and switched to cryout_seo_hook
    * Cleaned up some inline JS and options JS code
    * Fixed Google fonts failing to enqueue until first theme options save
    * Fixed bullet vertical alignment for widget items
    * Fixed minor design issues in the theme settings page
    * Fixed post formats displaying format images on single posts

    (From https://themes.svn.www.ads-software.com/mantra/3.0.2/readme.txt)

    I don’t know what the notation about child themes with “old code” means — but I just updated and am not seeing any problem. But something to be alert to.

    The reason I posted the list of CSS changes above is to help others know where to look for corrections.

    Changes 3.01 and also 3.02 affects site on mobile devices too!!

    Now im busy to change all back as it was.
    But still on mobile devices poor views.

    I am not happy at all!
    If it’s not working tomorrow i am going to use a other theme.

    ??

    • This reply was modified 7 years, 2 months ago by leolivenl.
    Thread Starter Abigailm

    (@abigailm)

    I had a problem with mobile view of the social media icons overlapping with the other text in the header and footer, plus they were too small for mobile use.

    I didn’t really need them on this particular site so I simply set my style sheet on the child theme to remove them in the mobile view.

    I don’t remember seeing that problem before the upgrade, but I really can’t be certain.

    Well,

    I found the problem!

    After update 3.01 and 3.02 the site responsiveness was enabled.
    First i updated to 3.03

    Disabled it and now it’s working good, (as i like).

    I’m clueless how to fix the problems the update caused to my site https://www.calvarycouponers.com. It’s a hot mess now ??
    Any input or advice would be much appreciated!

    Helen

    Is there a way to revert back to the old one if this can’t be fixed?

    Thread Starter Abigailm

    (@abigailm)

    You can revert back to the prior theme with the WP-Rollback plugn – https://www.ads-software.com/plugins/wp-rollback/

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Upgrading to 3.0x with Child Theme’ is closed to new replies.