sotirissmix

Glad to hear it. Marking this topic as solved.

I solved my problem, though in a very cheap way, and I do not recommend it, since it exposes the url to the uploads directory.

In the file awesome-support/includes/file-uploader/class-file-uploader.php, on line 466 where it says
<li><a href="<?php echo $link; ?>" target="_blank"><?php echo $name; ?></a> <?php echo $filesize; ?></li>

change $link to $attachment[‘url’]

@demaiomassimo89 please try it and see if it works in your case so I can mark the topic as resolved.

Would the changes in 3.3 also affect the functionality of the custom fields? I mean, is it gonna be a pain to configure?

Might I also note, the attachments don’t work AFTER migration. The attachments still load fine on the website that resides in the original server (before the migration). Any idea what that might be? The URL of the website changed as well after migration.

@julien Liabeuf any news on what I should do for this problem?

No, I’m not using iThemes Security. Or any kind of security.
Attachments worked until I enabled “Agents can see all tickets”.
Now, supervisors, managers or agents (assigned or not) can’t access attachments.

That would certainly be great. Though I was looking for what to do right now so I can make it possible. Is there any piece of code I could alter or should I just wait for an update?

Yes but that has the effect of even agents being able to see tickets not assigned to them.

I want supervisors and managers to see all tickets (so they can assign and manage them), and agents to see only tickets assigned to them.

For now I’m using the same variables and values to display them correctly.

Might I also suggest, since there is functionality for the html5 pattern validation, another field named ‘pattern_error_message’ so we can specify the error message when the field doesn’t validate using the html5 pattern.

If I recall correctly, the function for this in javascript is
this.setCustomValidity(errorMessage)

Please let me know if I should post this suggestion somewhere else.

The submission problem has been solved, it was just bad coding on my part.

The problem remains with variable names being output for the options instead of the values.

Solving my first problem seems to have produced another one.
For anyone looking for the solution, my first problem is solved by editing the submission.php file inside themes folder of the awesome-support plugin folder.

But now I cannot submit my form. I’ve made the (default) subject field into a <select> field, and my form looks correct and exactly how I want it to look, but clicking submit just returns me to the submission form.

I’m using greek characters with UTF-8 encoding to fill out the form options, if that helps.

Any idea why the form doesn’t submit?

Alright. Thank you very much.

Thanks for the reply. Can I add more than 3 ticket status or will the key->value addition break something?