jquindlen

I’m not getting that issue, the front end works perfectly for me still in all my test sites. I do not doubt that you’re experiencing the issue though.

Here’s some troubleshooting advice to help me figure out what is causing your issue.

First, insure that you’re running the very latest version of wpsc Support Tickets: at this time it is 4.9.23. If you’re not running 4.9.23 then update to it immediately, and then recheck to see if your problem is still present.

Next up, if you still have the issue, let’s check to see if your settings may have been reset. Go to wp-admin > Support Tickets > Settings > and verify that your Main Page is set to the page that you’ve placed the [wpscSupportTicket] shortcode.

If all of that looks good, then next we should see if there is a plugin or theme issue. To do that, please disable all plugins except for wpsc Support Tickets and switch to a default theme, like 2012. Now revisit the support ticket front end and see if you’re issue has been resolved. If it has been, that means that another plugin or your theme is causing the issue. To narrow down what plugin or theme is causing the issue, reactivate 1 plugin, then revisit the support ticket page and see if it still works. If it does still work, then activate the 1 plugin, and check again. Repeat until you activate a plugin that causes the support ticket page to fail. Once you locate that plugin, let me know and I’ll write a work around for the plugin. Finally, if no plugin causes the issue, reactivate your theme. If the theme causes the issue, let me know which theme it is.

Thanks again ??

Thanks for the compliments and for using wpsc Support Tickets. Apologies that you’ve experienced some issues. Hopefully I can help resolve them for you.

The PRO version uses a different text domain for the PRO plugin: wpsc-support-tickets-pro

The open source version posted on www.ads-software.com has the text domain of wpsc-support-tickets

You just need to create a .POT file for the PRO version, as one has not been generated.

By the way, in the future you should know that it is against the www.ads-software.com’s forum policies to seek support here for anything other than the free version which is hosted here. Feel free to contact me to directly if you have further issues with translating PRO or other issues regarding PRO. Thanks again, and have a great day!

Hmm. I’ve tried something which may help. Try updating to 4.9.23 and let me know if it solves your issue or not (note, it won’t allow to have more than one line break in a row without explicitly using tags.) Thanks again.

Thank you for the compliments and feature requests. Let me offer you some information which you may find useful:

1. The ticketing system does have a unique ID for each ticket, although it is not prominently displayed anywhere, which is what I believe you’re asking for. As an admin, you can see a tickets ID now when you go to wp-admin > Support Tickets > and hover over the link to a support ticket. You will see a URL like this, where the value of primkey is the unique ID, in this case 11: https://example.com/wp-admin/admin.php?page=wpscSupportTickets-edit&primkey=11

It makes sense to display this more prominently. Look for me to address this feature request in an upcoming release.

2. I understand what you mean. One of my other plugins already has a similar feature which I can easily port over. Should be a simple enough feature request; I’ll make sure it is included in upcoming release.

3. As a developer, I am not a fan of TinyMCE, which is what WordPress uses for it’s text editor. The reason I am do not like it is because I have been developing WordPress themes and plugins since 2007 and have previously used TinyMCE in both themes and plugins that I released. What I experienced over the next several years was a lot of issues related to TinyMCE, plugin conflicts, javascript conflicts, as well having TinyMCE change within WordPress itself several times breaking previous code that worked.

After all those headaches I moved away from TinyMCE in all my plugins and themes. I know they recently updated TinyMCE to make it much better, and I’m not sure if those updates broke backwards compatibility again or not. It is for these reasons that I hope you understand that I am not willing to throw out all the coding I have for the current editor, and to write a bunch of new code to switch back to TinyMCE, which was a previously nightmare of wasted work. Hope my honesty here doesn’t make me sound off putting. I just want to give you the truth as to why I feel justified to decline your 3rd feature request.

Thanks again for your compliments and suggestions. I definitely did take it all positively, and I hope my reply is also taken positively by you. I appreciate it!

I think I got it fixed in 4.9.21, which should be available for download within the next 30 minutes (uploading it now.) Double check that 4.9.21 does solve the issue for you, but I’m sure it will as it solved the issue for me. Thanks again!

I’ll take a look and see if I can recreate the issue. Thanks for reporting it.

EDIT: I was able to recreate the problem. My guess is that the guest email address is not getting set properly, causing the first ticket to fail on submission but at the same time causing the guest email to set correctly, allowing further tickets to submit correctly. I’m digging into the code now trying to prove/disprove my theory so that I can get this issue patched. Thanks again.

That sounds frustrating, and I’d be happy to help resolve your issue. So apparently you’re experiencing an issue where you can submit support tickets correctly, but other registered users can not? Or is it guests? Or both? Do you have a main page set in the settings? Have you tried disabling all other plugins and testing whether or not the issue still remains with only wpsc Support Tickets activated? Let me know, and thank you.

You’d be looking for “Statute Expires” in the code instead of “StatuteExpires” as I posted above. Like I said in the email you sent though, if you can help me out on this dinner date, I’ll get this code done for you tomorrow ?? I’ll still help you here regardless.

if you’re only looking to display the field “StatuteExpiry” then change this line:

if(@isset($res[0]['primkey'])) {

to this

if(@isset($res[0]['primkey']) && $specific_items[0]=="StatuteExpiry") {

the inside of that if statement should probably only echo the value like this:

if(@isset($res[0]['primkey']) && $specific_items[0]=="StatuteExpiry") {
    echo strip_tags(base64_decode($res[0]['value']));
}

or something like that. I haven’t tested this, but I think it should point you in the right direction. Let me know how it goes if you have any other questions.

EDIT: and get rid of the table code that is before and after the foreach loop.

Thanks! Glad to hear it resolved the issue. I took a stab in the dark, and was successful. Just make sure to leave the setting at wp-admin > Settings > Email > Override WordPress Email Sent “Name” & “From” > to FALSE. Thanks again for your help, glad to hear things are resolved!

You’ll want to copy the wpsctDisplayCustomFieldsToFrontend() function you mentioned and name it a new function that spits out the data you want, where you want it. Get rid of the table code inside the function, and use $specific_items[0] for the custom field name, and strip_tags(base64_decode($res[0][‘value’])) for the value.

Thanks. As I said, I’ve tried your suggestions to recreate the issue but the emails always worked for me. I’m asking for your help if you can just check to see if the new version fixed the issue or not so I can decide if I need to investigate further. I’m asking for that help because I cannot recreate your issue myself, as emails are always sent in all of my test environments. Since I haven’t been able to replicate your problem, it is literally impossible for me to test to see if the problem is resolved for you, which is why I’d appreciate you taking a second to let me know one way or the other if version 4.9.11 still exhibits the behavior you describe. Thanks again.

Let me know if the latest updates resolves your issue (4.9.10)

I’m working on a fix, but I can’t recreate your issue at all, which is making it especially difficult to fix. Obviously you can rate any plugin whatever you’d like, but I ask you to consider that you’ve used my works for years of service, does it really warrant 1 star now, even when I am working to fix an issue that from all accounts so far, is only affecting your installations? Please, work with me so that years of my work doesn’t get written off as garbage. Thanks.

Let’s keep this in a single thread, no need for another.