1BJK903

The 3.2.2 update didn’t fix the broken button.

It is still not working. Can you fix this please?

Hi Julien..

Where can we translate the “closed” label? I can’t find it in the files.

PS: 3.1.5 didn’t work either. Not via the front-end submit shortcode anyway…

The products issue was fixed indeed, but with the latest update 3.1.6 it is not working anymore…

Have enabled multiple products, assigned a product to a ticket but it doesn’t show it nor on the front-end nor back-end. Hope you can fix this soon again…

Well, you can download it from gist.. it’s a minor function that helps us to add custom fields. It is hosted on your website.

Here you go: https://getawesomesupport.com/documentation/awesome-support/custom-fields/

The problem: if you add the custom fields, it adds them to the back-end, I want to show the fields in the front-end. Is that possible?

I understand, thanks for your answer, but can you give me a hint? I mean, which function do I have to use to show the agents name in that case?

Thanks for the answer. But I want to give them full access to editing etcetera. Isn’t this possible? Cause if I go admin, I have not the permission to add a ticket via front-end, for example. I find that rather odd.

Hmmm… Still not working here. Weird.

Is this fixed? Cause I still see 1 January 1970 when replied to a ticket via the back-end.

PS: if I add a tag for tickets, let’s say I add the tag “preparation”, I get this: ?ticket-tag=preparation

Nothing found with the tag “preparation”. My question: how is this possible?

Same here… getting errors with querying posts.. can’t update plugins, I don’t get it. WTF is happening.

I got this too, when activating the plugin:

The plugin generated 749 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

Looks like it is conflicting with Yoast SEO. Can this be true?

I get a page reload…

PS: I get the following error with 2.0.1: Parse error: syntax error, unexpected ‘private’ (T_PRIVATE) in C:\werkruimte\www\examinate\wp-content\plugins\inline-comments\frontend\class-comments.php on line 152

I can’t see my site anymore.

Yes, I am using the most recent version, downloaded from the WordPress repository. Exactly, that is correct… It does redirect me to the page where I can click on the post to open the comments instead of staying on the page with the comments.

Thanks. I hope your list will be translated to code soon ?? Good plugin btw.

Is this solved in any way?