Forum Replies Created
-
Posts
-
Thanks. What I meant about "current and useful" was not asking a subjective question. I recall that when I looked into doing upgrades last year (back when the impending launch of 5.0 and Gutenberg had everyone in a tizzy), I was told that Metro was end-of-life. Now I see Metro Pro is current. But perhaps my problem is the site I'm asking about is built on the old Metro (not Pro) theme? It's using:
Metro child theme v1.0
The Admin area is also indicating that I can only upgrade Genesis to 2.2.1So it looks like I was wrong. Maybe Metro Pro 2.2.2 was just a test install and the child theme that's actually active is quite old and not Pro.
This child theme has been significantly customized, so I can't just swap in Metro Pro and expect it to work. Sigh. It's looking like a total rebuild. Some aspects of the current site have broken, like blog pagination.
Thank you Sridhar. Conditionals are a great approach. I bought the Mobile Smart Pro plugin at Codecanyon, because in addition to is_mobile, it let me set a totally different homepage for mobile vs desktop, which turned out to be the easiest solution.
I'm terrified now that the plugin will eventually be abandoned, but figure that by paying for it, I can help ensure that it will be supported into the future.Since buying into Studiopress over 5 years ago, I've seen so many themes and plugins rise, fall, and be abandoned. It's nice Studiopress is still here.
Has anyone used the ideas in these tutorials to implement a different slider, like layerslider from codecanyon? Did it work just the same?
Thank you. I tried that but found it limiting. I bought Ubermenu for the one Genesis site I've built so far, and it replaced all the menus — regular and mobile — and offers many more options. (while increasing the page-load overhead)
I've noticed that even on the official demo for the new Parallax Pro theme, sub-categories can't be selected on mobile devices. It's very disappointing. I gave up and bought a 3rd-party menu plugin to make my mobile menus work, and may not buy from Genesis again without more fully-baked features.
Please let us know if you find a solution you like!May I ask how did you resolve this issue with your site?
(I'm really frustrated at the state of mobile menu support.)Thank you for posting this solution! I had the same problem with having no effect in some browsers, but not others. Commenting out this line in the CSS solved it for me too. And the default body text got slightly thicker, but still "normal". I liked the thin type, but having bold type is more important.
Anyone: Is there another solution that will keep the 300 thin type and allow or <b> tags to work?
John, your mobile menu solution is truly elegant. Maybe you can change the button that appears in the upper right corner into a full-width button/bar that sits between the header logo and the page content? (leaving the rest of it just the way it is)
Good point! And nice site. I'm just concerned that the button isn't as obvious as a bar (people prefer interface elements they already are familiar with).
Olivier, I like the way your menu looks when expanded. Do you find it odd that the menu turns from a bar to a button, and then the mobile menu appears at the bottom of the page? Are your web visitors OK with that?
fotodog13, that menu is great! It's nicer for the user than my uber menu. Did you base it on a publicly available tutorial or add-on library, or did you make it by yourself?
—LEeI did install and use Uber Menu ($16 at codecanyon).
It is very well documented, with fast and good support. I was able to use the Uber configuration panel to customize the colors, fonts, height, width, borders, etc. without coding. If I had just gone with this from the beginning, I'd have saved a lot of time. I'd use it again.
You can see it in use on the main menu here:You can only have one uber menu per page, so on the above example site where there are two menus, I am stuck with the upper secondary menu being the genesis Metro default menu.
I still want Studiopress to update all their themes with mobile-responsive menus, and am disappointed they are selling so many themes as "responsive" without this feature included. Once they update Metro with a real mobile-responsive menu, I'd certainly remove uber menu in favor of the built-in one, on the assumption it would require loading less code and therefore speed up the site a bit.
(Sorry for the delay responding to give you this update.)
Very nice, fotodog13.
I am in touch with Brad in his tutorial comments, and he wants to be clear that the tutorial code is based on the Sample Theme for Genesis 2.0, and would need modification for any other theme, like the Metro that I'm using.Hmm, I found a Metro demo on Brad Potter's site with his responsive menu, so I wonder what went wrong with my implementation of his demo... I may have to try it again:
Yes, I can confirm that it's easy to have Disqus dupe/mirror the comments into your WP database. So yes, you can dump Disqus at any point and retain all the comments for use with a local/built-in commenting solution.
Thank you William! My experience has been that Disqus loads asynchronously, so if that's the case, does it still hurt google's analysis of your site load time?
I have used Disqus on one news site, and the owner likes it because moderation is less necessary. There is an option to automatically sync the comments into your wordpress database, but I'm not sure if those synced comments show up in a way that helps search. Do you know?