Tyler

Awesome news! Cheers!

Sent that a few days ago. Any ideas yet?

https://smrf.us/wp-admin/
login: admin
pw: tester123

plugin activated, working fine. if you change permalinks to post name, it starts blocking the login page. let me know if you get locked out or anything.

I did some experimenting and found that the error is derived from the Permalinks settings. When on default, this problem does not exist. When you use post name, which is what I use for all my sites, the login redirect error happens.

Hope this helps in solving the issue. I didn’t think the test site was necessary anymore after discovering this, but if you’d still like access, let me know.

That’s very strange. I’m hosted by godaddy, so I don’t think I can get you “access to the server”. However, I can set up a test wordpress installation on my hosting and give you access. Let me know.

Other plugins currently running:
Disable Comments
Disable Title
Meta Slider
Page Builder by SiteOrigin

Ok, after much trail and error I figured out how to make the emails include the ticket details. You edit /php/submit_ticket.php and there’s two $cleaned_message fields, one for the message sent to the submitter and one to admin.

Original:
$cleaned_message = __("The content of the work order is: ", 'wpsc-support-tickets'). '"'. strip_tags($_POST['wpscst_initial_message']) .'"';

This is how I changed it for the submitter:
$cleaned_message = __('<b>Name:</b> '. strip_tags($_POST['wpsct_custom_2']).' <br><b>Company:</b> '. strip_tags($_POST['wpsct_custom_4']).' <br><br><b>Contact Information</b><br>Phone Number: '. strip_tags($_POST['wpsct_custom_10']).' <br>Email: '. strip_tags($_POST['wpsct_custom_5']).' <br>Biling Address: '. strip_tags($_POST['wpsct_custom_6']).' <br><br><b>Property Information</b><br>Property Address: '. strip_tags($_POST['wpscst_title']).' <br>Access Information: '. strip_tags($_POST['wpsct_custom_22']).' <br>Occupant Information: '. strip_tags($_POST['wpsct_custom_23']).' <br><br><b>Work Order Information</b><br>Type: '. strip_tags($_POST['wpscst_department']).' <br>Work Order Message: "'. strip_tags($_POST['wpscst_initial_message']) .'"');

This is what the email they received looks like now:

Thank you for opening a new work order. You will be hearing from us shortly to confirm the order.

Please visit https://www.cspreo.com/work-orders to view all your pending and complete work orders.

Name: CLIENT NAME
Company: CLIENT COMPANY

Contact Information
Phone Number: 9045555555
Email: [email protected]
Biling Address: 1234 TESTING DR JACKSONVILLE, FL 32222

Property Information
Property Address: 12345 Property Blvd Jacksonville, FL 32222
Access Information: LB CODE 1234
Occupant Information: CALL BLAH AT 555-5555

Work Order Information
Type: Repair
Work Order Message: “Work order details. Blah blah blah blah blah blah.Repair this, repair that. “

I did pretty much the same thing for the admin email too. Obviously, I have customized this script a lot. But to call new items to the email you have to add fields like this:

<br>Occupant Information: '. strip_tags($_POST['wpsct_custom_23']).'
Line break to format mail, section name, and the strip_tags($POST is calling the ticket custom forms. To figure out the numbers, just view source on your browser on your Support Ticket page and it will list out all the values of your custom fields, as well as the default ones, like wpscst_department.

I hope this helps anyone trying to customize the auto reply emails; it took me the whole afternoon to figure it out.

The only thing that I still can’t figure out, is why in the wpscst_initial_message value the function is not including line breaks. Currently it jams the message all together if the user put in line breaks.

Fixed the &nbsp issue by toggling Send HTML Emails to true (pro version) but now everything is mashed together when the email is sent to me. The email that the client views is easily edited from the settings tab, however the email we view isn’t.

I will submit a feature request to add editing this email to the settings page. In the meantime, I would still like to edit it from the backend, any pointers would be great.

No, your plugin is fine. It was the theme – Hemingway. Other people might have this problem though. I found the solution on a general html support site with a completely different WordPress theme that had the “input { -webkit-appearance: none; }” line in the style.css.

Is there not a way to edit tickets?

Style.css

Remove the following from CSS:

input { -webkit-appearance: none; }

input[type=search] {
   -moz-appearance:none;
    webkit-appearance:none;
}

resolved

After much experimenting, I found the solution.

.blog .header-cover  {
display: none;
}

For some reason header-cover is used on the blog page instead of header-image.

What browser are you using? Do you have some kind of custom browser theme?

I’ve never seen radio buttons look like that.