Giorgio25b

Thanks so much @anlino : proactive and on top of your business as usual.
The issue is RESOLVED on my end!
https://rimotivazione.koinesistemi.com/
hopefully @elhyaban will find the same result and close this ticket.

Cheers,
Giorgio

• This reply was modified 4 years, 11 months ago by Giorgio25b.

@anlino I can confirm that the mobile anchor links have been fixed introducing though a regression on the desktop view navigation.
The very first click on any anchor link works, see here: anchore-links-menu-test-site
Consequentially all the other internal links are all leading to the bottom of the page.
Tested on Chrome, Firefox and Brave (latest versions to date)

Thank you!

@anlino thank you for being on top of this!
I really appreciate the end result, especially knowing how busy you have been with Twentytweny development.
It works exactly as expected.
Excellent work

Hi @karmatosed ,
there is actually something that bothers me on some themes: is the fact that Gutenberg styles are overridden by poorly coded inline css (with excessive abuse of !important) rules and therefore the look and feel of the theme stays the same regardless our effort to customize the content blocks.
So I guess what I’m trying to say is that I’d love a toggle option somewhere that would force my Gutenberg settings for that post (or dunno maybe also globally in the Gutenberg options) to be applied and override the theme settings.
I know that this might be an edge case, but poorly coded theme are still a big reality out there so…
That’s it for my 2￠ today, hope this helps!

Thanks @anlino I guess/hope that the patch could solve the issue on both themes, since also Twentytwenty has the same problem.
I wish I could help more with the code, but that JS is above my pay grade.
Thank you!

@gatorbri99 I got a suggestion from another user, here below, but I did not have time to explore it. Also it seems a little bit too much to fix an issue, seems more like a refactoring of the nav script.

For single page navigation case, you may need to create additional scripts to highlight the active #project id section you just reached if you wanted to complete the single page navigation manner.

Similar to scroll spy method, for best UX you may need to add smooth scrollto the particular section#id. This feature would complete all possibility especially if we wanted to showcase how Gutenberg block and section can achieve with this new default theme.

Conceptually how it work;

In mobile, click the mobile menu toggler,
Mobile menu revealed
Click on particular link (let say #portfolio)
Menu add menu highlight active class to ? Portfolio (may highlight parent/ancestor page)
Mobile menu closed, Mobile menu toggler reversed to default state
Screen will smooth scroll to selected section

Though no signs from the developer yet on this issue

@triblu other than the memory_limit (ideally set to 512Mb) can you check that
max_execution_time=120 and max_input_time=120 are set to at minimum these values?

It’s very often a max_execution_time runtime error, once those parameters are set (via php.ini or cPanel or whatever tools your server offers) you should be good to go.

• This reply was modified 5 years ago by Giorgio25b. Reason: formatting code portions

Agreed!
Plus it is an unlikely scenario that you have the wrong short code on a page while there are no forms associated with it.
Nonetheless, thanks for taking care of the issues and for the plugins.

I know my bad, my apologies for the confusion, but to give a little bit more context:
I had a unique scenario related to this message, no contact form 7 present!
Therefore the message is there because there is no check for if CF7 == [ ] or something like that.
Cheers and thank you!

@lechon yes, but .htaccess is where most of the ithemes settings are stored, so my wild guess would be on some sort of sanitizing function that is stepping in after ithemes settings, regardless which file they are in.
Would be interesting to compare your .htaccess before and after update. In my case was so simple and straight forward that it took me a minute to fix it, though for a minute my dn name/user/password were visible as plain text on my homepage. I had to create and clone a new db and user and I changed passwords, table prefix and salts after.

Hi guys, I don’t know if it is of any helpto your issue, but what happened to my wp-config.php is just this:
after its own ithemes settings and comments, the new updated version 6.9.0 just closed automatically the ?> php tag, leaving all the WordPress settings lingering just as plain text comments.
I removed the ?> closing tag and all went normal.
Though since I didn’t like ithemes settings on top of my wp-config.php I moved them at the bottom, so if it happens is just closing the php markup at the end without causing any problem.

<?php
// BEGIN iThemes Security - Do not modify or remove this line
// iThemes Security Config Details: 2
define( 'FORCE_SSL_ADMIN', true ); // Force SSL for Dashboard - Security > Settings > Secure Socket Layers (SSL) > SSL for Dashboard
define( 'DISALLOW_FILE_EDIT', true ); // Disable File Editor - Security > Settings > WordPress Tweaks > File Editor
// END iThemes Security - Do not modify or remove this line?>
....
the rest of my code was below this point

note the // END iThemes Security – Do not modify or remove this line?>

Hope this helps.
G.

• This reply was modified 6 years, 9 months ago by Giorgio25b. Reason: code typo
• This reply was modified 6 years, 9 months ago by Giorgio25b. Reason: code typo
• This reply was modified 6 years, 9 months ago by Giorgio25b.

You started the tread with the back-to-the-top link issue,
then you moved to those pages 100vh, which BTW can be solve like:
id="bloque1" background-color: red; height: 100vh;
and
id="bloque2" background-color: blue; height: 100vh; padding-top: 0px;

then the overflow for these pages should be set to visible in case the content is higher than the screen height!

the sticky footer can be easily handled by the Hueman theme customizer, there is no need to re-invent the wheel, it has already been implemented, but your custom css should be like

#footer {
    position: fixed;
    bottom: 0;
}

Hi Dario,
the back to top link is a standard link that points always to #
Doing so, regardless the page, template, id, that link will always scroll to the top of any page.

As usual would be easier to debug having a live link to refer to.

I did have the same issue, but after a full-refresh all started working as expected.

What kind of conflict?
A link to your site?
What version of the plugin? WordPress? Theme? all the info you can give the merrier…