Archives: Replies

Hello, i use CSS for now, and will wait for update. If you let me know, then, would be great.

Thank you a lot.

Regards.

Lukas

Thank you for the speedy resolution Ashan. Have another issue but will open a new ticket as unrealted to this. Thanks again.

Yes. Thanks so much!

Here you have the sftp:  (not ftp)

Connection address: meizelf.tempurl.host
Port number:22

user: eventonhelp
pw: aground.hypnotism.quail

I installed the eventON 4.9.8 beta on your staging site but still getting that error. Time is also incorrect when downloading CSV in event edit page.

So yes would really appreciate you can share FTP in here. This ticket is private.

Hello Jacy, I am terribly sorry. It indeed is an available option in RSVP addon as part of actionUser integration. I overlooked it.

Ok so it works fine on our end with repeat RSVPs. But I can clearly see in your website the 1st instance of the repeat is showing incorrect times. 

Is it possible to get FTP access to the staging site to see why that is only happening in your website?

Greg, my friend. in your original code you shared, you have commented out the label value and that should work. Be sure to copy the latest ticket_confirmation_email template over. 

If you look at the code, the label is only shown if the value is passed. 🙂

Yes thank you for letting us know of this redirect. we are working on getting this fixed. We are hoping to get a new version out early next week 🙂 Much appreciate your patience my friend!

Sanjeed, We have processed your refund and the subcription has also been updated to reflect this. Thank you my friend!

I want to reiterate my appreciation for your support efforts in helping resolve my RSVP email issues. While we eventually identified the root cause (server/email configuration), I wanted to share some observations that might streamline future troubleshooting for users like me—especially those without technical expertise.

During our ticket exchanges, certain critical steps (like creating a domain email or configuring SMTP) were mentioned, but their *direct relevance to the issue wasn’t fully clear*. This led to a “let’s try this” approach rather than a structured, step-by-step diagnosis. For example:
– It wasn’t immediately clear that not having wordpress@mydomain.com would trigger spam filters, or that using Gmail SMTP could cause authentication failures without explicit hosting-side settings.
– A quick checklist (e.g., “Have you verified these 3 server/email prerequisites?”) could help agents and users isolate the problem faster.

What made the difference was my hosting provider’s support. They:
1. Treated it as a step-by-step process (no jumping between steps or backtracking).
2. Made real-time adjustments (e.g., fixing settings on their end while guiding me to test).
3. Avoided assumptions (they didn’t blame the plugin or dismiss it as a “third-party issue”).

This wasn’t just about urgency—it was about clarity and collaboration. I’m sharing this not as criticism, but as a way to highlight how proactive, linear guidance (even in documentation) could reduce resolution time for users who may not know where to start.

Suggested Improvements:
– Add a pre-troubleshooting checklist (e.g., “Before contacting support, ensure you’ve: (1) Set up a domain email, (2) Configured SMTP, etc.”).
– Include hosting-specific examples (e.g., “Common SMTP settings for GoDaddy/SiteGround”).
– Note how missing emails (like wordpress@domain.com) affect deliverability.

Again, thank you for your patience and assistance. I hope this feedback helps refine your process for future users!