SiteBolts
Forum Replies Created
-
Hi @anowerhossain16 – None of these issues have been resolved yet.
If you visit the site that we linked above, you can see that the same three bugs as before are still present, even in the latest version of Happy Addons.
Remember, this is on a fresh site with the Hello Elementor theme, Elementor plugin, and Happy Addons plugin. Any user who sets up a new site with that simple setup is going to be greeted with these same bugs.
Hi Anowar, thanks for the follow-up. Here are the results of our testing:
1 – Clearing Elementor’s cache doesn’t resolve any of the issues. The testing site we have set up here isn’t using any other forms of cache either.
2 – Setting “Load Font Awesome 4 Support” to “Yes” fixes the missing dropdown icon. That’s a good workaround, although the Happy Addons plugin should ideally check for this setting and/or have some kind of default/fallback to account for this. Since this issue occurs on a fresh WordPress installation with all of the default Elementor settings, that means that the Happy Addons “Nav Menu” element is currently showing a broken icon to anyone who hasn’t specifically gone and changed that setting, unless their theme happens to be loading FA4 on its own, which isn’t guaranteed. If FA4 is required for Happy Addons to work correctly, then the Happy Addons plugin should enqueue it on its own, not fail silently.
3 and 4 – We don’t see any breakpoint options on Happy Addons “Nav Menu” element. There’s a section called “Responsive Navigation” but it doesn’t appear to let you make any breakpoint width adjustments. Also, even if that does fix it, the real issue is that the nav menu’s default CSS doesn’t correctly handle the (768px – 782px) range of browser widths. This issue occurs on all of the “Twenty” themes as well as “Hello Elementor” with no modifications made, so the underlying issue appears to be with the Happy Addons CSS.
5 – This is a fresh installation with just Elementor, Happy Addons free version, and the Hello Elementor theme with no customizations made. These issues also occur on WordPress’s official “Twenty” themes. No workarounds or special settings should be required to have the Happy Addons “Nav Menu” work correctly in these situations. These appear to be bugs that need to be corrected in a future release.
Please have your developers review these issues on your end when you get a chance; they can be easily reproduced on a fresh installation of WordPress. We like many of the features that the Happy Addons “Nav Menu” element offers over the default WordPress nav menu, but right now those issues are problematic enough that we can’t justify using it on production sites.
@tanvir101 – The issues described above are an issue with the Happy Addons nav menu widget, not with any specific website.
The webpage that we linked to is a bare-minimum reproducible example page with just Hello Elementor, Elementor, and Happy Addons installed. It shows that the issues occur even when there are no other plugins involved.
Forum: Plugins
In reply to: [Event Booking Manager for WooCommerce] Event list order bug@devidfri – Uninstalling and reinstalling the plugin successfully fixed the issue on our site.
It’s been two months since we did that and so far the issue hasn’t reappeared.
@teoustreet – You’ll need to rename or delete the plugin’s files via FTP or your web host’s file manager, or have their support do it for you. There’s unfortunately no way to do it through the normal wp-admin UI because of the fatal error.
Afterwards, you can reinstall the working 3.4.10 version with this ZIP file: https://downloads.wordpress.org/plugin/facebook-for-woocommerce.3.4.10.zip
Forum: Plugins
In reply to: [Meta for WooCommerce] Critical error with update 3.4.7 > 3.5.0Here’s a link to the last working version if anyone needs it: https://downloads.wordpress.org/plugin/facebook-for-woocommerce.3.4.10.zip
Forum: Plugins
In reply to: [Page scroll to id] Support for other WYSIWYG editors like ACF?Hi @malihu ,
We found a quick fix for this issue. It looks like the plugin’s malihu-pagescroll2id-tinymce.js file just needs to add the buttons to the ACF toolbar via a filter, at which point everything works correctly.
Here’s the code to add near the bottom of the file:
if (acf && typeof acf.add_filter === 'function')
{
acf.add_filter('wysiwyg_tinymce_settings', function(tinymce_editor, id)
{
if (tinymce_editor.toolbar1)
{
tinymce_editor.toolbar1 += ' ps2id_tinymce_custom_button_link ps2id_tinymce_custom_button_target';
}
return tinymce_editor;
});
}Here’s what it looks like after adding that code: https://sitebolts.com/wp-content/plugins/page-scroll-to-id/includes/malihu-pagescroll2id-tinymce.js?nocache=may062025v1
If you’re able to release an update with that fix, that would be really helpful.
As a temporary workaround, the deprecated legacy Places API can still be enabled via this hidden link:
https://console.cloud.google.com/apis/library/places-backend.googleapis.com
But it’ll be turned off soon, so a plugin update is still needed to support the new Places API.
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] ORDER DUPLICATING@inpsydekrystian – We’ve also been having this issue for several weeks now, but with a site that’s on WP Engine (which uses Cloudflare) and doesn’t have any Sucuri or Elementor plugins installed.
I see that your plugin released two new major updates in the last few weeks, which makes the timing seem related. Are you sure there’s nothing new that might be causing this?
We’re going to roll back this plugin to 2.9.6 for now and disable the PayPal button on all pages except the checkout page to see if it helps.
- This reply was modified 1 year, 1 month ago by SiteBolts.
Forum: Plugins
In reply to: [Happy Addons for Elementor] Mobile menu color bugHi @anowerhossain16 –
Just to clarify, the HappyAddons Nav Menu already has a text color control, and it works fine for changing the desktop colors.
But in the snippet shown above, it appears that you’ve commented out the lines that would make it work on mobile, which seems accidental. Perhaps that was done for testing at some point and accidentally pushed to production? It works completely fine if you uncomment those two lines.
Forum: Plugins
In reply to: [Happy Addons for Elementor] Mobile menu color bugFollowing up on this, the relevant file is happy-elementor-addons/widgets/navigation-menu/widget.php
Strangely, it appears that you’ve already written the selectors that would make it work on mobile:
$this->add_control(
'nav_menu_item_color',
[
'label' => __( 'Color', 'happy-elementor-addons' ),
'type' => Controls_Manager::COLOR,
'default' => '#333333',
'selectors' => [
'{{WRAPPER}} .ha-navigation-menu-wrapper ul.menu > li > a' => 'color: {{VALUE}}',
'{{WRAPPER}} .ha-navigation-menu-wrapper ul.menu li .ha-submenu-indicator-wrap' => 'color: {{VALUE}}',
// '{{WRAPPER}} .ha-navigation-burger-menu ul.menu li a' => 'color: {{VALUE}}',
// '{{WRAPPER}} .ha-navigation-burger-menu ul.menu li .ha-submenu-indicator-wrap' => 'color: {{VALUE}}',
],
]
);But the last two lines were commented out (by accident?), so the mobile menu’s text color is currently unable to be changed via the UI.
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Order comments when using Stripe LinkHi @mahfuzurwp –
We have WooCommerce’s default order notes field on our checkout page and it works fine when customers use traditional payment methods like PayPal, but if we enable Stripe Link and they pay with that, then they’re never presented with any way to enter their order notes.
We’re not picky about the details but just need some way for customers to enter their order notes when paying with Stripe Link, either via WooCommerce’s order notes field or through the Stripe Link interface.
Forum: Plugins
In reply to: [Breeze Cache] PHP 8.4 fatal errorIt’s already resolved on our end and that’s a nice temporary workaround for anyone who needs it, but most users are just going to see a broken site and not know how to do any of that. It would be better to patch your plugin to either catch the fatal error or avoid relying on mbstring to begin with.
Forum: Plugins
In reply to: [Breeze Cache] PHP 8.4 fatal errorIt looks like the issue is that Breeze requires the PHP “mbstring” module to be active and for some reason Namecheap has it disabled by default in PHP 8.4.
I would recommend either removing that dependency if possible or at least catching the error and displaying an admin notice instead of letting it throw a fatal error.
@ahmedimran – What solution did you end up going with? We’re facing the same dilemma.
@mosesmedh – Would you consider adding this option as an official setting in the plugin? We want to allow Google and Apple Pay as normal payment methods that appear alongside the others.