Bage

I am extremely sorry, the issue was not the plugin. It was Gravity forms preventing external scripts from running in the form. I have to disable it in the GF settings. Now everything works great.

Actually when I removed the connection to the list and reconnected it, all the custom fields automatically appeared.

Thank you for the wonderful plugin.

Also do you have a demo of the PRO plugin, please?

Thank you.

It turns out I just have to add the “display” parameter to the [katex] shortcode. It works perfectly.

Thank you again.

I just feel dumb. It is right there in the search form settings.

Thank you for the awesome plugin.

Hello,

Thank you for the reply. But the issue was on my side. I should have reported it earlier.

In one page template, which I have used with the page builder instead of the_content(), I have used ‘echo get_the_content()’ to prevent other plugins from inserting anything after content. Now I have changed it back and everything works perfectly now.

Thanks,
Baage.

Have the exact same issue. Is there any fixes out there already?

You will be able to just drag and drop.

Thank you.

I found out the validation in the form breaks the continue button. Since the fields are empty in the next page, it returns an error and the continue button doesn’t work as expected.

Thanks.

I have the same issue too.. Is there any quick fix please?

Here are some more information,

I have a custom single-ticket.php in my theme. When I use the the_content() I only see the form with error message that i not able to view the ticket. and it displays the awesome-support login form.

When I use the wpas_get_template( 'details' ); instead of the_content(), it also displays the replies too. Only hides the ticket content and displays a login form there.

I was actually asking to list the Ticket ID on the “My Ticekets” page. Not in the WordPress Dashboard.

Thanks,
Bage.

Awesome. Thank you.

Just to clarify, I am able to get the total number of tickets by a user, but not separately by “closed” or “awaiting reply.”

Thanks again.