Ahsan Chowdhury
Forum Replies Created
-
Hello @halyxer ,
Thank you for the detailed information regarding the timezone configuration and the verification flow. We truly appreciate the effort you put into outlining the environment settings.
We have carefully reviewed the signup verification flow again and attempted to reproduce the issue in our testing environment. However, we were not able to replicate the immediate-expiry behavior on our end.
Since everything appears correctly aligned in your setup (WP, PHP, and DB all in JST), this may be something environment-specific. To properly investigate this further, we’ll need to debug it directly from your installation.
Could you please open a support ticket at the WPManageNinja portal?
Thank you
Hello @halyxer ,
Thank you for reporting this.
We have tested the email verification process on our end, but we’re not able to reproduce the issue. The verification code is working as expected and not expiring immediately.
To help us investigate further, could you please confirm which timezone your WordPress site is set to (Settings → General → Timezone)? Also, let us know your server timezone if possible. A mismatch between these could potentially cause the
valid_tilltimestamp to be considered expired right away.Once we have this information, we’ll check more thoroughly.
Hello @mediblereview ,
Thank you for bringing this to our attention. I have tested and a similar result was found. I have notified our dev team. Hopefully, it will be fixed in the next update.
Thank you
Hello @thuyanhlien ,
Hello,
Thank you for your message.
Fluent Support does not have a dedicated “post widget.” The support form can be added to any post or page using the Shortcode or the Gutenberg block.
At the moment, Fluent Support does not have a built-in feature to automatically assign tickets to the author of the post where the form is placed. Tickets submitted from the shortcode or block are handled based on your default product, inbox, or workflow configuration — not dynamically by the post author.
Thank you
Hello @telesites ,
Thanks for letting us know about this.
At the moment, we’re unable to reproduce the issue on our end. To help us investigate further, could you please share the complete error message, along with the exact file path and any additional details shown by Defender?
Alternatively, you’re welcome to open a support ticket at the WPManageNinja support portal and share the full context there. Our team will be happy to take a closer look and assist you promptly.
Thank you for your cooperation.
Hello @cagdasdag,
I have tested this on our end, and everything appears to be displaying correctly as expected. To help us investigate further, could you please let us know which theme you are currently using?
Once we have that information, we can check whether this issue might be theme-specific or if it could be related to your particular site setup. Providing any additional details about your configuration or any customizations you have applied would also be very helpful.
Thank you for your cooperation, and we look forward to resolving this for you.
Hello @adamcze1 ,
Thank you so much for your kind review! I truly appreciate your patience while we worked through the issue together. I’m glad we could identify the cause and get everything running smoothly for you.
If you ever need help again or have any questions, feel free to reach out anytime. We’re always here to help!
Thanks again for choosing Fluent Support.
Hello @himanshusharma20 ,
Thank you for reaching out and for sharing the details of what you’re trying to achieve.
At the moment, FluentSupport does not have a built-in option to filter or block outgoing emails based on the customer’s email address or custom conditions. The hook you found is part of our internal notification flow, but it isn’t currently extendable in a way that would allow overriding or preventing the email from being sent.
However, your requirement is valid, and we truly appreciate you bringing this up. I’ve noted this as a feature request and will share it with our product team so we can consider adding more flexible email-filtering options in a future update.
Thank you!
Hello again,
We’ve taken this matter seriously and have already released an update on November 21st. The issue has been resolved in that version. If you haven’t updated the plugin yet, please do so to apply the fix.
Thank you
Hello @fredawd ,
Thank you for confirming you are using the Google Drive.
We have carefully reviewed the behavior you reported and were able to replicate it during our testing.
Issue Summary: When the Google Drive integration is enabled, files are uploaded to your Google Drive successfully. However, when attempting to view an attachment from within WordPress, it redirects to the WordPress admin page instead of opening the file.
We are aware of this issue and are actively working on a solution. We will keep you updated on the progress and notify you as soon as a fix is available.
Currently, you are requested to use the Default WordPress Storage.
Thank you
Hello @fredawd ,
Thanks for reporting this. I’ve tested the attachment functionality on our end with version 1.10.3, and everything appears to be working as expected.
To help us investigate further, could you please share a bit more context?
When you mentioned “links to attachments inside tickets”, were you referring to:
- Actual ticket attachments?
or - A link you added inside the ticket content?
If it’s a link inside the ticket, please let us know how you added it (e.g., manually pasted URL, uploaded file, etc.).
Additionally, are you using any caching or security plugins on your site?
This information will help us identify what might be causing the redirect in your setup.
Thank you!
Hello @ghulamjafar2 ,
We have released an update Yesterday!
The issue has been fixed on this update. Please update the plugin. Hopefully, everything will work fine.
Thank you
Hello @ghulamjafar2 ,
Thank you for bringing this to our attention.
However, the inclusion of
_wpnoncein the ticket URL, which causes the “Security check failed. Please try again.” error, is a bug after the last update. Our development team has already fixed this issue on our end.The fix will be included in an upcoming update, which will be released soon. We appreciate your patience and understanding.
Thank you
Hello @ricsca2 ,
Yes, this is possible using Email Piping in Fluent Support.
If you configure email piping on your support email address, any user reply sent directly from their email to the ticket notification will automatically be added as a response inside the ticket thread.
Here is the doc: https://fluentsupport.com/docs/email-piping-email-based-support-ticket/
Thank you
Hello @tobaco ,
I’m sorry to hear that you’re experiencing this issue. I have tested the shortcode on our end, and everything appears to be working correctly. To investigate further, we will need to test it directly on your website environment, as the issue might be related to specific settings, plugins, or configurations on your side.
Could you please open a support ticket through the WPManageNinja Support Portal? This will allow our technical team to securely review the details, replicate the issue, and provide you with the most accurate solution.
Thank you
- Actual ticket attachments?