Thierry

Hi Oliver,

me again… I decided to abandon the idea of category pages as front page sections for the moment. Static pages with nice posts sliders which allow to filter by category do the job for now. Found a nice plugin for that.

Thus, I wanted again to point out the importance of named anchors in the #page-slug style. Having these would allow to easily re-arrange front page sections (adding, moving, etc.) without having to rewrite the menus all the time.

Kindest regards from France

Thierry

Just for info: I just got feedback from the WP-Multilang plugin developer. In fact, the translated URL rewriting works, when the full URL is given in the custom link, i.e. https://mydomain.com/#myanchor. I tried this and can confirm. Thus, if a new update with named anchors and putting the full url by default will come from you, we could definitively close this part of the construction site.

The other thing, the category page(s) as front page sections, might be more complex or need more thinking, thus I’m ready to put it on low priority for the moment.

As I said, that would be a “nice to have”, no hurry!

I imagine adding the upcoming-categories (or any other) archive page as if it were as static page into a front page section. I imagine it being rendered like the original archive page, again like a static page which is also be rendered identically, independent of the page being displayed as stand-alone or as a front page section.

The academies are a good example. Under the hood, I have the academies basically organized in chronological categories like academies-2018, academies-2019 and so on. And I have one category apart from that which is upcoming-academies and which I attribute temporarily always to the next two or three upcoming academies as a second category to have a quick selector.

This way, I automatically have an archive page for that temporary category which is automatically always up to date (reachable from the main menu). But in order to have that on the front page, too, I actually add manually single post blocks (another Gutenberg plugin) to the static front page. That works, too, but I feel that this manual add is redundant work, and the style is horribly different from the upcoming-academies category page. That’s why I’d like to integrate this one directly as a front page section. And with named anchors, I would not longer have to rework the custom links when I add front page sections or when I change the order…

Will try to play with PayPal, now.

Ah, and how can I feed your PayPal again for all your efforts?

Yes, great! Everything works as expected, now!

Already thinking about new ideas like…

• Your jQuery injecting the page slug as an id for the content-panel div, to have named anchors like /#contact in the custom links
• Added functionality to use category archive pages as front page sections, too

…just dreaming…

Experimenting a little, I found that

.panel-content {
    padding-top: 5.7em;
}

might be a valid workaround. Could this be injected via jQuery, too?

• This reply was modified 6 years, 4 months ago by Thierry.

Hi Oliver,

the post date issue is solved, thank you very much.

I actually added two front page sections (only in the English version of the site) and added two corresponding links “Test 1 and “Test 2” in the main menu below “Welcome”.

The jumping to top does not longer happen, black magic?

But at least on my Mac (macOS Sierra, Safari 11.1), it scrolls still beyond the page title. As I told you, I’m not a web developper, but I’ve seen others solving that via CSS with some negative padding…

Edit: Same problem on same Mac with Firefox 60.0…

I’ll leave these 2 test menu links in place for the moment to allow you testing this. The URL is https://theremin.academy

Thank you for your patience!

Thierry

• This reply was modified 6 years, 4 months ago by Thierry.

In case you really can‘t reproduce some problems, we‘ll need to find and agree about a short ?demo“ time where I‘d turn everything on for a few minutes, so that you could have a look.

Regarding the WPML issue, it‘s a general WP custom link problem, since these work basically with hard coded urls, so it’s not only about your anchor navigation. I will try to put that on the WPML developer’s shoulders, since I understand that I’m already eating ways too much of your precious time.

I’m sad to say I found a few things which I can’t (yet) confirm…

Hiding the post date works well in the single post view, but not on category pages, the date remains visible above each listed post, for example here: https://theremin.academy/teachers/

For testing the one page navigation, I added one static page in front page section #1 and I replaced the page link in the main menu by the corresponding custom link /#panel1-title.
When I’m already somewhere on the front page, clicking this custom link in the menu will jump to the top of the page which should not happen.
When I’m on a different and independent page or post and click the same custom link in the menu, it jumps to the front page section, but still scrolls too far, the section page title is again hidden behind the header image, so no improvement from the last release.
Had (again) to revert to the single page navigation, it’s a prod site and I unfortunately can’t allow to keep it malfunctioning to show and reproduce these errors.

Another issue I discovered just now is the incompatibility with the WPML (multi-language) plugin which I use to maintain the site in English (default), French, and German. That’s not your fault, I have to see with them how I can get custom links rewritten depending on the actual language, so that if I’m for example on the German front page (https://theremin.academy/de/), the custom link would be automatically rewritten as /de/#panel1-title.

Ok, my fault, didn‘t look in the admin appearance menu because I thought everything was in the customized. Thank you for your patience with me. Besides the scrolling too far, it works fine now.

Just to prevent any misunderstandings (which are for sure on my side), I expected that to work like demonstrated here:

https://wpcolt.com/create-one-page-website-using-twenty-seventeen-theme/

Thank you!

In fact, I found the slider to adjust the number of front page sections. At the very first moment, I thought that it did not work until I understood that I had to click on publish, close the customizer, and open the customizer again to see the changes take effect.

Afterwards, I feel a little dumb… Can’t see how to make a menu item from a front page section. Do I have to create a custom link with a #panel-1 anchor? Will try that now.

I think that I am not a bad coder in C++ and assembly when it comes to make music on 32bit ARM CPUs. But this html/php/js stuff is definitively not my cup of tea…

Edit: Works somehow with a link towards #panel1, but I don’t know if it’s my Safari browser or what, although the id=”panel1″ comes before the h2 class=”entry-header”, the browser scrolls too much forward that the header will already be hidden and the content be displayed on top of the page.

Reverting everything temporarily for now until I have a better understanding of all that…

• This reply was modified 6 years, 4 months ago by Thierry.

Incompatibility with newest Gutenberg version. Was fixed in latest release.

Incompatibility with newest Gutenberg version. Was fixed in latest release.