Forum Replies Created

Viewing 15 replies - 166 through 180 (of 470 total)
  • Thanks so much — that’s very helpful in a situation with multiple levels of group privileges — but I am looking for a way to take a group member back to whatever page they were trying to reach before they were redirected to the custom sign in page.

    So here is what typically happens.

    There is a useful, informative page on the web site, Page A.

    The group member receives the link to Page A in an email communication — for example, a private email sent to all group member announcing the creation of Page A.

    Group member uses the Page A link to go to the site but is not logged in, so is redirected to Page B, which is the custom log in page. I will call this B-1.

    Gruup member logs in. Now Page B looks different as it is displaying the appropriate text for members, and some useful links — but it is still Page B. Since appearance has changed with login, I will call this B-2.

    I want a way to redirect the user back to page A after a successful login — rather than having to re-enter the URL to Page A or to find it via navigation tools. So ideally I want the user to come to page A, be redirected to B1, and then be redirected back to page A after login rather than ending up on B2.

    The trickier part is to get the page to redirect back to the protected page after login. I haven’t managed to figure out how to do that, unfortunately.

    Instead, what happens is — the user goes to

    mysite.com/restricted-page

    the user is referred to the page with the login and notice “this content is restricted, please log in”) – i.e., mysite.com/login-notice-page

    After log in, the user is still on the same page where they logged in. (The restriction notice and login box is gone, because that is set to display only to people who aren’t logged in — but the other content on the page is still there) So they have to navigate back again to the restricted-page

    I am doing this; it’s very easy. You want the free plugin Groups 404 Redirect – https://wordpress.org/plugins/groups-404-redirect/

    So you then create a page with a login form, along with whatever notification text you want to include (such as “content restricted – please login to view”)

    Then simply set the Groups 404 Redirect to redirect to that page with the first option on its settings page.

    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.

    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.wordpress.org/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.

    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.

    I don’t know about SEO but I am using events calendar on a site that offers courses and here is what I have done.

    I used the pods plugin to create a custom page type called “course descriptions”. Each course has the course description on the page, and also lists all upcoming event with links. The events are simply put in using a shortcode tied to the category that matches the courses – [tribe_events_list category=””] I believe that this is a pro feature, so you’d have to get the premium upgrade to use it.

    The regular event calendar is also accessible from the home page so users really have a choice as to whether they want to read course descriptions or go straight to lists of the courses. So the site is sort of redundant, but once I set up a course description page I don’t have to revisit it again — and I was more concerned with making sure that site visitors could find what they were lookng for easily than SEO.

    Go to:

    Appeararance >> Theme Options >> Custom Home / Front Page Builder >> Content Boxes

    The text for the box is entered in the “Description” field.

    (It seems like you were already in the right place, but perhaps did not realize which field contained the box content)

    But the point is, you supplied a link to the site that you say has a problem. When others go to your site, we don’t see any evidence of skewing. So readers of your question would have assumed that you had resolved the problem. It looks like the problem may be specific to your computer or your browser.

    Thread Starter Abigailm

    (@abigailm)

    @savanipriyank — the reason I had the code in my child theme is that 2 years ago the upgrade to 3.5 completely changed Bootstrap slider display and I had to spend hours recoding and customizing the slider because of the changes. See my thread at https://wordpress.org/support/topic/problem-with-boostrap-slider-caption-after-theme-upgrade/ – and can see from comments there that this specific CSS dates from that time.

    So I appreciate that you’ve added new features so that my child style specification is no longer necessary — but the point is it is very annoying when Evolve upgrades add new feature that override previous settings.

    Thread Starter Abigailm

    (@abigailm)

    Yes, I had found that I had to re-enable those settings (even though they showed as “enabled” already) — however, the theme also overrode my settings for background color for the bootstrap slider caption.

    I had this setting in the child style sheet:

    #bootstrap-slider .carousel-caption h2 {
        background: rgba(147,182,201,0.4)};

    With the upgrade, the color was changed to

    background: rgba(0,0,0,0.7);

    That seemed to happen when I enabled the content boxes and clicked “save changes”, although the settings for the boostrap slider typography are on a different page … but maybe I’m mistaken and I just didn’t notice the problem at first.

    In any case, I’ve fixed it now, but it’s the same annoyance that crops up again and again with Evolve upgrades. It’s great that you add new features for new users — but it seems that the tweaks frequently impact style settings from previous versions.

    (ObviouslyI don’t want or need to build a new home page — I just want the one I have to look the same way before and after upgrade).

    Donna, I agree about the issue with !important — and that has been an annoyance for me with Evolve (which is why I mentioned it. When you select and customize layout in Evolve, it adds a large amount of in-line styling, and the in-line stuff will tend to override the style sheet.

    But when I look at my style sheet I see it’s not as bad as I was remembering– mainly because I haven’t actually done many customizations to the main theme- so I could be mistaken about it being an issue for this particular theme.

    @ma3ry — just by coincidence I happen to be using GeneratePress on a couple of sites as well as using Evolve… so I have an opinion. I like the simplicity of GP, so I have chosen it for basic, utilitarian sites — I can get things up and running very quickly.

    But straight of the box it’s not very pretty — whereas all the features in Evolve made it easy to create a very attractive commercial site very quickly.

    I also do a lot of my own customizations, but it’s pretty easy to customize Evolve with a child theme. The only problem is that I find I typically need to add to !important to modifications in the child theme style.css file to get the changes to stick in Evolve.

    For the site that you’ve linked to, I’d recommend staying with Evolve because either way you will be doing your own customizations, but I think Evolve makes it easier to create an attractive site with the built-in features. I just would recommend making styling changes to your child them css rather than relying on in-theme customization options for anything beyond the basics.

    Thread Starter Abigailm

    (@abigailm)

    Follow up — I did some testing and I was able to roll up to 3.8.2 and restore content boxes by going to to theme options and clicking “save” on the page with the content boxes–but that overrode other styling on the page (such as color of headline text on slider). I don’t have time to mess with going through various settings to restore them, so I just rolled back to 3.8.1 again.

    But I think somewhere along the lines the change to the Custom Home/Front Page Builder is causing a problem, at least in terms of the content box display.

    @ktsherb2017 — GoDaddy isn’t telling you that there is a problem with this theme; they are telling you that they don’t support any custom themes. It’s not a problem with the theme, but simply that it is beyond the scope of the hosting company’s support to try to debug the theme.

    If you want to continue using evolve. I would suggest the following:

    1. If possible, create a development copy of the site to work on.

    2. Install the WP Rollback plugin. As you work on the site, use that plugin to upgrade and rather than going from 2.6.4 to 3.8.1, work incrementally. I’d start with a 2.6.4 to 3.0.0 upgrade first, if that works, then try a higher version.That will help narrow down the point where things start to break. (But caution – read the theme’s changelog so you don’t inadvertently select a release that had a bug — the changelog will also give you clues as to which versions introduced changes that might impact site layout.

    I think that the big problem is trying to make such a major upgrade from a much older version of the site. Although you said that the site had not been updated since 2014, the 2.6.4 theme is actually older than that. V 2.6.4 was issued in November 2013, and apparently had some bugs, because v. 2.7.0 was pushed out 4 days later with “PHP and CSS fixes”.

    This is a big project because of the neglect of the site over the years. In your case, it may be less time consuming to start from scratch with a new theme rather than trying to debug the upgrade. You could even do that with evolve — by simply renaming the existing installation to something else, and then doing a clean install of the current evolve theme. That would give you the ability to essentially do a side-by-side comparison by switching back and forth between old and new theme.

Viewing 15 replies - 166 through 180 (of 470 total)