Md Mahbub Morshed Chowdhury
Forum Replies Created
-
Hi there,
Thank you so much for the thoughtful 5-star review.
We truly appreciate you sharing your experience while evaluating Eventin as an alternative to The Events Calendar. You’ve described the ecosystem perfectly.
We’re really glad our team could assist you throughout the evaluation process and address every concern you raised. Knowing that this gave you the confidence to migrate to Eventin means a lot to us.
Our goal is to provide a stable, feature-rich WordPress events plugin at a fair, without compromising on support. If and when challenges arise, we’ll be right there to help.
Welcome to Eventin, and thank you for trusting us with your site.
If you need anything during migration or beyond, just reach out, we’ve got your back.Best Regards,
M MahbubHi @agenceamar,
Thank you so much for your kind words and for taking the time to share your experience with WPCafe.
We’re truly happy to hear that our team was able to quickly resolve the booking form issues and deliver an update without delay. Providing fast, reliable support is a core part of what we aim to deliver with WPCafe.
It’s also great to know that you appreciate the modern, user-friendly interface and overall design. We work hard to ensure WPCafe remains a powerful yet easy-to-use WordPress restaurant booking and food ordering solution, without the complexity found in many other plugins.
Your recommendation means a lot to us and motivates our team to keep improving both the product and the support experience.
Thanks again for trusting WPCafe, we’re always here if you need anything!
Warm regards,
M MahbubHi @djsaber,
Thank you for being direct with us. We understand your frustration, and you’re right to be upset, the experience you’re describing is not acceptable, and we’re genuinely sorry for that.
Regarding the “Invalid Date” issue:
We just released a fixed version, but my bad I didn’t give the direction how to fix. We should not have say it like that. At the moment, the only available workaround is unfortunately manual:- Open the affected event
- Clear (remove) the “Invalid Date” field https://prnt.sc/ApTAwiqUUlyj
- Re-set the event date and save
We fully acknowledge this is a tedious and frustrating workaround. We are really sorry for that.
About the schedule feature:
Your criticism is fair. Disabling a feature without clear communication or an immediate alternative is not a good experience. We hear you. The schedule feature will be brought back, and we are currently working on stabilizing it properly before re-introducing it. We ask for a bit more time to do this the right way.We’re truly sorry for the frustration this has caused and for the trust it’s impacted. While the rating reflects your experience and we respect that, feedback like yours is important, it helps us identify where we failed and where we must do better.
Thank you for taking the time to share this so candidly. We appreciate it, and we’re committed to improving Eventin so it earns better feedback going forward.
Best regards,
M MahbubHi@finomeno,
Thank you for reaching out and for the detailed explanation, we really appreciate it.
Regarding the translation/namespace issue in the ticket purchasing flow:
We are currently checking this with our development team. The strings you mentioned (Ticket Price, Quantity, Get Tickets, etc.) are designed to be translatable. We’ve successfully translated these strings using the Loco Translate plugin. However, we’ll need to investigate this specifically with WPML to ensure proper compatibility. Once we have an update from our dev team, we’ll get back to you.As for your second question about the event title heading:
We now have a template creation option, which allows you to control the structure easily. The default Event Title widget is already set to H1 on single event pages, so you can manage this directly from the template without any extra customization.And for checking your site, please check our pinned post and reach out to us more, or visit our landing page and reach out to us. We will deeply check your issue.
Thank you for your patience and cooperation.
Best regards,
M MahbubHello @djsaber,
Thank you for taking the time to share such detailed feedback, we truly understand how frustrating this experience has been for you, and we’re really sorry for the inconvenience caused.
We’d like to let you know that the date-related issue has already been fixed on our end. Please try updating your event once, and you should see improvements. Additionally, we’re preparing a new version release today or tomorrow, where all remaining date-related issues will be fully resolved.
Regarding the layout changes, our intention was to give the system a fresh, improved experience and more flexibility going forward. That said, we completely understand your concern about the Global Schedule feature. For customers like you, this feature is genuinely important, and we sincerely apologize for the inconvenience caused by its removal.
We’ve already shared your feedback with our developers, author team, and product owner, specifically regarding bringing back the option to select and apply a global schedule per event. We’re hopeful to release an update soon where this functionality will be available again.
Your feedback truly helps us improve, and we appreciate your patience and honesty. Once these improvements are live, we’d love the opportunity to reconnect with you, and hopefully earn back your trust and update the rating from 2 stars to 5 stars.
Thank you again for being with us, and we’re really sorry for the trouble you faced.
Warm regards,
M MahbubHi there,
Thank you so much for your amazing 5-star review and for sharing your experience with WPCafe it truly means a lot to us!
We’re really glad to hear that the Product Addons issue and that WPCafe is working perfectly for your restaurant website. Your feedback about real-world restaurant use cases is incredibly valuable, and we’ve already shared it with our development team to help us continue improving WPCafe for WooCommerce-based food and restaurant websites.
Your kind words about our team motivate us to keep delivering reliable features, smooth performance, and top-notch customer support. If you ever need assistance or have more ideas to share, we’re always here to help.
Thanks again for trusting WPCafe and being part of our growing community!
Warm regards,
M MahbubHi @rnproject,
Oh, that’s great!
We truly appreciate the level of research, effort, and dedication you’ve put into identifying this issue. Your detailed analysis and clear reproduction steps are incredibly helpful, and we genuinely love seeing this kind of contribution toward improving Eventin.
Thank you so much for taking the time to dig deep into the root cause and even proposing a practical workaround and a potential core fix. That’s awesome.
We’re sitting with our dev team tomorrow, and we’ll thoroughly review this issue together. We’ll discuss the best possible approach, including your suggested solution and the overall flow you’ve outlined. Since you’ve already explained the reproduction steps so clearly, we’re confident this will help us address the issue very soon.
If we need any additional information, logs, or testing support, we’ll definitely reach out to you.
Thanks again for your valuable input and support, it truly means a lot to us.
Best regards,
M MahbubHi @agenceamar,
You’re absolutely right, and we sincerely apologize for the earlier confusion. WPCafe seat capacity works on an hourly basis, not as a full-day limit. For example, if you set 100 guests per hour and one time slot is booked with 39 guests, that specific hour should show 61 remaining seats, while other time slots should still show 100.
However, in your case on January 28, the system is showing 61 remaining seats across all hourly slots, which is not expected behavior. We tested this scenario on our end and it’s working correctly, so the behavior on your site appears abnormal.
As a quick check, could you please try changing your date format to
MM-DD-YYYYand see if the issue persists? This will help us rule out any date-format-related conflicts.It’s currently midnight on our end, but please rest assured, we’ll review this thoroughly and get back to you as soon as possible with more findings.
Thanks a lot for your patience and for pointing this out so clearly.
Best regards,
M MahbubHi @devontecsys,
Thank you for reporting this issue and for clearly outlining the steps, it’s very helpful.
We’ve checked the Table QR functionality on our end using the latest WPCafe Pro version (v3.0.4), and the QR-based table ordering itself is working correctly. You can see our test result here:
https://prnt.sc/iSTXoBkAvM-6However, we did notice that on the checkout page, the table information (table ID/name) is not visibly displayed, even though the table is correctly detected from the QR code. This aligns with what you’re experiencing.
We’re currently discussing this behavior with our development team. If it’s feasible to improve or fully fix how the table information is handled/displayed during checkout and order creation, we’ll make sure to address it and include the fix in an upcoming release as soon as possible.
In the meantime, if you notice any other concerns or behavior, please don’t hesitate to let us know. Your feedback helps us improve WPCafe further.
Thanks again for your patience and cooperation.
Best regards,
M MahbubHi @agenceamar,
Thank you for the detailed explanation and for sharing the test URL, it really helps.
We’d like to clarify one important point regarding seat capacity behavior in WPCafe. In WPCafe, the seat/guest capacity (for example, 100 guests) is calculated as a per-day total capacity, not based on individual time slots.
That means if bookings are made at any time during the day, the booked seats are deducted from the total daily capacity, which is why on the 28th you’re seeing 61 available seats (100 − 35 − 4), regardless of the selected time.So, this behavior is currently expected and works based on daily guest limits, not time-slot-wise limits.
Regarding the other issues you mentioned (booking time not appearing, today’s time slots missing, and the end time / “until then” error), we’ll need to investigate these more deeply from your site environment and settings.
For a more detailed discussion and hands-on checking, we kindly request you to check our landing page and reach out to us more. That will allow our team to properly review your setup and assist you more effectively.
We’re here to help and will do our best to resolve the remaining issues once we can look into them closely.
Looking forward to your response.
Best regards,
M MahbubHi@stelakoulas,
Thanks for reaching out.
In WPCafe, delivery charges are handled through WooCommerce, so you can easily set up a delivery fee directly from WooCommerce settings. You can quickly add a flat delivery charge (like 6€ per order) from WooCommerce, In example: https://prnt.sc/RAoM4Pj5l27o, or use any WooCommerce-supported shipping plugin if you need more advanced or conditional delivery rules.
If you need any help setting this up from WooCommerce, just let us know, we’ll be happy to guide you.
Best regards,
M Mahbub
Hi @swinggraphics,
We apologize for the frustration this has caused. We completely understand your concern and appreciate you bringing it to our attention.
As a temporary workaround, you can prevent the admin email from being exposed by adding the following code to your active theme’s functions.php file:
add_filter(
'etn_locale_vars',
function ( $data ) {
$data['admin_email'] = 'hidden';
return $data;
},99
);
This will remove the admin email from the public script output immediately.
We’ve already fixed the issue, and this will be handled directly inside Eventin in our next release, so no manual changes will be needed going forward.
If you have any questions or need help applying this, feel free to reach out. Our team will be happy to assist.
Thanks for your patience and understanding.
Best Regards,
M MahbubHi @agenceamar,
We sincerely apologize for the inconvenience this has caused you.
Regarding the Email Variables: We have tested the latest version of WPCafe in our local environment. While the booking time appears correctly https://prnt.sc/2KnglTL2btC6, we confirmed that the status is not displaying. We have already forwarded this issue to our development team for a fix.
Regarding Seat Capacity: If you set a total capacity of 20 with slots from 8 AM to 2 PM, a booking made for the 8 AM–9 AM slot should only block that specific time. The subsequent slots (9 AM, 10 AM, etc.) should remain available for other users. If your site is blocking the entire day instead of just the slot, then please reach us more via landing page so that we can deeply check your environement.
Regarding the ‘Until Then’ Issue: The error ‘the end time must be after the start time’ indicates that the end time must be later than the start time. For example, if the start time is 8:00 AM, the end time must be 8:01 AM or later but it can’t be 12/1/2… AM. Please double-check your time selection.
I hope you get it.Thanks for being with us.
Best Regards,
M Mahbub
Hi @tortip,
Thank you so much for your 5-star review and kind words!
We’re really happy to hear that our Eventin team could quickly identify and resolve the issue after the update.Providing fast, reliable, and hands-on support is a top priority for us, especially when it comes to keeping your WordPress event management and ticketing system running smoothly. We’re glad we could fix everything within 24 hours.
Thanks again for trusting Eventin for your events. If you ever need help with event setup, tickets, or future updates, we’re always here to help!
Best Regards,
M Mahbub
Hi @mattyice808,
We have checked it on our end and its working and counting exactly: https://prnt.sc/HaWOn6kLNaBn Please try to delete all and again setup your FAQ I hope it will work fine. Please let us know your update.
BestM Mahbub