Ruman Ahmed
Forum Replies Created
-
Hello @sevenseconds777,
Thank you for your cooperation on this matter. It appears that you are using the PHP snippet option instead of the JS option. Please switch to the JS snippet option and paste the code as shown in the screenshot: https://prnt.sc/C0zAnmERCcsp
Hopefully, this might help you in this matter.
Best regards!
Ruman Ahmed.- This reply was modified 6 months, 2 weeks ago by Ruman Ahmed.
Hello @sevenseconds777,
Thank you for sharing the detailed information. Currently, in FluentBooking, you can only switch the number format between US style and EU style, and there is no built-in option to remove decimal places. However, there is a workaround that allows you to remove decimal places when events are embedded on a page using a shortcode. You can use the code snippet shown in the screenshot: [https://prnt.sc/woK439b3SZF1] and add it through a code-snippet plugin such as FluentSnippets.
Hopefully, this helps with your requirement.
Solution Code: https://github.com/RumanCodes/WPManage-Ninja/blob/master/fluent-booking/js-snippets/remove-decimal-points.js
Code Snippet Plugin: https://ww.wp.xz.cn/plugins/easy-code-manager/
Best regards!
Ruman Ahmed.Hello @emiel9d,
Thank you for sharing the detailed information. It seems this issue may be caused by a specific configuration that we need to investigate from our end. We might require temporary admin access to your site to look into it properly. Please open a support ticket here so we can examine the issue in detail and provide the appropriate assistance.
Best regards!
Ruman Ahmed.Hello @afrs,
Thank you for sharing the detailed information anf for bringing this to our attention. I have tested it on our end and it seems like a possible bug. I have reported it to our developers, so they will take a deeper look at it and fix this issue soon.
Best regards!
Ruman Ahmed.Hello @altala,
Thank you for sharing the detailed information. Currently, FluentSnippets works this way, it globally activates snippets across all sites in a multisite network. So, there’s no workaround available for this at the moment.
However, if you’d like, I can submit this as a feature request to our R&D team for further investigation and potential future implementation. Please let me know if you’d like me to proceed with this request.
Best regards!
Ruman Ahmed.Hello @dimy,
Thank you for sharing the detailed information. Could you please enable the debug log to check if it’s showing any errors related to FluentSnippets?
Share Debug Log: Please enable the debug log by defining the following constants in the wp-config.php file of your website (located in the public_html folder, accessible via a plugin or your hosting panel). This will generate the actual error log.
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', true );After enabling it, please share the log details with us so we can investigate this matter further. You can reload the page where the critical error appears, and it will display the direct error code there.
Please let me know the update.
Best regards!
Ruman Ahmed.Hello @willgreeny,
Thank you for sharing the detailed information. FluentSnippets automatically attempts to deactivate any script if a fatal error is encountered. However, in some cases, you might still get locked out due to a fatal error within one of your snippets. This doesn’t happen often, but if it does, or if you simply want to disable all code snippets temporarily, you can enable Safe Mode.
You can learn more about why this happens and how to disable Safe Mode by setting the variable to
falseinstead oftrue, as shown here: [https://prnt.sc/Wlhwcjs3dTGb].Best regards!
Ruman Ahmed.Hello @lweedman,
Thank you for sharing the detailed information. If it’s possible, could you please share a bit more context about the conditional logic you’re using and the code you’ve implemented? This will help me take a closer look and provide you with the appropriate assistance.
Please let me know the update.
Best regards!
Ruman Ahmed.Hello @rebornhairppp,
Thank you for your cooperation regarding this matter. Regarding the snippets group feature, it is already available in FluentSnippets. To group your snippets, simply create a group and select it while creating a new snippet, as shown in the screenshot: [https://prnt.sc/Ag4CZ79qx2UI]. Hopefully, this might help you in this matter.
For the others suggestion, I will take this as feature request and forward it to our R&D team for further investigation. Hopefully, they will conduct a thorough review and pass it on to our development team for future implementation.
Best regards!
Ruman Ahmed.Hello @jchristopherb,
Thank you for sharing the detailed information. Regarding the conflict, could you please try using another snippets plugin, such as Code Snippets, instead of FluentSnippets, to check if the issue also occurs there?
Additionally, please contact the Bricks support team, as they might have applied certain restrictions to the version 2.x that prevent snippets from running. As these works as previous version. Once we receive confirmation from Bricks about the root cause, we’ll definitely work on a fix if it’s required from our end. I hope this helps clarify the matter.
Best regards!
Ruman Ahmed.Hello @smhsmh,
Thank you for sharing the detailed information. Regarding the issue you’re experiencing, it might be occurring due to a specific configuration. You can investigate it further by following the steps outlined below:
- Temporarily disable all snippets, then re-enable them one by one.
- Check for
admin_enqueue_scriptshooks inside your snippets, make sure they target specific screens usingget_current_screen()rather than running globally. - Wrap outputs in proper hooks, not direct echoes.
- If all snippets are clean, test FluentSnippets on a clean site (with only Burst or SolidWP). If the issue persists, then please contact with the Burst or SolidWP support to get know more information about the issue.
If that’s the case, I’d suggest:
- Enable WP_DEBUG and WP_DEBUG_LOG, reload the dashboard, and check
/wp-content/debug.logfor any FluentSnippets-related warnings. If found, please share these with us. So that we can take a deeper look into it.
Please let me know if you have any further questions or if there’s anything else I can assist you with.
Best regards!
Ruman Ahmed.Hello @follaky,
Thank you for sharing the detailed information and for building this converter tool. If you’d like, you can publish it on ww.wp.xz.cn so that anyone who needs this type of converter can easily use it.
We truly appreciate your efforts on this matter.
Best regards!
Ruman Ahmed.Hello @flowdee,
Thank you for sharing the detailed information. If possible, could you please share your snippet code with us? That way, I can take a closer look at it and provide you with further assistance.
Best regards!
Ruman Ahmed.Hello @mdc2957,
Thank you for sharing the detailed information. Currently, you can only import snippets that were exported from FluentSnippets, not from any other snippet plugins. That’s why your snippet isn’t working. I hope this clarifies the matter.
Best regards!
Ruman Ahmed.Hello @mdrahul92,
Thank you for sharing the detailed information. The issue you are experiencing is occurring due to caching, which prevents the table view stats from updating. To resolve this issue, please follow the steps outlined below:
Clear Cache: Could you please clear your website’s cache, as well as your browser’s cache, to ensure there’s no cached version of the site interfering? Also, please check if the server-side cache has been enabled for your websites.
Hopefully, this might help you in this matter.
Best regards!
Ruman Ahmed.