Ruman Ahmed
Forum Replies Created
-
Hello @nguyentien01634,
Thank you for sharing your experience and feedback, we truly appreciate it.
We understand your concerns regarding the round-robin scheduling and calendar synchronization. For round-robin events, this feature is available, but it does require specific configuration to distribute bookings across team members correctly. It’s possible that the event was set up as a one-on-one meeting instead, which would explain the behavior you experienced. We’d be happy to review your setup and guide you step-by-step to achieve the expected result.
Regarding the calendar sync issues, this is not expected behavior. In most cases, synchronization problems are related to connection permissions or API limitations. If you can share more details (such as the calendar provider and any error messages), we will investigate this thoroughly and help resolve it.
Please feel free to reach out with your configuration details, we’re here to help ensure everything works as expected.
Best regards!
Ruman Ahmed.Hello @furkansenturk,
Thank you for sharing the detailed information.
Regarding Problem 1, the validation is currently applied to the submit button. That’s why when the user clicks the submit button, it prompts them to select a date and time for the booking accordingly.
If you’d like, I can submit this as a feature request to our R&D team for further review and possible future implementation. Please let me know if you’d like me to proceed.
Regarding Problem 2, this is not currently possible in FluentBooking. The system is designed to work with time slots, and events can be created for up to 12 hours in duration rather than full-day bookings. Therefore, selecting a day without a time slot is not supported, and there is no available workaround at the moment.
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 @szymonfortuna,
Thank you for sharing the detailed information.
At the moment, there isn’t a plan to implement this feature. However, I will go ahead and submit it as a feature request to our R&D team for further investigation. They will review it thoroughly and pass it along to our development team for consideration in a future update.
Best regards!
Ruman Ahmed.Hello @akgt,
We’ve tested the same scenario on our end by adding UTF-8 characters (including emojis like 🛒) inside a Fluent Snippet and rendering it on the frontend. The characters display correctly after saving, which indicates that Fluent Snippets is properly preserving UTF-8 encoding in our environment.
Since Fluent Snippets stores snippets as PHP files (in /wp-content/fluent-snippet-storage/), this behavior is likely related to the server or environment configuration rather than the plugin itself.
We recommend checking the following on your setup:
Server default encoding:
Please ensure default_charset is set to UTF-8 in your php.ini
Verify mbstring settings (e.g., mb_internal_encoding)
File system / locale configuration:
Check available locales using locale -a
Make sure a UTF-8 locale (e.g., en_US.UTF-8) is active
File encoding after save:
Open a saved snippet file from /wp-content/fluent-snippet-storage/
Confirm it is saved as UTF-8 (not ISO-8859-1)
Plugin or theme conflicts:
Temporarily disable other plugins or switch to a default theme to rule out interferenceAdditionally, if possible, please share:
A screen recording of the issue
A copy of the snippet file before and after savingThis will help us pinpoint whether the encoding issue occurs during file write or output.
Best regards!
Ruman Ahmed.Hello @heval1,
Thank you for sharing the detailed information, and apologies for the delay in response. We appreciate you documenting all 7 issues.
We’ve shared your report with our development team for deeper review. Also, we’ll evaluate implementing a consistent cross-platform handling strategy.
The additional points you raised, including input validation for $_FILES, sanitization of $_GET parameters, and the leftover debug log, are also noted and will be reviewed as part of this process.
If needed, we may reach out for clarification while validating fixes internally.
Thanks again for taking the time to put this together!
Best regards!
Ruman Ahmed.Hello @jolentes,
<span style=”box-sizing: border-box; margin: 0px; padding: 0px;”>I appreciate your cooperation</span> regarding this matter. However, I will take this as a 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 @jolentes,
Thank you for sharing the detailed information. At the moment, Fluent Booking builds the CalDAV URL using the provided username, and there isn’t a built-in option to use a separate user ID (such as a UUID) for constructing the CalDAV endpoint.
Since your Nextcloud setup relies on LDAP and generates CalDAV URLs based on UUID instead of usernames, 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 @cskasler,
Thank you for sharing the detailed information. Could you please share the link that I have shared earlier? So that I can take a deeper look and provide you with the correct code URL.
Please let me know the update.
Best regards!
Ruman Ahmed.Hello @subwebsites,
Thank you for letting us know. I will submit this as a feature request and forward it to our R&D team for further investigation. Hopefully, they will review it thoroughly and pass it on to our development team for future implementation.
Best regards!
Ruman Ahmed.Hello @subwebsites,
Thank you for sharing the detailed information. Currently, there is no option available to add additional fields to the FluentAuth registration form. At the moment, there is also no workaround that I can suggest for this requirement.
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 @gburwise,
Thank you for sharing the detailed information. Regarding the calendar shortcode, you are correct. The events shortcode works in a very similar way, except that the event ID differs for each individual event.
For the Divi page builder, could you please try embedding the events shortcode and see the result you receive? There should not be any issues, as the shortcode is designed to function properly with standard page builders.
Additionally, you may test the events shortcode using the Gutenberg page builder to compare the results.
Hopefully, this might help you in this matter.
Best regards!
Ruman Ahmed.Hello @ashf,
Thank you for sharing the detailed information. However, 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 @esilverstrike,
Thank you for letting us know. However, 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 @esilverstrike, @gslweb,
Thank you for sharing the detailed information. However, 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 @yoav-drcousensglobal,
Thank you for sharing the detailed information. However, 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.