This is searchable archive of our old support forums, which operated from 2012 - 2016. To find out how to get support for your current theme, please visit our support page.

davidcpa135

Forum Replies Created

Viewing 15 replies - 16 through 30 (of 33 total)
  • Author
    Replies
  • in reply to: embed youtube wo playlist #13217
    davidcpa135
    Participant

    s/b :embed with an

    <iframe>
    in reply to: embed youtube wo playlist #13207
    davidcpa135
    Participant

    Fixed. I found that if you embed with an , it doesn’t cycle through the play.

    in reply to: Text size in Toggles #12167
    davidcpa135
    Participant

    Got it–almost

    found what I believe to be the right css file at framework\assets\css\themeblvd.css
    on a localhost set up I tested the following (basically inserting font size in various places to test )

    /* Toggles */
    .accordion-group-last,
    .tb-accordion {
    	margin-bottom: 20px;
    	font size=16pt;
    }
    .accordion-heading .accordion-toggle {
    	color: inherit;
    	-moz-border-radius: 4px;
    	-webkit-border-radius: 4px;
    	border-radius: 4px;
    	font size=16pt;
    }
    .accordion-heading .active-trigger {
    	-webkit-border-bottom-right-radius: 0;
    	-webkit-border-bottom-left-radius: 0;
    	-moz-border-radius-bottomright: 0;
    	-moz-border-radius-bottomleft: 0;
    	border-bottom-right-radius: 0;
    	border-bottom-left-radius: 0;
    	font size=16pt;
    }
    .accordion-heading .accordion-toggle:hover,
    .accordion-heading .accordion-toggle:focus {
    	background: #f5f5f5;
    	color: inherit;
    }
    .accordion-heading .accordion-toggle .switch-me {
    	margin-right: 5px;
    	font size=16pt;
    }

    doesn’t appear to be changing the title font of the toggle
    I’m self-taught on css-does this seem like the right approach?

    in reply to: use of html in builder #12125
    davidcpa135
    Participant

    Sorry, I was unclear. In the Builder, we added a column element to the page layout.
    The options for the column content are
    external page
    floating widget
    raw content

    Would the raw content option accept html to display an image from another part of our site? This would be outside the WP media library.

    Thanks

    in reply to: tabs with post slider #11564
    davidcpa135
    Participant

    Thanks for the answer. Was able to use toggles to get the same basic effect

    in reply to: Post slider #11509
    davidcpa135
    Participant

    I’ll check it out. Is there a link in the documentation where I could read more about how crop sizes are handled?

    in reply to: Update to 3.0.2 #11410
    davidcpa135
    Participant

    Good advice. I was able to map the layout and then re-tool on the live site. Best of all, it finally dawned on me what was inserting text below the footer etc. Got it working with 3.2.

    in reply to: Update to 3.0.2 #11347
    davidcpa135
    Participant

    After 3 days, I give up. Can you recommend a consultant or can this be contracted through themeblvd?

    in reply to: Update to 3.0.2 #11337
    davidcpa135
    Participant

    Made some more progress by renaming some of the above folders and then moving. In summary, still missing a few widgets from the sidebars which I can fix. The top 2 lines of one of the text widgets is now appearing under the footer on all pages and posts. Don’t see it when I edit pages. The homepage is based off a template so I tried copying the content to a new page with the old template but still get this verbiage below the real footer. Template appears fine.
    If I can get rid of the stuff below the footer, we’ll be ok.

    in reply to: Update to 3.0.2 #11323
    davidcpa135
    Participant

    Jason,
    I think I have isolated the problem. Need to get your take on how to fix. As mentioned above, I always look over the restored site in the localhost environment (2.1.5 prior to upgrade attempt). Everything works fine. I started poking through all the dashboard areas with the idea of finding what looked out of place. Under themes I have active Alyeska 2.1.5 as expected as well as twenty thirteen, twenty twelve etc.

    What struck me as odd was that there was an additional alyeska theme listed but not activated. The details show it to be 3.0.

    My guess is that during first attempt to upgrade on my internet host (which crashed the site and required hosting company to restore) that, within the FTP program I dropped the 3.0 file inside the existing alyeska 2.1.5 file. Logging back onto the live site I see the 3.0 upgrade site alyeska folder, and its subfolders, inside the alyeska folder (2.1.5) under themes.

    Live site is still functioning fine under version 2.1.5. Here’s where it gets interesting. On the localhost I tried the following solutions.

    From localhost dashboard–>Appearance–>Themes deleted the non active 3.0 theme-site crashed on localhost
    From localhost explorer deleted the alyeska folder (3.0) that was inside the theme/alyeska (2.1.5) folder–site crashed
    From localhost dashboard tried to activate the 3.0 theme- site crashed.

    Any suggestions appreciated.

    in reply to: Update to 3.0.2 #11319
    davidcpa135
    Participant

    Thanks for the response and sticking with a troublesome question. After restoring to localhost, I always go in and play around with the site (under 2.1.5) and all appears well. Backup Buddy appears to handle the url change behind the scenes when it’s restoring.

    I’ll try again with the plugin cache disabled and download the update again just in case.

    in reply to: Update to 3.0.2 #11304
    davidcpa135
    Participant

    FYI- update. I tried the Thomas Edison approach trying different things in the test environment to eliminate what doesn’t work. Latest attempt was not renaming the old theme folder but dropping the new one on it and letting it overwrite.

    Upon login both themes (2.1.5 and 3.2) show as available but I had to activate 3.2. At the point the widgets are scrambled up again.

    in reply to: Update to 3.0.2 #11302
    davidcpa135
    Participant

    The new (3.0.2) folder is called alyeska. Renamed the old folder. I did notice one other thing. When I logged into the dashboard (after the above steps) the theme had switched to twenty-twelve. I selected and activated the new alyeska and had to resave (check the box) the primary menu again.

    Would it be worthwhile to try with the old alyeska folder deleted (via FTP) and then load the 3.2 folder?

    in reply to: update theme #10281
    davidcpa135
    Participant

    It seems this is more of a problem for my hosting company but to answer your question at first the site was just scrambled. The menus were turned off somehow in the upgrade, Turning them back on solves the jigsaw puzzle look and made the pages navigable but the sidebars were on top instead of the side etc. Got my backup buddy restore and it crashed due to timeouts in the restore process. Due to this crash, I can’t get to the dashboard. I think the only workable solution is for the host to restore to Sunday’s backup.

    I say all that to ask this question. Having watched the videos etc on installing the update – it seems that the upgrade would be just a matter of copying the new Alyeska folder into the theme directory. When I try this again should I download a copy of the alyeska folder first then do the update? Is so, and there are problems, would copying the original folder back to the theme directory be a quick way to fix them?

    As always, thanks for the help.

    in reply to: Using video as featured image #9623
    davidcpa135
    Participant

    ok-I managed to duplicate the effect I wanted. You use the “make a video the featured image” option on the new post screen,select full-with thumbnail, and (most importantly) do not put an embed,link, or iframe of the video in the post body.

    This seems to work.

Viewing 15 replies - 16 through 30 (of 33 total)