Fahad Mukhtar
Forum Replies Created
-
I Updated the Password. Thanks
also want to confirm something about the recurring feature. The plugin only repeats events using fixed day intervals, so it can’t generate correct dates for patterns like “3rd Wednesday of every month.”
For example, the 3rd Wednesdays in 2026 are: Jan 21, Feb 18, Mar 18, Apr 15, May 20, Jun 17. The plugin doesn’t calculate these correctly.
Does your plugin support “nth weekday” rules (like 1st Monday, 2nd Tuesday, 3rd Wednesday)? Or is this feature planned in an update?
Please let me know.
Here’s the
https://events.icabaworldnetwork.com/wp-admin
Username: faadm_@outlook.com
Password: E9@ni25da#faadm
Sure I will Share Shortly. Meanwhile I also want to confirm something about the recurring feature. The plugin only repeats events using fixed day intervals, so it can’t generate correct dates for patterns like “3rd Wednesday of every month.”
For example, the 3rd Wednesdays in 2026 are: Jan 21, Feb 18, Mar 18, Apr 15, May 20, Jun 17. The plugin doesn’t calculate these correctly.
Does your plugin support “nth weekday” rules (like 1st Monday, 2nd Tuesday, 3rd Wednesday)? Or is this feature planned in an update?
Please let me know.

Here is the link…
Forum: Plugins
In reply to: [Event Booking Manager for WooCommerce] Events Expired before Start TimeI’m checking an issue where events are showing as expired before the scheduled start time. The event times themselves are correct, and the website timezone is already set to New York (EST) in the general settings.
Before assuming this is a configuration problem on our end, I want to confirm whether this behavior could be caused by anything inside the plugin. For example:
• Does the plugin use a separate internal timezone or metadata that overrides the WordPress timezone?
• Can old or duplicated events carry outdated expiration metadata that makes them expire early?
• Is there any known bug where events show “expired” even when the start time is still in the future?
I’ve already tested clearing cache and reviewing server time. I’m now creating a fresh test event to isolate the issue, but I’d like your guidance to confirm if this is a known behavior or if there is something specific we should adjust inside the plugin settings.