Parsing form variables and data from email bodies to fill out ticket details automatically.: Page 2

Parsing form variables and data from email bodies to fill out ticket details automatically.

ScientistGuy

I do, give me a little bit to get back to my computer. My guess is it's something to do with the email body itself not being plain text maybe. The email is a list format, field=variable, like First Name = Generic Person Name, on different lines. I can't seem to find a line break and it is saving the whole string after the equals sign. A Regex example I've tried is something like fname=(+) from memory, I'm on phone but will give accurate assessment when I get back to computer.

Note, I am not well versed in Regex so it is good chance just me having won't capture syntax. But I tested it separately in eclipse and it worked perfectly so I dunno.

Grizly

Explained: https://regexper.com/#fname%3D(%5B%5E%3D%5Cr%5Cn%5D%2B)%20

You're better off starting simple, like: fname=(.+)

But you'd have to change the plugin to work with capture groups.

https://github.com/Micke1101/OSTicket-plugin-Emailform/blob/9421e19c3a92c41b61a1fa10d9dd18a88bcdf43d/class.EmailformPlugin.php#L62

Change the $match to $match

Micke1101

Try the following pattern instead: (?<=fname=).*

ScientistGuy

I will give that one a whirl too. There's some weird stuff going on and I'm not exactly sure what it is. with the regex fname=(+) it finds the eol, however for lines like fname=some dudes name, it saves the whole string as fname=some dudes name, instead of just some dudes name. I have tried all indexes of the array, they are all the same. Get's weirder when its a line like phone=1111111111 using phone=(+) it captures only 1111111111 and not phone=1111111111. So still working through it ha

ScientistGuy

Update:I found the issue and it has been corrected, it wasn't in the plugin but my own momentary stupidity. The plugin works near perfectly. The only issue with it I have is being able to pass a summary text from the email into the thread, instead of having the email body in the ticket thread. I know what needs to happen, the trick will be finding a way to pass whats extracted from the email into $vars. As of yet I have not found a way to cleanly do this. Any suggestions?

ScientistGuy

I have been testing this plugin for a week or so now and have really found it helpful. I have however found a few issues that may need to be addressed. One appears to be a bug and the other is more with functionality extension. Not sure if its a bug or what but it is very strange. I have 2 fields that used to work perfectly like everything else, however recently when I was attempting to change regex expressions to a different form, these two fields now will no longer save. Whenever I put an expression in, click save it comes up and shows everything saved properly. But when I reload the page or go to a different page and go back the fields are empty again. I don't really have an explanation for this. I have tried deleting the fields and remaking them but the same thing occurs. Another thing is that section breaks do not appear on the ticket. I do not know if this is something with the plugin or with a custom form. Other the other forms I have used section everything out as it's supposed to but the custom forms seem to ignore section breaks.The last thing is the email body itself. It does not appear that the string has been decoded. The plugin works perfectly if the email is plain text, but if it isn't I think it breaks my regex.Previously I used very simple regex and emails to test and refine the plugin(using email lists styled with field=variable and regex of field=(+) and it worked perfectly). I noticed the list must be in perfect order with the form fields for it to find matches. I think this can be corrected using preg_match_all instead of preg_match, though I haven't messed with that yet. The email format however seems to break my new email list and regex. This is the form that the plugin in production will have:Field name: \n \t variable answerFirst Name: John DoeI have tested the regex outside of osticket and it works perfectly on field/end of line/tab/variable. However it does not work parsing an email in osticket, even if email is plain text before it is sent. I will continue to work on this but if anyone has any thoughts/insight/ideas that would be Great.

ScientistGuy

Edit:

First Name:

John

Last Name:

Doe

mfelber

Grizly

It's because of the dynamic plugin config.. that never worked for me. Attempting to change a plugin's fields config in any dynamic fashion resulted in config corruption for the plugin. Not sure why. Probably should report it as a bug to osTicket, however I'm not sure if it is a bug, or just an assumption that we will use a static config for a plugin.You might get away with it by saving the config form twice.. however it's not guaranteed..

ScientistGuy

I believe deleting it and resetting everything anew will fix it, I will try to just not edit it too much which shouldn't be a problem once all kinks are worked out and moved to prod. Note saving twice appears to have no effect.

SteRinaldi

Hello everybody
I'm interested in @Micke1101 plugin, but I cannot install it. How can I do it?
I tried to copy all 3 files in /include folder and osTicket doesn't start any more.
Thank you for your help

ntozier

SteRinaldi

Doesn't look like it has been updated in 4 years.
https://github.com/Micke1101/OSTicket-plugin-Emailform

Chances are it will not work for a contemporary version.

« Previous Page