en0x

Hi Pavan789,

I’m sorry to tell you, that there isn’t an option to attach files at the moment. This will be a feature in an upcoming version i think.

It’s also included in the update from today, so i think it is solved

I just released an update

ah ok, yes this is a good idea, i will ad this to my agenda…

I’m glad you like it! ??

It’s an upcoming feature to rename the optional fields.

Wording on the datepicker

you mean date format?

For these settings i’m planning to add a second backend page.

And GitHub needs a bit to unterstand, but once you got it, it’s just great. There are a lot tutorials you can find.

it’s included, just grab the development version.

Well thats a point, always keep the evil users in mind ??

But why? it isn’t more comfortable or anything else.

I got that errors too. It’s because i implemented a function to automatically update the database, when there are changes within an update. But for that i had to add a knew table in the database first and these changes only apply on installation or reactivation, so when you update from an older version as 1.1 these errors will be shown until you reactivate the plugin.

I also wrote it in the changelog, to reactivate the plugin.

I had some free time, today so i released an update with these things included.:)

I have one other suggestion to go together with recognizing when someone has logged in through WordPress. When a user goes to submit a ticket, the name, email, and optional fields should not appear because the plugin and site should already recognize who the user is.

Well that are good ideas i think, only the optional fields should not diesappear, an upcoming feature will be to rename these fields as you want.

And one more suggestion (relevant whether the user is logged in or not) is that there should be a designated title field. This will make it much easier to locate each ticket.

A title is also a great idea, i’m going to implement that.

But the : is placed outside the translatable string

I put them outside because it is’nt important for the translation, but i can do that. When you are into code, feel free to create a pull request on GitHub, this will simplify my work a lot ??

That’s great! I completely agree with this. In fact, it’s exactly what I am looking for.

That’s cool!

I made a first small update to delete the salutation. I am going to look for the login update the next days.

Hi,
my idea was it, to create a Ticket System completly for the front-end, because maybe you want people to handle the tickets, who should not get access to the back-end of wordpress. Therefore i made a login independent from wordpress and to create these users you use the back-end ‘User Administration’ page. The login is also needed to track which user works on which ticket. But you are right, it is not that comfortable to login again, whenyou are already logged in into wordpress. Maybe i can include, that you can log in with both, wordpress and the ticket system user.

The salutation was for a mail notification about your ticket status, like who works on it and is it pending and thinks like this, but it’s not completed yet, so i should remove it until this function is ready.

Does thinks get a little bit clear and are there other questions?