since2007
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Dazzling] Help with menu on mebile deviceCheck out one of the many other topics that already dealt with that issue, like:
https://wordpress.org/support/topic/top-menu-on-doesnt-work-after-upgrade-to-wp-5-6/
Forum: Themes and Templates
In reply to: [Dazzling] what has been fixed with the new update?Edit:
my bad, if the modify date of the files is seriously true then my comment is wrong, december 2019 is actually one AND a half year ago before it got released just now and fixed nothing.Forum: Themes and Templates
In reply to: [Dazzling] what has been fixed with the new update?According to README.md:
####2.1.3 - 11.12.2016#### * Added wp_body_open * Added License & Copyright * Added unminified Scripts and stylesAnd that’s wrong for some reasons:
– totally wrong date (the file changes have a date of 11.12.2019, which means the update was laying somewhere around for half a year before release)
– they removed the changelog entry for version 2.1.1
– readme.txt has itself as version 2.1.2
– README.md lists the depedencies of html5shiv.js and respond.js but that’s not new nor is it mentioned in readme.txt, too.For actual changes from what I could see:
– header.php has (as they say) that wp_body_open check
– footer.php has the scroll-to-top as button (was a div before)
– in style.css mostly image and navbar got :focus selector (only had :hover before). and inc/extras.php got adjusted accordingly
– inc/custom-header.php got a check for header_textcolor removed
– tgm-plugin-activation.php changed requirements from kiwi-social-share 1.0.3 to kali-forms 1.2.0So yes, they didn’t solved any problem. :/
Forum: Themes and Templates
In reply to: [Dazzling] Assigning H1 withouth removing logoIn header.php there is a check if you’re on the Homepage, then it puts the logo in h1 or else it puts it in a span. Somehow for me it always ends in a span.
So in your child(!) theme around line 44 change:
<?php echo is_home() ? '<h1 class="site-title">' : '<span class="site-title">'; ?>
to:
<h1 class="site-title">and around line 59 change:
<?php echo is_home() ? '</h1>' : '</span>'; ?><!-- end of .site-name -->
to:
</h1>That way the logo always ends up in a h1, even on crawling the site. Hope that’s what you were looking for.
- This reply was modified 4 years, 11 months ago by since2007. Reason: typo
Forum: Themes and Templates
In reply to: [Dazzling] Top menu on doesn’t work after upgrade to WP 5.6Update:
they just came out with a Dazzling version 2.1.3, but sadly I couldn’t find a changelog.
I tried it in a test enviroment and the above mentioned issue is still there, hence my fix is still working the same way.
Forum: Themes and Templates
In reply to: [Dazzling] Menu Bar on mobile phone is not workingIn general Dazzling works with WooCommerce, I have a site where it was working fine for 2 years.
See my reply here for what changed when WordPress 5.6 came out recently and affected Dazzling’s menu:
https://wordpress.org/support/topic/top-menu-on-doesnt-work-after-upgrade-to-wp-5-6/
If you open your site on desktop with devtools open you will see the exact same Bootstrap error message.
Forum: Themes and Templates
In reply to: [Dazzling] Top menu on doesn’t work after upgrade to WP 5.6Same here.
This is because Dazzling theme includes an outdated Bootstrap v3.3.6,
WordPress 5.6 now comes with jQuery v3.5.1 and not 1.9.1 anymore.When opening DevTools you will see the error:
“Bootstrap’s JavaScript requires jQuery version 1.9.1 or higher, but lower than version 3”Bootstrap supports jQuery 3 as far as I know from v3.3.7 on (which is from mid 2016 already) and below v5 (which doesn’t need jQuery anymore).
There are now two ways:
1.) get a more recent theme under active development
2.) update Dazzling’s Bootstrap to v3.3.7
To do so get the bootstrap.min.css and the bootstrap.min.js and put them into the respective folders in “/wp-content/themes/dazzling/inc/”.
Just discovered and tried that myself and Menu is working again. 🙂
- This reply was modified 5 years, 4 months ago by since2007. Reason: typo