juin
09
WATS going on…
If you speak french, you may prefer to read the french version of this note.
What is WATS? WATS is a wordpress plugin I have just written with my small fingers. WATS stands for « Wordpress Advanced Ticket System ». It allows transformation of Wordpress into a CRM system thanks to the addition of a ticket submission module into the administration panelas well as associated pages creation on the frontend.
As of today, there is no plugin like this one for Wordpress. There has been an attempt for Wordpress mu but it has never been propagated into the single blog version. WATS is therefore an original plugin.
In Release 1.0, WATS is absolutely free. The only requirement is to keep the backlink automatically added by WATS in the footer of your site. This is a mean to promote this plugin and recognize my work. If you disagree with this, just don’t install the plugin.
Ticket system features (release 1.0) :
1/ Statistics :
In the Wordpress admin panel, WATS adds a dashboard widget containing few stats about the number of tickets.
2/ Options :
In the Wordpress admin panel, WATS adds a page for the options where the admin can set the ticket numbering, define a guest user who will be allowed to submit ticket, add, modify or delete statuses, priorities and types of tickets and define the categories where tickets can be submitted.
3/ Ticket creation and edition :
In the admin panel, WATS adds a menuitem for the edition and the submission of tickets. These are quite similar to the post ones. Only registered users who can edit posts and the guest user can submit new tickets. Only registered users who can edit posts can edit tickets.
Guest user is an account dedicated to the ticket creation. Thanks to this, you don’ t need to ask every visitor to register to be able to submit tickets. They can just use the guest user account. The guest user account must have a minimum level of contributor.
As of release 1.0.43, you can also submit tickets through the frontend thanks to the frontend submission form feature. To do this, just create a post or a page with the following tag : [WATS_TICKET_SUBMIT_FORM]. This will create the submission form automatically on this page. The form works with Ajax so it won’t reload once the ticket is submitted. You have several options to set the form access, ticket publication status and default author for tickets.
As of release 1.0.44, users can now directly submit tickets through email! This feature allows them to submit a ticket without connecting to the site. The ticket is directly inserted into the database pending validation.
4/ Tickets display :
In the frontend, WATS uses custom templates to display the ticket. If you haven’t created a custom template in your theme, WATS uses default ones.
In order to customize your theme for WATS, you can copy and edit singe-ticket.php and comments-ticket.php from the theme subdirectory (within the plugin directory) to your theme directory.
Ticket display is just like the single post display with few modifications (number, priority, status and type).
5/ Ticket update and follow-up :
Ticket follow-up is performed within the frontend by just adding comments and updating the custom fields : status, priority and type of ticket.
6/ Tickets listing table (available starting 1.0.4) :
It is possible to automatically include within a post a table containing tickets listing for all categories or post category associated to the created post. To achieve this, just include one of those two tags within a post :
- [WATS_TICKET_LIST 0] : table containing all tickets for all categories
- [WATS_TICKET_LIST 1] : table containing all tickets for the post category
Starting release 1.0.16, there is an ajax filter available. It allows the user to filter the table content dynamically based on the tickets priorities, statuses, types and owners.
7/ Tickets visibility filtering (available starting 1.0.12) :
Available starting 1.0.12, there is an admin pannel option that will allow you to specify who can browse and updates the tickets : everybody, only registered users or only ticket creator and administrators. This strongly enhances security and confidentiality around exchanges with users through tickets.
For instrance, by selecting the value « only the ticket creator and admins », on the frontend, you will have to connect to be able to browse tickets. If you are an admin, you could see and update all the tickets. If you are the ticket creator, you could see and update this ticket (and more generally all the tickets you have created). But if you are just a visitor or another registered user than the ticket creator, you won’t be able to see and update this ticket.
This filter also impacts the tickets listing table.
Download WATS
You can download WATS here.
Install WATS
WATS installation is plug and play! You just need to activate the plugin and then get to the options panel where you can associate the guest user (if you have created one) and the categories where you want to allow ticket submission. WATS has a moderate impact on the database. It doesn’t create any new table. It just adds one entry into the options table and 4 entries into the metas table per ticket.
WATS works fine with Wordpress 2.8. It uses Ajax and Javascript under the admin panel so be sure to turn JS support on under your browser settings.
WATS Localization (release 1.0) :
WATS is available in english and french. If you would like to contribute and translate it into other langages, don’t hesitate to send me the translated PO, they will be integrated.
German added in Release 1.0.23 (thanks to Tobias Kalleder).
Bug and support :
Please submit a ticket! When I would have migrated to 2.8 here 
Changelog :
This page includes the changelog.
Donation :
You appreciate WATS? That’s great! While WATS is free, I already spent hundreds of hours developping it, supporting it and adding new features following user requests. Why don’t you acknowledge my work on WATS by making a donation? This is a way to say « thank you » and motivate me to deliver new features and support.
 | Catégorie : Wats |
 | S'abonner au blog |
| S'abonner au flux des commentaires |
 | Laisser un commentaire |
 | Faire un trackback depuis votre propre site |
 | Partager ce billet avec vos amis par email |
