DWsCoreWP

Hello Tessa,

Please excuse me for only being able to answer you now, as I was out of action for a few days for health reasons.

Thank you for your detailed answer to my post and also for translating the answers into German for me. I really liked it and thought it was really great of you 🙂

Based on your answers and the question about stored data, I must have completely misunderstood the actual application area and current function of DTX. At least as far as my application is concerned.

To explain:
When I installed DTX for the first time many years ago, this was because you couldn’t transfer data to a CF7 text field using “Post or GET”. I solved this with DTX at the time.

And only now, after many years, I was looking for a way to use “Post or GET” to preselect a specific CF7 drop-down select entry.

What I didn’t know at the time of my post and the email to you, however, was that pure transmission using “Post or GET” has been implemented in CF7 for some time and that DTX is no longer necessary for this function.

So I’m really terribly sorry if I’ve wasted your time with my request, but I only found this out by chance after my post to you (see the link below), before I got a bout of flu.

CF7: Getting default values ​​from the context
https://contactform7.com/getting-default-values-from-the-context/

I think that I may have expressed myself somewhat poorly in my post, so that you had to assume that my request was actually a DTX use case, which is what I assumed myself at first.

At this point I would like to apologize to you again for not doing more thorough research before my post to you. The idea that CF7 can already do this never occurred to me. I only knew from the past that this was possible with DTX.

As a small gesture of reparation, I would like to do something for your coffee fund via PayPal, so please let me know how I can do that.

Thanks again for your support and your plugin, I will definitely come back to it when a use case requires it.

Best regards
Werner

• This reply was modified 1 year, 7 months ago by DWsCoreWP.

Hello malihu,

the last solution you suggested didn’t work so well, since a scrolling problem arose again in that clicking on “Home” from another page or a section no longer scrolled to the top of the start page.

But in combination with your previous solution (see code below) and a short search in the forum for “Home”, I found this post and finally found a satisfactory solution by adding the following to it.

Previously, as you suggested, I had moved the “Page Scroll to ID Target (headline)” before the first paragraph, so everything works fine now.

#headline{
  position: absolute;
  top: 0;
  height: 100vh;
}

Here is the complete CSS again, which, in conjunction with the GeneratePress Menu Hover Animation and your great support, has now led to a really satisfactory result.

/* Source: https://docs.generatepress.com/article/adding-menu-hover-animation */
@media (min-width: 769px) {
  .main-navigation .menu > .menu-item > a::after {
    content: "";
    position: absolute;
    right: 0;
    left: 50%;
    bottom: 15px;
    -webkit-transform: translate3d(-50%,0,0);
    transform: translate3d(-50%,0,0);

    display: block;
    width: 0;
    height: 2px;

    background-color: currentColor;
    transition: 0.3s width ease;
  }
  .main-navigation .menu > .menu-item.current-menu-item > a::after,
  .main-navigation .menu > .menu-item.current-menu-ancestor > a::after,
  .main-navigation .menu > .menu-item > a:hover::after {
    width: 50%;
  }
}


/* Fixed "Page scroll to id" issue when multiple menu items are highlighted when using GeneratePress Hover Animation (see above) */
.main-navigation .main-nav ul li[class*="current-menu-"] > a[href*='#']:not([href='#']):not(.mPS2id-highlight):not(:hover) {
	color: inherit;
	background-color: inherit;
}

@media (min-width: 769px) {
	.main-navigation .menu > .menu-item.current-menu-item > a[href*='#']:not([href='#']):not(.mPS2id-highlight):not(:hover)::after,
	.main-navigation .menu > .menu-item.current-menu-ancestor > a[href*='#']:not([href='#']):not(.mPS2id-highlight):not(:hover)::after,
	.main-navigation .menu > .menu-item > a[href*='#']:not([href='#']):not(.mPS2id-highlight):not(:hover)::after{
		width: 0;
	}
}

#headline {
  position: absolute;
  top: 0;
  height: 100vh;
}

By the way, I think I’m not the only one with this problem, but this might also be helpful for others who work with GeneratePress.

I knew you were a superhero 🙂 and thanks again for your support.

• This reply was modified 3 years, 4 months ago by DWsCoreWP.
• This reply was modified 3 years, 4 months ago by DWsCoreWP.

Hello malihu,

the fact that the links are no longer briefly highlighted when the page loads works great.

However, as far as your suggestion is concerned to set a section ID for the home link and to create an individual link for the home button, I have now installed it once (see website), but it does not meet my expectations, since it does not scroll should, but it does instead of just loading the home page.

I really appreciate your effort, but it can’t stay the way it is now, as the home page isn’t supposed to have its own section and just isn’t allowed to scroll.

Isn’t there another option here?

Many thanks again for your support.