Gail

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • in reply to: Remove Slider from all but front page #28138
    GailGail
    Participant
    • Topics: 1
    • Replies: 7
    • Total: 8
    Member since: March 5, 2016

    Thanks for your reply.
    I followed your directions. The home page slider, 4 boxes, and my own content for the “home” page did not appear on the “home” page.
    I realized that we have a static page named “home”; this was our home page specified in Settings > Reading. The URL without a page name (directory “/”) correctly showed the SKT BeFit Home Page Slide and 4 boxes, but not the content of our static page “/home”. Our static page “/home” showed its content but not the SKT Home Page Slider or 4 boxes.

    I did the following:

    1. Removed my custom CSS that made the slider & 4 boxes “hidden”
    2. Copied the content of the static page named “home” and pasted it into Section 1 in Theme Options > Sections
    3. Edited our menu: item “Home” was pointing to page “home”; replaced that with “custom URL” menu item pointing to “/”.

    Now it displays correctly. Thanks.

    in reply to: Remove Slider from all but front page #26973
    GailGail
    Participant
    • Topics: 1
    • Replies: 7
    • Total: 8
    Member since: March 5, 2016

    The suggestion from Shri will remove the slider on most other pages. However, we have a front page that is a static page, with our blog on another page (called “news”). The home page slider and 4 boxes appear on both pages. To remove it from the “news” page, SKT support suggested using Dashboard > Appearance > Theme Options > Basic Settings > custom CSS and entering CSS to hide the home page slider and 4 boxes on the “news” page.

    The CSS would be:
    body.blog .slider-main, body.blog section#wrapone {
    display:none;
    }

    However, even though the CSS successfully hides these items, I believe that the browser will still fetch the images and execute the JavaScript. (I could be wrong on this.) This adds an unnecessary burden to both the web server and browser. The PHP should really not generate the objects in the first place.

    in reply to: Befit theme from the local server to the web server #26969
    GailGail
    Participant
    • Topics: 1
    • Replies: 7
    • Total: 8
    Member since: March 5, 2016

    Just to add to my comment above: We also lost all settings when switching from SKT BeFit Pro to a child theme of that Pro theme; and again when switching back from the child theme to the parent. As with the domain change, there was no change in the database during either of these switches.

    I looked in the wp_options table. I did not find any option_name like “options_framework_befit-pro”. Instead I found rows with “option_name” equal to “skt_befit_pro”, “theme_mods_skt-befit-pro”, “skt_befit_pro_child”, and “theme_mods_skt-befit-pro-child”. So that would explain why switching to a child theme, for the first time, would lose all my settings. (It does not however, explain why I also lost settings when switching back to the parent theme. Perhaps I had changed the domain name between switching to child theme and switching back to parent theme.)

    In the row with option_name = “theme_mods_skt-befit-pro”, there was a relatively short list of 7 settings, with no domain names:

    a:3:{i:0;b:0;s:18:”nav_menu_locations”;a:1:{s:7:”primary”;i:3;}s:16:”header_textcolor”;s:3:”fff”;}

    However, in the row with option_name = “skt_befit_pro”, there was a long list of options, in a similar format, that included the domain name several times. For example:

    a:208:{s:4:”logo”;s:85:”http://myhostname.dtdns.net:8000/demo3/wp-content/uploads/2016/03/PMAmockLogo-1.png”;s:10: …

    It appears that “s” stands for string and the number after the “s:” is the length of the following string.

    So it is not enough to simply copy that table.
    It is also not enough to simply update the table using the SQL function REPLACE(option_value, “old_domain”, “new_domain”).
    You also have to adjust the string length number (85 in this example) if the length of the domain name changes.

    We need an easier way to migrate a web site using this theme.

    in reply to: Befit theme from the local server to the web server #26964
    GailGail
    Participant
    • Topics: 1
    • Replies: 7
    • Total: 8
    Member since: March 5, 2016

    I had a similar problem. I changed the domain name of the server; but I did not actually move the site to a new server, I just changed the domain name from a local host “myimac” to a dynamic DNS domain, “something.dtdns.net:8000”. So that row options_framework_befit-pro in the wp_options table was still there. But my settings were lost regardless. So there is something else going on besides the wp-options table not being copied.

    Please explain how to change the domain name without losing all the many settings in this theme. Thank you.

    in reply to: Remove slider from pages #26205
    GailGail
    Participant
    • Topics: 1
    • Replies: 7
    • Total: 8
    Member since: March 5, 2016

    (Sorry if this is off-topic; I just realized that the original post is about the SKT Biz/Corp theme. We have SKT BeFiT PRO theme.)

    add this in […] custom CSS box:
    #home_slider{display:none;}

    There are a couple of problems with this:

    1. The selector is incorrect. The HTML is:
      <div class="slider-main">
          <div id="slider" class="nivoSlider">
              <img src="..." />

      So the correct selector would be .slider-main.

    2. This is still not correct: it hides the slider not only on the blog (posts) page but also on the home page! To select only the <b>posts</b> page, you need to add an ancestor to the selector: body.blog .slider-main.
    3. On the posts page, I want to hide <b>all</b> home-page items; this includes the four boxes, whose HTML begins with <section id="wrapone" class="menu_page featuresbg">. So I would need to add an alternate selector: body.blog .slider-main, body.blog section#wrapone.
    4. Even if the CSS successfully hide these items, I believe that the browser will still fetch the images and execute the JavaScript. (I could be wrong on this.) This adds an unnecessary burden to both the web server and browser. The PHP should really not generate the objects in the first place.
    GailGail
    Participant
    • Topics: 1
    • Replies: 7
    • Total: 8
    Member since: March 5, 2016

    the Child theme wasn’t created properly

    We followed the advice at
    http://wordpress.stackexchange.com/questions/163301/versioning-import-of-parent-themes-style-css/182023#182023
    , which the official WordPress Codex
    https://codex.wordpress.org/Child_Themes#How_to_Create_a_Child_Theme
    links to (at “See here a more detailed discussion”) as the definitive way to create a child theme. If you have a more official and supported way to create a child theme, please point me to it. Don’t just say it “wasn’t created properly” without telling me how to create one properly.

    You don’t need to create a child theme as we have Custom CSS

    Yes, I already knew this. I wrote this in my post:

    the PRO version has a Custom CSS text area

    But as I wrote, the biggest problem is when the base URL (including domain name and port) is changed. You did not respond to this problem.

    Also we send emails of update after theme update so the theme doesn’t get automatically updated without you knowing so again no chance of anything being lost.

    Sending an email is nice; but unless the upgrade contains major bugs (would you tell us if it did?), we will upgrade to the new version, of course. You did not say whether upgrading the theme loses our settings. Does it?

    I would again request you to use the original theme and let us know if the settings lost stops there.

    As I wrote, I already switched from my SKT BeFit PRO child theme to the parent SKT BeFit PRO. Settings were lost in the process. Since then, I have not made any changes that would cause settings to be lost.

    I want to be assured that settings will not be lost when I move the site from one host to another. Based on my experience in item #5 above, they will be. This is not acceptable, with 100’s of settings that may have been changed. Please fix.

    Lastly check if you click on restore defaults by any mistake within appearance>theme options.

    I failed to mention it, but yes I actually had to do this once. I believe at item #7, settings were not simply reverted to defaults but were blanked out or set to nonsense values. For example, all the default font sizes were set to the same size, 10px. I had to click “restores defaults” to get back to reasonable numbers, then re-enter all my customizations.

    In short, your response was a non-response. Please re-read what I wrote and respond substantively to my main concern.

    in reply to: Remove slider from pages #25905
    GailGail
    Participant
    • Topics: 1
    • Replies: 7
    • Total: 8
    Member since: March 5, 2016

    I have the same problem as Hossam Samir: “despite the fact that i made it on “hide” in the theme properties it still appears on the news page which i made for the blog”. I will email you our site admin details.

Viewing 7 posts - 1 through 7 (of 7 total)