laurentlanglais

Thank you for your answers. It’s a bit too techy for me, so if you could bear with me a little bit more I would appreciate. The guy being unprofessional I will keep the other calculator that I am renting, which is on this page.
https://www.fengshuienfrance.fr/calculateur-bazi
Same problem however on phones and they say it’s API and would charge quite a sum to have it fit on different screens, so I would prefer to do it myself if I can implement such coding. But I’m not sure if they are saying this to overcharge basically…The thing is, I need one of those calculator to eventually work on my site on phones.
When I look at the page source I get this
<meta name=”viewport” content=”width=device-width, initial-scale=1″ />
Is there some css lines I can add to rewrite this, and how, for it to work?

Hello and thanks for your answer.
Well a calculator such as this one https://bazibz.masteryacademy.com/Default.aspx gives the chart and tables scaled down exactly to the phone screen size, on which one can then zoom in. This is what I would try to implement…You would however need to register (for free) to try it and see what I mean, if that’s ok.

Thanks for your answer Nicolas

I have found the plugin that conflicts…and it’s Nimble page builder 🙂

As soon as I deactivate it the slider appears!

So what do I do? I wish to keep Nimble for the look I’ve built. Is it because I’ve included some section under the top menu that the slider cannot appear?

Thanks for all these answers Nicolas.
About the homepage and Yoast/Nimble.
You wrote: For the home page, when you display the latest posts, it’s a little different because there’s no page to edit in WordPress. In this case, the SEO plugin will allow you to optimize the title and description meta tags, and Nimble Builder won’t prevent it.

I have written a meta-description in Yoast for this home page (at least the blank page on which the Nimble architecture is built on) but cannot see this meta-description when I look at the source online for the frontend/home of my site.
So what do I do wrong? how to integrate this description in the source?

How can I actually edit the metadescription of my front page once it’s been built in Nimble, for example? Thank you.

Hi Nicholas
For the past 3 years during which I have used Memberpress on my site, the system to restrict access is always the same. I have created a rule that only members subscribed to one of my subscription can access content. Then I create a post that is in this category, therefore falling under this rule. If the post is only in this category then automatically Membepress protect its content and people have to log in (so need to have a paid subscription) to access the content. It has always worked and the only post that is not protected and for which content is fully visible despite this category/rule is the one I have designed in Nimble builder – hence me thinking the problem can only come from Nimble. It seems that even if the post was created in this category, once I edited the post through Nimble it didn’t take into account the rule/protected category?

I still haven’t been able to solve this. I am a bit clueless with coding, while still understanding the overall logic of the post you’ve linked to. What I would need is the following if possbible
1. What is the name of a general nimble builder section that I want to move/put in the code? In the example given: my_nimble_header_location, should I replace by: my_nimble_main_content_location, or my_nimble_main_location, my_nimble_body_location, my_nimble_container_location or something else please?
2. Once it is done, which file do I need to copy from the parent theme to include the hook function – is it Main Index template, or Custom Page template?
3. In this file do I just add <?php do_action(‘my_nimble_XXX_location’); ?> and it should work?

As a reminder I want to edit my front page template and being able to insert a section between featured pages and the blog/posts section.

I’d really appreciate being guided a bit more because so far it’s not working. Thank you!