[stevland]

Hey guys… please upgrade to osTicket-1.12.2-Awesome-101 to resolve this issue.

[stevland]

Hmmm it is still marked as “support request” on my end. Actually I’ve changed it to “in progress”.

I just released 105. I have no immediate plans or schedule for the next release. I will try to tailor something for you soon.

[stevland]

Nein, Ihre PHP-Version ist in Ordnung.

Bitte überprüfen Sie Ihre Fehlerprotokolle. Wenn Sie nicht wissen, wie Sie Ihre Fehlerprotokolle überprüfen können, wenden Sie sich an Ihren Webhost.

[stevland]

Leider sagt uns HTTP ERROR 500 nichts Sinnvolles. Bitte überprüfen Sie Ihre Apache / PHP / MySQL-Fehlerprotokolle auf die eigentliche Fehlermeldung und veröffentlichen Sie diese hier.

[stevland]

Did you get this sorted yet?

Error 500 is very generic and tells us almost nothing. Pro tip: check your PHP, Apache and MySQL error logs for the real error message!

[stevland]

@Code54,

Did you learn anything through posting to my osTicket Awesome installation? I’d like to revert my template back, so do let me know.

[stevland]

Oops sorry disregard my last message!

I got confused. I fixed this recently and I mistakenly thought the fix had been included in the last release. It was fixed since the last release, hence it will be included in the next release.

[stevland]

Thank you very much for taking the time to clarify this. It will be fixed in the next release.

[stevland]

Okay, I have added %{ticket.thread.lastmessage} to the Response/Reply Template of my own company’s osTicket-1.12-Awesome-105 installation.

Go ahead and open a ticket here. I will reply and you will see that the %{ticket.thread.lastmessage} variable works.

[stevland]

By “latest update” I assume you mean osTicket-1.12-Awesome-105, yes?

Please clear your browser cache and try again.

If the issue persists, let me know if you encounter the same issues in the latest staff demo.

[stevland]

That is a good point. I also find it annoying to have to use the keyboard to submit the search. I will address this in the next release.

[stevland]

Unfortunately, a 500 error is a very generic server-side error that tells us almost nothing. There will be more information as to what is going wrong recorded somewhere however. Please check your PHP / Apache / MySQL logs for the relevant error message.

 

[stevland]

@Code54,

Regarding osTicket Awesome, there is nothing that should change the way templates work.

When problems such as this arise, the first step is to always isolate whether or not it is actually an issue with osTicket Awesome.

Do you still have your original osTicket installation? As per the installation instructions I recommend holding onto it for situations like this.

RBGE in the osTicket forum is recommending the same thing. He is using the term “clone” installation. I would call it a “parallel” installation. If you didn’t keep a parallel osTicket installation, you can easily add one.

Assuming you have osTicket Awesome installed into a folder named support/, upload the osTicket (v1.12?) files into a folder named support-old/.

Copy support/include/ost-config.php to support-old/include/.

Visit your core osTicket installation by going to http://www.yourdomain.com/support-old/scp and troubleshoot your email templates.

If it turns out that it is an issue with osTicket Awesome, let me know!

[stevland]

@graphskill,

Thanks for the animation. Your “back to top” button is definitely messed up! (It is also meant to be on the left side of the page).

Have you tried clearing your browser cache?

Do you see the same glitch in the demo?

[stevland]

Indeed, a “back to top” button has been implemented in 105. And you only have to scroll down 600 pixels for it to become visible.