Aucun mot clef pour cet article.
Articles relatifs :
Error with install i get this in All Category
Warning: Invalid argument supplied for foreach() in C:\xampp\htdocs\wordpress\wp-content\plugins\wats\wats-template.php on line 192
I think I know why… Have you been first to the options page first to add at least one category to which you can submit a post?
If you don’t add at least one, then you could get this error. I will add some robustness into the code on that front to prevent this error.
i noticed a bug, when you activate the theme your pages (about,etc) get indexed on your main index, which shoudlnt happen. once you deactivate it they no longer show on your blog index.
Hi Chris,
Thanks for your feedback. I am not sure I fully understand what’s going on. Can you provide me with the url and describe the bug more precisely?
Thanks a lot!
Olivier
i unchecked include tickets on home page with posts, and it fixed it.
Ok great! This was a feature requested and implemented between 1.0 and 1.0.1, I am glad that it helped you.
1) Unable to associate a contributor user.
2) Fatal error: Call to undefined function esc_attr() in \plugins\wats\wats-edit-form-advanced.php on line 31
3) I would want people to have to create a user in order to supply a ticket. (they all have accounts anyways)
4) A templet page to add a ticket and show tickets would be nice.
1&2 : From what I saw on your site, you are running 2.7.1. You must be running 2.8 in order for the plugin to work fine. It isn’t supported on 2.7.1.
3 : That’s natural. Right now, you cannot create tickets without being registered so I think that’s what you are looking for.
4 : What do you mean? There is a page to submit tickets, you should have seen these in the admin panel. There is also a page to display ticket. You can edit this one by copying the template php files from the plugin theme directory to your own theme directory and then customize these according to your needs.
I have been waiting for this a long time and have started development on my own ticketing system. Now I can move on to more essential things.
So you make sure you keep up the good work! If you need any help or donations contact me. or put up a donation button.
@Xmoov : thanks a lot for your kind words, they are much appreciated! I may put a donation button later
found its using a lot of server load, when i try and login its trying to load wats-ticket-new but just times out and wont let me login
You are right, with the guest account, you will directly be redirected to wats-ticket-new in order to enter a new ticket, no other option for the guest account. Now I am a bit surprise by your statment about the server load as this page doesn’t load a lot more data than the new post page…
Are you running php 5?
Hi Olivier,
Thanks for the great plugin.
Maybe my question is stupid…, but I hadn’t find where/how can I see the form for the ticket submission.
I added one of my categories in the settings, but i can’t see anything in that category or inside the posts.
What I’m doing wrong?
Best regards
mmmh, I’m working with 2.7.1 version of wordpress isn’t supported for this version???
I can’t upgrade to 2.8 version of Wordpress…
Any Idea?
The form to submit tickets is under the admin panel. You can access it through the menu added by the plugin.
The plugin doesn’t work fine under 2.7.1. You will get some errors. It is so tightly linked to the core that I had to make a choice between 2.7.1 and 2.8. As I didn’t want to maintain a lot of specificities for the first version, I decided to drop 2.7.1 support.
aha…, ok Olivier maybe I will find another plugin for this. I’ll be find with a simple solution. Maybe you should think to build the plugin in a more flexible way…, in order to maximize your efforts.
Thanks anyway for contribute with your work.
Why don’t you migrate to 2.8? It is a great release with improved performances.
in order to maximize you efforts?
Well
The issue is that WATS reuses some part of wordpress core templates for the ticket submission. 2.8 introduces several functions. In order to add 2.7.1 support, I would have to copy those functions into the plugin or to test if those functions exist before calling these, this would add a lot of complexity to the plugin and therefore increase maintenance… At this point, I prefer to concentrate on new features, I think it is more benefitial for users, isn’t it
Hi!,
When you are using more than 5 plugins, and mantain several blogs that are working perfectly, you don’t want to get in troubles upgrading to a very recent version of Wordpress… and who can tell to you that if you don’t work with compatibility in mind, your plugin will be compatible with the next version of wordpress…
I think Cforms doesn’t have this feature, so your idea is very good (I didn’t see any plugin like your yet), but for me this feature is not very high in my agenda.
I know I’m a little « bastard » with my my critics but just take it in a positive way.
You know I’m right
Dont’ take me serious, we use to have great stuff for free on the net.
Maybe that’s the problem
Saludos desde Madrid
Of course your right, I just couldn’t resist.
Well, you need to understand that Wats isn’t a plugin like others. By saying that, I don’t want to say that it is the best one, certainly not, I just want to highlight the fact that it goes very deep with Wordpress core by reusing some of the pages with few tweaks.
I will see later what can be done as you are not the first one asking for 2.7.1 compatibility. Most of the plugins have been upgraded for 2.8 compatibility so the upgrade shouldn’t cause a lot of problems to you
I’m tweaking wordpress in order to be an advanced CMS and currently needs a few delicated hacks with several plugins, so for me it’s a delicated situation to go to 2.8 and I have more things to do…
Just have a look to the code maybe it’s not so difficult to make it 2.7 compatible, anyway at the first time that I upgrade to 2.8 I’ll check it out your plugin for sure.
Best regards
Ok so I took a look further into the code to try to make it work for 2.7.1…
I had to import few 2.8 functions that aren’t available in 2.7.1. Still I am getting few warnings on the backend as some functions prototypes have evolved between both releases.
For the frontend, I will have to tweak back the query, it will not be really fun
Not sure that I will be able to make it and also to make it clean because I don’t want to make the plugin so heavy to maintain because of these modifications.
Will keep you posted.
as soon as i set the guest account it times out, its set as subscriber, tries to load the ticket new, then i have to rename the plugin directory so i can deactivate it and login again.
this is a fresh 2.8 install with no plugins but WATS
The guest account needs to have « contributor » level at least. With subscriber, you don’t have the minimum level required…
Based on the number of requests I had to make the plugin compatible with earlier releases of WP, I have added it. It wasn’t really easy as I had to bring few WP 2.8 functions within the plugin in order to allow it to be support on earlier releases. I also had to tweak the query differently from 2.8, not easy but did it
As of 1.0.5, 2.7.1 is supported as well. It will be available for download from the wordpress svn tonight. If you face any bug, please report these.
i set an account up name support and set it as contributor, but still times out while trying to login
Have you installed the latest release issued today? Do you run php 5 on your blog? Are there any other plugin running beside Wats?
Great Olivier!,
Now I’m enjoying some holiday days, but as soon as I can I’ll give you my feedback.
Best regards,
Great thanks, I am looking forward to hear from you.
Enjoy your holidays!
I have problem with creating ticket – my Guest user is set to admin and I try to insert new Ticket (« You are not allowed… »). It would be also very helpfull not to require registration and use template form for my users (and not Wordpress administration) to insert new tickets.
What is the level of your guest user? It should be at least contributor.
The insert ticket form is on the admin side for security purposes as you are inserting new tickets (which are posts from a DB point of view) so it is better to require the user to login so that robots don’t come and spam your database with bunch of fake tickets. The guest user is there to avoid the registration, this is a user to be shared between visitors so that they don’t have to register to submit new tickets.
I have user test (Contributor). But I am not allowed…
When I try to login as admin and publish ticket, I am also not allowed…
I understand your reasons for login, thank you for your answer…
Can you please contact me through my contact form and send me the guest user login details to your site?
A very nice Wp-Plugin – thanks for shareing …
Great plugin. I’m having a problem. When a non-administrator logs in, they get encounter a redirect loop. If you send me an email I can send you the site login details to demonstrate.
This is a known issue which was fixed in 1.0.6. I encourage you to upgrade to 1.0.8 which was released two days ago, this should clear the issue
If not, please let me know. You can send me a mail via the contact form.
Screenshots please!
oh yes, please I am really curios what it looks like. Screenshots please.
I have updated this post with some screenshots, hope it will raise interest
I have installed the plugin and set the options. I have a basic question.
So can an unregistered user submit a support ticket from my blog?
How do I include the support ticket form on my blog page?
Yes, an unregistered user can submit a support ticket from your blog. Basically, just create a guest user account, identify it as the guest user in the options and then provide in your frontend.
The support ticket form is part of the backend. This is for security purposes. Only logged in users can submit tickets. But you just need to set a guest account and provide it to your visitors so that they can use it. With this, no robots will be able to spam you with fake tickets.
Using your fabulous plugin at http://postfixmail.com/blog in the questions category. Everything works except when a ticket is clicked on (showing its details)the sidebar navigation/widgets disappears. I love your plugin but want to display the navigation for users when they are viewing tickets.
This is absolutely true! I missed it while developping the plugin because I used the default kubrick template which doesn’t include the sidebar on single post.
So I have modified the single ticket template in 1.0.13 to include the sidebar. It is now available for download
Wow! That’s awesome! I wrote you a killer review http://wordpress.org/support/topic/303973?replies=1. Let me know if I can do anything else for you as this is support I wish every plugin had!
Andrew,
Thanks a lot for your kind words and the killer review!
I don’t commit on « 10 minutes support » however if I am available and I can fix it easily, I always try to do it quickly. Luckily, this was the case for your request as I was at home next to my SVN so I could directly update the WP repository after I have fixed the plugin. As you can imagine, it sometimes takes more than 10 minutes to find a solution and post it but I always do my best in order to maximize user’s experience of my plugin…
If you want to make a donation, don’t hesitate but your kind words already represent a great donation on my mind
Is it normal for the plugin to be making a bunch of custom fields in static pages that has nothing to do with the Plugin with WATS_TICKET_NUMBER, WATS_TICKET_STATUS, WATS_TICKET_PRIORITY and WATS_TICKET_TYPE? and values like 9 and 10s
Or is this conflicting another plugin? I tried del them but then it just re-appears after I update. It only seems to affect the pages I create after I installed WATS and not the pages I created before
I had the same problem but, like you, didn’t know if it was really a problem. I got great support from the author, lets see if her comes through
Eric, Andrew,
I acknowledge the issue. I checked it first time this morning. I am trying to understand the root cause now. Hope I will be in a position to provide an explanation and a fix soon. I will keep you posted.
Good news! I have identified the problem and found a solution for it. There was a problem with a hook being called while it shouldn’t. I have moved it to another location where it would be hit only when it is supposed to…
1.0.14 contains the fix and is on its way to the repository
If you have any problem, just let me know.
Excellent fix! Thanks for fixing it and releasing the updated download so fast!
You are welcome!
Thank you Oliver for the fix…
I have a few suggestion for this plugin…
1) Instead of having all user in general being able to view or edit a ticket… could you make it so only certain wp roles can do it… I am using the capabilities plugin and I have custom roles created with it certain capabilities, I only want certain wp roles to be able to view and certain wp roles to be able to edit the tickets and certain ones to be able to create. I was wondering if that come be implemented, it would make the plugin so much more flexiable.
2) Would it be possible to be able to add custom dropdown menus to the ticket. Like if we want to have a drop down menu or input menu for « Assigned to: » or w/e else we want for a drop down or input box when we create and edit the ticket.
Anyways that great work!
Eric,
Here are the answers :
1/ Not sure if you have seen this option but as of release 1.0.12, you have some flexibility with regards to ticket browsing/update. You can set it to anybody, only registered users or only ticket originator and admins. Isn’t it enough granularity?
2/ I am not sure of the requirement there. Are you looking for a way to yank/assign the ticket to users? Through the admin only or frontend as well? Only at the ticket creation or through the entire life of the ticket?
Thank you for the nice plugin, it is really useful for us!
The only problem – how can we filter tickets by Type/Status/Priority? We badly need filtering by status. Is it possible to add such a feature to plugin? Unfortunately I don’t know php and cannot do it myself
Are you looking for filtering or sorting? Filtering is about showing only entries having a designed value. Sorting is juste about sorting by values. Are you looking for this in the admin side or the frontend on the ticket list?
Oliver
1) I saw those options, and they are very useful. However I am talking about letting a certain role be able to view, create or edit. What I am trying to do is allow role1 to create and view only. Role2 to edit, create and view. But I don’t want role2 to be an administrator.
Current I am running Capabilites by Jordi and it allows me to create custom roles, set capabilities to roles and add capabilites. Does your plugin use their own seperate capabilites to achieve the create, view and edit or does it use the WP create/edit/view page capabilites? Cause If you use your own capabilities I could just add it with that plugin and I think I could achieve what I am wanting to do
2) No I am talking about someone just going in and selecting their name in the dropdown menu so that people can see who is working on the problem. For example: You have dropdown menus for priority, status and type, But I want to add another dropdown menu (or more with custom options) to that list such as « Assigned to: »
Eric,
1/ I am currently using the edit_post capability for ticket creation/edition. This is the most flexible. For your needs, I would suggest to set role 1 as a contributor and role 2 as an editor. I guess this meets your requirements.
2/ Ok I think I see what you are looking for. I’d like to get your input on this :
- who could assign tickets to individuals : anybody, registered users only, admins only?
- when can you assign a ticket : only at ticket creation or anytime?
- where can you assign a ticket : in the admin side on the creation/edit page or in the frontend (along with ticket update form)?
I will give that a try, I will play around with the roles to see if I can achieve this.
As for the assign to option.
- I was thinking that only an admin and moderator WProle that fixes problems can assign individuals
- I was thinking when you create a ticket it would show – or N/A and then when someone goes to look at it and edit it they can change it to assign to a person name
- Both the backend and the comment area but NOT during creation. We don’t want members assigning problems to ppl
Is it possible to make it so that we can create our own custom dropdown fields and txt boxes fields, so incase we have more fields we want add later we don’t have to go through code. it can be easily inputed in the backend in admin options or something?
Ok for the assign, I think I got it, I will work on it when I have some time…
For the last request, everything is feasible but not always easy to achieve… I think the easiest would be to bring customer fields meta box in on the ticket creation window. It would allow you to add text inputs.
Hi Eric,
You are lucky, I woke up motivated this morning
So I have coded the assignment feature in 3 hours. Release 1.0.15 is available for download now.
Hope it meets your requirements.
Olivier> Are you looking for filtering or sorting? Filtering is about showing only entries having a designed value. Sorting is juste about sorting by values. Are you looking for this in the admin side or the frontend on the ticket list?
I talk about filtering in the ticket list. So, for example I will be able to see all Open tickets with High priority which belong to category Sales and only them. You already have a filter by category so if you add 3 filters by Type/Status/Priority it would be very nice. All these 4 filters should be combined by AND, I think it is enough in more than 99 % cases. I’m sure it is very necessary feature.
Thank you in advance.
@Max : Ok, I will take a look at this. It shouldn’t be that complex to achieve with raw post form. In Ajax, this is another story
1) Thank you oliver… I was wondering if the assign to could be a text box, so that I can just type something in there and then it will show up as what I type. Because if I have a community of 300+ members I don’t want a list of 300 ppl to look for.
2) can u please explain that customer field meta box thing to me, I am kinda lost with that.
1/ Everything is possible
Now it requires additionnal work on my side… The issue with the text box is that you could enter what you want into that so it needs some error check to ensure that the entered login is a valid login. Also users will have to know login from each other. Let me think about it further.
2/ There was a typo, it is custom fields, not customer fields. This is a meta box that is present in the post/page pages and that allows you to add meta data to your post.
@Max : Ok I did it! It took me around 6 hours and I had very hard times with Ajax on the frontend and mysql left join but sounds like it is ok know
1.0.16 is on its way to the repository!
Hope you will enjoy it.
Hi Olivier!
Thank you for your fast responce! I installed the version 1.0.16.
I see that you made a lot of changes in code. The only problem – I cannot see how I can filter
Unfortunately I cannot give you acess to my wordpress installation (it is private), but I guess I’m doing something wrong. When I tell about filter in the ticket list I mean page:
localhost/wp-admin/admin.php?page=wats/wats-edit.php
when I open it I see no changes since previous version. Proibably you implemented this filter on another page? Or may be I have to change some of my settings or install an additional plug-in?
You didn’t specify that you wanted the filter in the admin… So by default, I implemented the filter in the frontend on the ticket list (the one you add to a post). Please check out there.
Hi Olivier!
Yes, it was my fault that I did not specify where I need.
You wrote: « I implemented the filter in the frontend on the ticket list ». Do you mean localhost/wp-admin/admin.php?page=wats/wats-ticket-new.php ?
I don’t see any possibility to filter there. I only see that there is a possibility to setup type, priority, status, owner for new ticket.
Can you tell me which URL should I open? May be also a screenshot where I can see what should I see.
Thank you!
In fact, I misinterpreted your statment : « You already have a filter by category so if you add 3 filters by Type/Status/Priority it would be very nice ».
If you refer, to the ticket listing feature, there is already a filter by category so I thought you were talking about this one…
To see the ticket list I am talking about and play with the filter, you need to create a post and put into it the relevant syntax as per point 6 (see the original not at the top and check out point 6). This should clarify.
Hi Oliver!
Thank you very much! I missed this point. Now I added such a post with [WATS_TICKET_LIST 0] and happy
Just for a case if you have time – you may add the same filter functionality also on admin page – for most users it will be clear to find it there.
Sorry again that I did not find it at first and thanks for your great work!
Hi Max,
No trouble, you are welcome
Adding these to the admin isn’t that simple to perform as you need to hook on the core. I may implement this later…
I get this error after setting up WATS and changing the ‘guest user’ to GUEST.
This webpage has a redirect loop.
The webpage at localhost/helpdesk/wp-admin/admin.php?page=wats/wats-ticket-new.php has resulted in too many redirects. Clearing your cookies for this site may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
This error makes DASHBOARD unable to load.
WATS requires security rights set to EDITOR in order to work properly, not CONTRIBUTOR as the documentation states.
With the EDITOR setting, the ‘guest’ user has the security rights to change the WATS settings.
Fred,
You aren’t the first one to report this issue but I have never been able to reproduce it on my test site unfortunately. WATS is working perfectly for me with a contributor level guest user.
I am really sorry for this issue. I would be happy to work on it and fix it if you are willing to help me reproduce it. Please contact me through my contact form, it will be easier.
I setup a guest user with contributor privs. That user cannot login. Login just sits there and does nothing, then times out. When i try and login its trying to load wats-ticket-new but just times out and wont let the guest user login.
I also cannot find where a user submits a ticket. Help?
Tony,
I guess you are facing the redirection loop issue faced by few users which I haven’t been able to reproduce on my test site.
I would really appreciate if you could contact through the contact form providing me with your site details so that I can debug the issue.
Did you get my message? I sent it on the contact form
Yes, got it, I have dropped you a mail.
How do I change the default language to English?
The default language is English. If the plugin is working in French for you, this is because you have set your blog default language as French in the wp-config.php file. Just remove this setting or set it as English and the plugin will work in English.
I have emailed you back just now.
The redirection issue is now fixed thanks to Tony’s help with his site!
Just use 1.0.17 and no more problem!
hi Olive,
I have just installed WATS on the latest WP but I found unsolved problem with the integration.
I made a new post and the « comment » already checked (active), but when I check the result (preview) in the frontend, I can not see the status, type, and category dropdown at the page
If you want to create a ticket, then use the ticket creation menuitem, not the post one…
The status, type and priority drop down show up on individual ticket page together with the comment form.
Can it work in Wordpress MU 2.8.4?
I can’t run it.
another question is…
If I change the words of option in Chinese, it couldn’t work either.
Is there any solution?
You really did a great job! Keep going!!
I just tested the new WATS with the admin notification and it works GREAT!!! Thank you very much!
@Echo :
I don’t think it will work with MU but I am not sure… In fact, I haven’t tried as I don’t have any MU test site so I can’t commit on this…
For the Chinese, I don’t know either. I am not sure of how it works. There is a separate enconding I guess. The issue is that since it goes through Ajax, it may cause some problems.
The easiest would be to modify the options directly in the DB in your case I think.
@Tony :
Thanks! You are welcome! Don’t hesitate to rate the plugin on the wordpress extend repository if you like it
Works great, thank you
I am building a website in which the users do not get to see the admin panel. So effectively they can not access the form to submit questions. Can we place the form in a category page by inserting some code?
You need to user the guest account feature. Create a guest user account with a minimum level of contributor and then go to the wats options and set it as the guest user. With that account, they will only be able to submit new tickets.
Hi Oliver!
Thank you again for this great plug-in. One more wish – could you make sorting by columns on pages which contains [WATS_TICKET_LIST 0] and [WATS_TICKET_LIST 1]? If it is hard to implement – is it possible at least to change sorting to descending by creation date – to show the newest tickets first?
Thank you in advance.
Hi Max,
Good news, I have added the sorting for all columns within the ticket listing table. I will post the new release tonight, stay tuned!
This has to be the best supported plugin on the planet. Thanks Oliver
Thanks Tony for your kind words!
Hi Oliver
Thank you, sorting works great!
You are welcome, don’t hesitate to rate the plugin on the WP repository and/or make a donation if you like it!
there is a problem with this plugin and nextgen gallery… when it is activated.. the lightbox lightbox that occurs with nextgen when you click on a thumbnail no longer works. Just thought Id let you know
Hi Eric,
Thanks for the information. I have tried to reproduce it but I couldn’t, the lightbox effect works fine even if WATS is activated. I am using Next Gen gallery 1.3.5.
I just double checked if it was the plugin and it is… When I activate WATS the lightbox no longer works.. but if I deactivate it works fine…. I will provide you with the link to my site once it goes live this week…
How do I get the contributor’s information (or at least username) to show when the ticket is viewed?
You already have the ticket author in the default template. You can modify it by copying it to your theme directory if you want so that your modifications don’t get overriden upon WATS upgrades.
The ticket author appears on the Edit page, but not on the page of the ticket.
Is there a checkbox I missed?
If you are talking about the admin page, that’s right. This is as per WP default template.
Please allow me to restate.
The ticket contributor’s name appears on the admin page (?page=wats/wats-edit.php).
If you click on a ticket to edit, the contributor’s name does *NOT* appear (?page=wats/wats-ticket.php&action=edit&post=637). If someone comments on the ticket, their info appears.
When you view the ticket as a page, the contributor’s name does *NOT* appear (e.g. ?p=637).
How can I get the contributor’s name to appear on 1) the Ticket Edit page and 2) the View Ticket page?
I thought it would have showed up on the frontend at least… Let me have a look at this, I need to check into the code to see what I can do. I will come back to you later on next week as I am quite busy these days.
Hi Olivier!
I found one problem with sorting on pages which contain [WATS_TICKET_LIST 0] and [WATS_TICKET_LIST 1]:
Sorting works fine in most cases but when I try to sort by creation date it sorts wrong, for example: September, 1, then September, 11 and then September, 2
Hi Max,
This doesn’t surprise me. Currently, sorting works regardless data types. Everything is sorted in alphanumerical order. I will check out if something can be done to improve this.
Hi folks,
I just installed your ticketing system which is quite brilliant work. I missed a small feature (ticket summary not only as a dashboard widget but also as a page widget) so I added it and I want to share the code with you:
« Code removed and integrated into the plugin »
As always: use at your own risk
Furthermore this should maybe considered to be included in future releases (basically I just adopted the code of wats-dashboard.php with some minor changes).
One more thing I have a problem with the email feature. Doesnt send email at all. any suggestions?
Thanks for your attention
Hi Tobias,
Thanks for this, I will remove the code from your comment for clarity (already 111 comments on the post) and include it into the plugin if it works fine. I need to do some integration testings.
The email feature will send email to the administrators when a new ticket is submitted if the appropriate option is ticked within the options page. If this is the case and you aren’t receiving any email upon new ticket submission, first check out your spam folder. Then, ensure that your host is properly set up for mail relay. And finally, just let me know if you still have some problems.
@Max & Ben : 1.0.22 has just been released with some modifications to answer your requests.
Hello,
thank for your script.
I have a question
I have installed capability manager but registered user don’t see the WATS in panel because they haven’t « edit posts » permission.
I don’t want grant edit posts permission, i need to show only ticket system.
Any solutions?
Thank you
Hello,
They are few solutions possible :
1/ The easiest one is to use the guest account feature where the shared guest user will only be able to submit tickets
2/ Another one could be to remove menuitem for which the user isn’t entitled to (this can be done by unsetting the right menu array entry). Users will however still be able to access directly the page if they know the url. To prevent, you need to put redirections in place, not really easy and smooth so I would rather suggest point 1.
okay, im not understanding, im looking at the admin and i see where teh admin can create tickets. but what about regular users on the frontend? i dont see where their form is am i missing something? i assumed a frontend user would enter their problem, then on the backend, the admin can see the open tickets and fix accordingly. i appreciate any help.
Steven,
The ticket submission is always performed on the admin side. You can either ask users to register individually or use the shared guest account feature where you provide login/pass to users and then they submit the ticket using it. With this, ticket submission from robots will be very limited as it always need to login to be able to submit a ticket.
Hello Olivier!
Now sorting works well (at least now, when I have only tickets from August and September). Thank you!
Glad it works fine
Don’t hesitate to rate the plugin on WP plugins repository if you like it
Is there a way to make the Ticket number part of the permalink structure?
such as domain.com/%ticketnum%/
I am not sure if this is even feasible. This would require hooking on the permalink creation function. The issue is that you have various permalink structure so modifying it to add the ticket number would be nice if you have the one with postname but if you have another one, it may create bad stuff and 404 errors…
Sorry if this is a very basic question compared to the others.. This is a great plugin but very confusing to me…to implement it into my theme i copied the 2 theme files as suggested into my wordpress theme folder..but what do i do after that?
I created a page…but dont know what todo..basically a good tutorial on how to install this plugin would be nice as it is different to a usual plugin which does things automatically
Thank you, just representing the basic user of wordpress lol
P.S also i have noted that i have downloaded v1.0 of the wats plugin but have notice in the comments that you have released newer version…do you have to pay to get those?
So the plugin is plug and play, as most others plugins. You can copy the theme file if you want to customize these for your needs but the plugin will work by default without copying these.
Basically, you have two ways of operating the plugins with various options to meet your needs :
1/ All visitors use a guest account to submit tickets. This account has to be created by the admin and associated within the options. Then you need to provide the visitors with the login/password and from there, they will be able to submit tickets. This account will be shared between visitors.
2/ All visitors register to have their own account and submit tickets as they would submit posts.
Latest release available is 1.0.23. It has many new features and bug fixes in comparison to 1.0. You can download it from the download link on the wordpress repository (link in the post note). It is free but if you want to make a donation, you are welcome
Thank you for your quick response…im concerned about the frontend …i want users to submit tickets from the frontend not the backend..
i can submit tickets from the backend..but im talking about the display on the frontend..ok so i have installed the plugin but i am not getting anythin on the home page i cant see a list of tickets or even the form…maybe its me
Ok so you cannot submit a ticket from the frontend. You have to be connected to the admin. This is for security purposes. The fact that the user is forced to log into the admin will prevent robots from submitting fake tickets or potentially corrupting the DB.
To see the list of tickets on the frontend, just create a post and insert the relevant tag in it as per ticket listing feature (check out point 6 on the post above).
problemo solved…thanks oliver great support
One final question….can a ticket be created as in submitted from the frontend by a new registered viewer? basically i have a new user who has his own space on the website and i can seem to find out how to provide him a link to CREATE a new ticket.. the only it can be done is through the backend..but i was hoping ifit could be done through the front end…i see the user can update a ticket which has been created in the backend…but an option to create a ticket in the front end? is it possible am i missing something?
Also i have registered a user and tried going to the ticket display page but it dosent allow me to view it comes up with « Sorry, you don’t have the rights to browse this ticket. »..i can see the page when i log in as admin
THanks for the great support so far..sorry for being a pain hope you can help me
You can only submit ticket when you are logged in. What you could do is adding in the frontend a direct link to the ticket creation page in the admin.
For the rights message, you need to set an option to allow every registered user to see the tickets.
wow i am loving this support i have solved the second issue…but would love in your future releases (if not hard) to implement a frontend form for submitting new tickets.. i dont want my users to go to the backend at all
The best supported plugin by far…and i would love to donate
Thanks for your kind words!
For the frontend submission, I have thought few times about it, it is very touchy from a security point of view. I don’t want to open a breach within WP core or DB because of a miscoded form handling on the frontend.
Hey Oliver… I was wondering if you ever had a chance to look into the conflict between the NEXTGen gallery lightbox issues and this plugin??? Cause I am running the latest version of WP, NG and this plugin and the issues is still occuring… my site is http://www.caconline.ca and i currently have WATS enable on a private on a private page, but as you can see the lightbox when you click on a thumbnail is now gone, and this only occurs when i activate ur plugin… Hoping you could take a look into it.. Thanks…
Only the thickbox works… lightbox/shutterset etc… none of those ones work.. if you go to about > Department > communication and click on a picture you will notice that they do not work.
Thanks Eric, I have dropped you a mail with modified code, just let me know if it helps so that I can release it for everybody.
Hi Olivier,
Great plugin. If I want to at the status of a ticket to the index page posts what line do I have to put in between the category and comments php in class= »postmetadata »(line 23 of index.php of theme) Something like but then for the ticket status
Cheers
Marco
Hi Marco,
In the loop, just add the following function call :
wats_ticket_get_status($post)
This will return you the status so if you want to display it, just use echo wats_ticket_get_status($post).
Cheers,
Olivier
Like this I don’t know a lot about php so you really have to spell it out for me
Well, you just need to add the code into the target php file at the place where you want the status to appear. I guess this is near the meta data from what you told me.
If you want, drop me a mail through the contact form and I will help you further.
Hey Olivier
I found a bug. (maybe)
I set the ticket only be seen by creator and admins.
But if any users login the site, they can saw the ticket in recent comments of the dashboard screen.
another question is…
If the OPENID user login, they can’t see WAT in the admin panel.
Is there any way to solve it?
Hi Echo,
For the recent comments, that’s right! I haven’t thought about it! I need to check if there is a hook on this dashboard metabox to filter it.
For the Openid user login, I am not sure of what it is. I need to look into it.
Hi Echo,
I have just published 1.0.24 with two modifications to meet your requirements with regards to the recent comments :
1/ Filter the recent comments dashboard widget based on the ticket visibility setting;
2/ Added an option to remove access to comments edition menuitem for users without moderate_comments capability.
There is no SUBMIT button on the WATS Option page. I cannot save the settings!
I removed the Guest User field from the WATS Options page and it works fine now. Something is wrong with that field.
The submit button is at the bottom of the page, it is called « Save »… If you have a problem, please drop me a mail with your site url through the contact form.
Hey Olivier,
Great Job!Thanks a lot!
about OPENID
user won’t need to register the site, just use OPENID login.
There’re two plugins could do it, OpenID and JanRain RPX.
Hi Echo,
For Open ID, if the user isn’t registered, then it doens’t have a local account. Without a local account, it canno’t post tickets, just as posts… I am not sure of what a user logged in with Open ID can actually do… Sounds like a virtual account but what are the capabilities?
How do my visitors submit tickets? I do not see any way for them to do it? Am I supposed to link to a page or post?
Visitors should either register as single users (with contributor role) or use the shared guest account (that you have to setup). Anyway, they should log into the admin to be able to submit tickets.
Althought guest can open the ticket.
If there are some private tickets whose owner won’t let them be shown to others, and the site because some causes can’t be registered.
OpenID can do it.
I’m not sure about it, just consider how to make it work….
Echo,
Well, this feature sounds really specific… I am happy to provide bug fixes and support as you have seen but this is very time consuming. While this plugin is free, the development has a cost. I have spent more than 250 hours so far in the development and support.
I am sorry but based on the very small amount of donations I have received so far since WATS first release in June (5€), I don’t want to spend time on too specific features for the moment… I am quite sure that you will understand that I cannot spend free development time coding too specific features.
Echo,
I have looked at Openid and I guess it doesn’t make it with WATS because Openid users are subscribers and the minimum required level for WATS is contributor because WATS user needs the edit_posts capability in order to be able to submit tickets.
Hi,
It looks like you have the makings of a really good plugin but I find I cannot use it because of two reasons.
1. The system only allows people to log tickets via the backend of the blog (via wp-admin)
2. When you display the tickets using [WATS_TICKET_LIST 0] shortcode, one of the filters displays all the email addresses of all the registered users which is a problem for me.
I understand your security reasons for not wanting to allow people to log tickets via the front end of the blog but in my case all my members are logged in. I use a plugin from http://www.infusionsoftmembershipsoftware.com which ensures that only people who are registered can see the pages so in my case I would not have the issue.
Could you not validate that the email address is already inside WordPress before accepting the ticket.
You could also add a captcha to the new ticket form which would stop most of the bots automating the process.
Thanks for your time with this. I would love to be able to use your plugin on my site.
Hi Mark,
The wats ticket list shortcode filter doesn’t display emails. It displays users login. Now if you have set emails as users login, that’s true that it would display emails. There is however an option to restrict ticket visibility between users, check out this one, it may help.
If all you users are logged in by default to view the frontend, then that’s good, they won’t have to login to submit tickets, you just need to put a link to the ticket submission page. You can also customize the new ticket page template to make it look like your frontend if you want.
The security issue behind the ticket submission within the frontend is mostly that WP hasn’t been designed to do that. So I would have to take the admin side code and adapt it to the frontend. My fear is that I will have to remove many internal checks to make it works because the admin works with a redirection engine to enforce security and checks which you don’t have within the frontend. At this point, I don’t feel confident with this and I don’t see that as a major constraint to ask people to log into the system. There is the guest account feature for people not willing to register.
Hi, using WATS 1.0.24 there are some problems:
- Trying to rename Critical to « Vážné » – error: not allowed characters. I tried it with some other characters and it is the same (ž, š, č, etc.)
- Is it possible to add another dropdown menu? There is type, priority and status and I would like to use two other internal characteristics with some predefined values which should be fulfilled during opening ticket.
Thank you very much for your help…
Hi,
1/ Please drop me a mail with the required characters list so that I can include these. These are characters specific to your langage. Currently, there is a filter to prevent special characters from being entered for security purposes.
2/ Which additionnal dropdown menus do you want? Everything is quite static so if you want additionnal dropdowns there, I need to take a look at what can be done if that’s not too specific.
hey, Olivier
I totally understand and I really appreciate what you did.
and.. I need to say this plugin is amazing!
Thanks Echo
hi oliver, is possible have the pot or po original update? i want translate your plugin, thanks
Hi Arturo,
Thanks for this. In order to translate the plugin, just make a copy of the WATS-fr_FR.po, then rename it with the appropriate langage suffix, open it with PoEdit and translate from english to the target langages the sentences already translated to french. Don’t translate the empty ones, the translation is already included within WP Core translation. Then send me a mail through the contact form. I will reply and from there, you could send me the files as attachment.
Thanks!
[...] Plugin Homepage Tags: cms, CRM, customer, help, support, Taxonomy, ticket Comments are closed. Visitor Like/Dislike Post Rating RSS [...]
Hello
Great system I really like it however there are some tweeks i need to do.
1. How to only show the global stats for the administrator. i.e I dont want to show the user how many tickets are created and opened in their dashboards.
2. How to i get the ticket number into the email response?
3. If a user submits a ticket is it possible that the administrator does not have to publish the ticket, can it be automatic??
Hello James,
1. This needs some further coding. I need to add an option. What is the goal? Having no dashboard stats widget for all users but the admins?
2. Which mail are you talking about? The ticket creation notification?
3. Yes it can, just set ensure that the user role is not contributor but author.
Hello Olivier!
In our small team we use your plugin with great pleasure, thank you.
If you remember, you added a filter by ticket type, priority, etc. I have a suggestion – very often we want to see not tickets with exactly one status, but tickets with a statuses which are less or more than this status.
For example, often we need to see tickets with status which is smaller than Completed (so, it will include Newly open, Waiting for details, In process tickets), etc. Or, vice versa we need to see all tickets with status greater than In process (Completed and Closed tickets). Similar idea belongs to priorities, but it is not very critical.
Also another idea – add a possibility to store such filters in some form. I think it is possible to do in a form like [WATS_TICKET_LIST 0/1 a1 op1 val1 a2 op2 val2 ...] where aX is type/priority/status/owner, opX is relation (ge: >=, eq: =, etc) and valX is a value (probably a code).
I think if you add this feature it will add an additional great feature for your amazing plugin.
Thank you for your work anyway! It’s great.
Hello Max!
You are looking for advanced features here
The filtering function is already quite complex. Adding this feature could have some interest for some users but it would require a lot of work on my side.
What value would you attribute to this feature development? 1€, 10€, 100€, 1000€? My feeling is that it would require between 5 and 10 hours of coding/testing. As an engineer, customers pay from 150 to 200€ per hour to my company (my cost is around 90€).
Don’t take me bad, I won’t ask you to pay 2000€ to get this feature. I would just like to see what amount of money you would be ready to donate to me in order to get the feature implemented in a later release? I am asking this because many people asked for features since first release in June 2009 but I only had one donation which I think is a bit low if you compare this to the hundreds of hours spent on the development, isn’t it?
Hi Olivier!
Of course I understand that you spend your own time for this work and you want to get some benefit from it. As for me it’s a great and useful work and if I were a rich guy I would pay well for it, no doubt. The problem is that I’m not reach, unfortunately and my income is about 10 Eu per hour. Using of this plugin in our company was my own initiative, so the company definetely will not pay for it. I never tried to give you a hope that I’m able to pay for it, sorry if I was misunderstanded. Of course it is always up to you whether you want to implement this or that feature, who can force you… But if this plugin has extended functionality may be you have higher chances for donations. Anyway thank you for your work.
Hi Max,
No pb, I agree that you haven’t given any hope for a donation.
Hi Oliver thanks for the reply.
With regards to the email, when a ticket is sent it should be given a the unique number does that make sense?
Hi Sorry i forgot about the dashboard. The admin should only see the number of global tickets. The user/guests/authors etc… should only see the tickets which they’ve created which are open and which are closed.
I will make a donation when I have some funds
Hi James,
The ticket number is obviously unique. Each ticket has its own number. The format is based on the option (no number, number, dated number).
With regards to the dashboard, I have coded a modification based on your original feedback, isn’t it enough? Should I modify add modify the options and have two options : one for the global stats and another one for the user stats?
Hi Olivier
the dashboard should be seperated, global stats should only been seen by the administrator. i.e if 100 tickets where raised by 10 different users he should see all 100 tickets in the dashboard.
The user should only see the number of tickets raised by there account i.e joe.bloggs raised 15 tickets which are open and 5 which are closed. He should only see in his dash board 20 tickets, 15 open 5 closed. The user joe.bloggs should never see the overal number of tickets raised.
does that make sense?
Hi James,
I have performed the modification. The option will now only apply to global stats and user own stats will be always be visible individually.
1.0.29 will be posted by the end of the day.
Thanks for a great plugin Olivier! Simple but effective!
I had a small problem which I thought I had solved – but havent. I changed one of the settings – I think the root cause was setting the Shared Guest User to the admin user. From then on – I couldnt get into the admin for wordpress, it would only show the new ticket interface.
I then found the wats options key in the mySQL database and removed the following from it, leaving it blank.
*** sql entry removed ***
This almost fixed the problem – but now I have the following errors for global and personal closed tickets on my dashboard : •Number of tickets closed :
Warning: Invalid argument supplied for foreach() in D:curioushippo.comwwwrootwp-contentpluginswatswats-lib.php on line 175
I am ok to uninstall it at the moment, but I need to know what database keys to remove to ensure a clean reinstall. Can you assist? Alternatively perhaps you know how to solve this little problem.
cheers
Jon
Don’t worry!!! I fixed it: the options field was missing a whole load of stuff, so I took the shared guest user settings from the « repaired » database string, pasted into the old one above, then resubmitted the above string as my wats options. All sorted. Now time to apply the upgrade you just released!! As soon as my little site begins to bring in some money I will make you a donation. Thanks again for your efforts.
And to all users – DO NOT set your shared guest user to your main administrator account!!! Not only is it a nonsensical thing to do, it will cause you considerable grief.
Jon
Hi Jon,
Well, the issue is that the guest user is intended to be a shared account. So I have restricted it to be only able to access the ticket creation page, nothing else, for security reasons. So if you attach an admin profile to it, this admin won’t be able to do anything else than create tickets.
I think the errors you had came from the fact that you corrupted the sql entry format. As you directly change the entry, you need to update the numbers before the entry otherwise, it is messed up.
A simple workaround if the problem happens again, just remove the wats_options entry from the table and then reload the options page, this will create a new entry with default value (ie no guest user set). This will fix your issue.
Last point, you have a very nice site, cool design
Cheers,
Olivier
Hi Olivier the new update is perfect thank you, 1 more questions.
When the ticket creator get an email response from the person dealing with the ticket, the email is a bit difficult to understand. Example below. Also in the subject line of the email it has name of the blog and comments and the subject line. Is it possible to have the ticket id. for example Subject = Ticket 6 – Ticket Title. Also is it possible to remove the whois, author and just have the message?
Hi James,
What you see is the default template for comment notifications. I have performed some researches and apparently, there are some hooks so I could potentially modify this.
I will add this to my to-do list for upcoming releases…
Hi – LOVE the WATS plugin and I’ll be donating soon to your efforts BUT how can I rearrange your footer so it’s more centered and in line on my site homepage?
Also – France uses the Euro right? My American dollar donation will not be worth much
Hi Rafael,
Thanks a lot! Yes Frances uses Euro. Not much is better than nothing, trust me
For the footer issue, I would need to see the problem before I can do something. You can contact me through the contact form for more direct access.
Hi Olivier, I’m struggling. I’ve got your plugin installed but cannot work out to get anything showing up on the front end so « Subscribers » can enter tickets.
I suspect I am missing something really obvious. When I log in as an Administrator I can create a new ticket without any problem.
How do I enable the front end? Great plugin by the way!
Regs….David.
Using:-
WordPress MU V2.8.6
BuddyPress V1.1.3
Hi David,
You cannot create a ticket through the frontend. You need to use the admin side. If you don’t want users to register to be able to submit tickets, just use the guest account feature. Create a contributor level user and set it as the guest account in the WATS options. Then give the login and pass to users. This will allow them to access the ticket creation page (and only this one).
Hi Oliver,
It looks like an excellent plugin but a bit confusing as well. I am getting 2 problems. One, there is this line showing on the index page which I can’t be able to place properly.
« Wordpress advanced ticket system from l’autre monde »
It is just distorting my theme and even default theme as well.
Secondly, I am confused on how a guest user who submitted a ticket can keep track of it? I mean this user is being shared by every guest. Would not that grant every guest to be looking at each other’s tickets?
And as we are not asking for any contact information during the ticket submission, how can we assign that ticket to a new guest user if he has submitted the ticket but did not provide any contact details.
Please explain.
thanks!
Hi Touseef,
The line you are talking about should be showing up in the footer and should not break your layout design. If it is, this is because the call to wp_footer is misplaced within the footer.php file. Try to adjust it and if you can’t manage to achieve what you want, just drop me a mail through my contact form with your site access details and I will take a look at it.
If you are using the guest user feature, then definitely, every visitor using this account will be able to see other visitors tickets if they have used the guest user.
You can assign the ticket to the guest user but I agree that this isn’t really relevant as this is a shared account.
In your case, I would suggest to use dedicated accounts for each user, this would allow you to clearly identify users.
Regards,
Olivier
Well thanks for the info. I looked into the code. Actually the layout is div based with absolute widths so it was showing at the end of the footer div. I have not uploaded the site yet, still working on it localy so doent have anything to show but thanks for the offer anyways.
I also have figured out a solution that I would not be using this ticket systems for guests. For them, I gonna use a simple contact us form.
But now comes another problem.
I do not want my registered users to change the status, priority and other settings of the site. I dont find any such option in admin panel so guess I have to remove the code, right?
Or is there any other option to only allow admins to change the status/priority options of the ticket.
Ok, this is not surprising, you should increase the div width if you want it to look nice…
I am not sure I understand what you are talking about for the status, priority and other settings of the site. Who can set these if not registered users? If you want only admins to be able to modify these, just add a test within the comments template file to verify if user level is admin or not when displaying the dropdown selectors.
i want to add categorie in persian language in « Categories opened to submission » . after that when i click add buttom show this message : Error : the entry contains invalid characters
Yes, this is because you are using special characters that aren’t in my regex. Please drop me a mail with the list of persian characters so that I can add these.
i fix this problem . plz add this char in your regex .
کگچپژی
Which chars? Only the ones you have put into the comment? I can only see 6 chars. These are all persian chars?
No . if you put this char in regex the persian language is complete . in arabic language these words « گچپژ » dont exist . ک ی in persian layout is two type . one is same as arabic language and another is same as my comment above. only add these chars for support persian and arabic togheter . it’s enought
ok thanks, I will do it in the coming days.
Hello Oliver
Is it possible to raise a ticket by sending an email to a ticketing email i.e *** mail address removed to avoir spam ***
I know Request Tracker can do this, and if WATS can do this then I would a very happy chap.
Going to make a small donation.
Hi James,
Thanks a lot for the donation! This is much appreciated!
Right now, WATS can’t do what you are looking for (ie raise tickets through emails). I will look into that to see what can be done.
Cheers,
Olivier
How do I remove the copyright bar at the bottom of my front page?
Why do you want to remove it? This software is free. This copyright is the only thing I am asking for as a compensation of my hard work. I already spent 300 hours developping WATS. This copyright is on the footer, not disturbing the user so I don’t see why you would like to remove it…
If you want to discuss this further, please drop me a mail through the contact form.
Hi! Thanks for the great plugin!
When a user clicks the link in their email and goes to my site, the ticket is so wide that it moves my sidebar down below my footer on wp 2.9.1.
I have checked the css, template, single post, and single comment script and can’t figure out how to set the width of the ticket.
Any help would be great!
Thanks!
Merci!
Alan
Hi Alan,
Hard to help without a view of what’s going on. Can you please drop me a mail with your site url?
Thanks!
Olivier
This plugin is an excellent idea and I’m very glad to have found it! I appreciate your hard work to make such a unique plugin. I’m currently going through it and testing, hoping I can use your new frontend ticket submitting option. I’ve come across a problem with notification and update emails not being sent to the test client (submitting tickets). The emails come through to the admin just fine, though. Is there something I’m missing here? The ticket page link won’t work for the test client either.
Thanks!
Scott
Hi Scott,
Glad that you enjoy the plugin! Don’t hesitate to rate it on wordpress.org plugin repo, write a review about it or even make a donation!
With regards to notifications, have you checked the settings? You have to activate the notifications under the options. Then you have two kind of notifications : notifications for new tickets which are only fired to admins and notifications for updates which can be fired to anybody or only ticket originator and admins. Notifications can then be turned on/off under user profile.
Please note that there is currently no notification generated to the visitor submitting a ticket by email or through the frontend contact form.
With regards to the ticket page link, I am not sure that I understand what the problem is. Please clarify. You can drop me a mail through the contact form.
Cheers,
Olivier
Thanks Olivier,
Yes, I went through the settings and tried various things, but it looks like there wouldn’t be any client notification generated through the frontend form. Thanks for making note of that.
The issue with the access link is with the page link generated by submitting the frontend form. It is pending update by admin at first, to prevent spam which is good, but after the admin updates, the link still does not work. Tried all kinds of tricks, but there seems to be a disconnect somewhere. I hope that makes sense – doing my best to describe.
Thanks again!
Scott
Hi Scott,
For the client frontend notification, I have to say that the frontend has been implemented very recently. I still need to think about the way to notify users because notifications will be sent out to non registered non authenticated users and therefore, it will be easy for someone to have the system sending spam by submitting tickets with another user email, so I need to implement some options so that the admin understands the constraints behind this.
For the ticket link, there should be a bug somewhere. May I please ask you to send me your site url with a sample failing ticket?
Thanks!
Olivier
Hi Olivier
I am getting
Error : The ticket description is empty or contains invalid characters.
even when I am typing plain English in. It does contain a few all caps, quote marks and ( or -, but nothing fancy.
What could be the trouble?
Update…it seems to work if I take out the carriage returns (the paragraph marks).
Hi Charles,
You are right! I will publish a release fixing this by the end of the day today.