For future development

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!

Thank you,
I became your client a few days ago .
I appreciate your honesty and look forward to future updates .

I don’t know if it is from my installed plugin or this is how you thinked to be , but when i compose a reply ticket the text in Frontend is linear, without the rows (Enter or <“br/”>). BUT when i copy a text from another page (Copy/Paste) the text in frontend was ok with rows and enters , good paginations. When i create a response the pagination does not exist text its linear. It is a bug in my module or i have done wrong something?

Best regards.
Robert

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.

New update is not working quite 100%,
In frontend, the table containing the list of tickets is displayed but the table whom contains the list of messages no longer displays. ??

Thank you for your trubble!

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 ??

I found the issue “it’s not you, its me” :))
2 days ago i have bought a DV SSL from globessl and now i realize that the problems started that period.

The ssl is active on wp-admin, also entire website but only when you type “https://&#8221; ; the plugin is acting for “https://&#8221; unusual but when i type “https://&#8221; is acting ok.

Thank you for your trubble!