Forum Replies Created
August 13, 2015 at 5:19 pm in reply to: Auto [lightbox] question vs older rel="themeblvd_lightbox" method #22915
Yeah we were behind the curve on updating the theme but we have it under control now. I’ve enable that feature. Figured it was something simple. Thanks for your help! 🙂
Just to follow up. I’ve fixed the issue. I used the custom conditionals like you suggested and it worked nicely and even eliminated the need for the customized files in the root of the theme. Thanks for all your help!
I’m going to try your suggested approach with the custom widget area and using a conditional.
Thanks again for the help!
Ok I’ve located the issue. It’s actually sort of the other way around. We had a developer do a little custom work for us way back when we launched the site. He created a couple of extra files that are placed in the main theme along with single.php, content.php, etc.
I see them now because their modified date is different than the rest of the files. It would seem they just need to be modified to work with the updated theme. I suppose that’d be the case even if they were in the child theme.
I’ll take a crack at that. It’s been a while since I messed with these files but I think I can work my way through it.
Thanks for jogging my memory!
I think originally the issue we had was that the two plugins we use (simple maps and event organizer) generated their own pages. So we needed a way to tell wordpress and the theme that if simple maps generates a page, use X sidebar. We weren’t sure of any other way to do that but there may be a better way.
The function code still works for the most part. The styling is what seems to be off because the menu is full width and above the page content. I’m trying to compare the two installs and see if I missed something. I just wasn’t sure if the theme update changed some styling somewhere.
We definitely learned the lesson on putting top level template files in the child theme. The only one in there now is the header.php file as far as top level ones go (the other two being functions.php and style.css).
I’ll continue to work on it but I hope that clarifies it a little more.
I see now. I was resizing Firefox to simulate a mobile browser. As it turns out, FF shows the sidebar on top but Chrome displays it correctly. My phone seems to show it correctly as well. Just one of the quirks of browsers. I think I’m all set. Thanks!June 24, 2015 at 7:42 pm in reply to: Remove responsive "hamburger" that's built in to Alyeska #22234
Perfect, thanks again!June 24, 2015 at 3:02 pm in reply to: Remove responsive "hamburger" that's built in to Alyeska #22222
Ok, that does hide it but one last request. I need the area that would show the menu to not be hidden. I know normally the menu would appear when you clicked the hamburger. So I’m not sure if this it beyond the scope of the theme or not. If you check it now, you’ll see what I mean. I get the blue bar but can’t get to the menu.
Thanks for your help!June 24, 2015 at 1:10 pm in reply to: Remove responsive "hamburger" that's built in to Alyeska #22220
I will give that a try. On our live site the theme is a child theme so we should be ok to implement it in that regard. I’ll let you know how it goes. Thanks for your help!
Ah, gotcha! That makes total sense. I was making it out to be more difficult than it was. It was one of those days…
I got it figured out without using the plugin. The map plugin provided a page template and I just had to code a custom sidebar for it to call up. Used the theme as a guide to make sure it got styled right and so forth and it’s done. I grabbed that widget plugin for future use as well. Thanks for the help! 🙂
Yep, I looked around and found some resources on their site that seemed to be taking me in the right direction. I’ve managed to manipulate the sidebar so now I just have to tweak the coding and that should do the trick.
I looked around in the widget area manager but the problem I’m running into is that the pages aren’t there as options. The map plugin we use just creates pages based on data we import. So the pages are there but they aren’t, in a way. I feel like it might require some tweaking of the actual code to accomplish. I’ll provide a couple of screens to help explain what I mean.
Thanks for your help!
Wow, I knew it was right under my nose. That did the trick! The confusion was with another menu plugin I have going so it had pushed that option further down. At any rate, thanks again for the help! I’ll try to look harder next time, haha.