[stevland]

Hola Javier,

Se informó un problema similar aquí, pero no he tenido la oportunidad de verlo yo mismo.

Lamentablemente todavía no sé cuál es la causa de esto.

Pero estaré feliz de resolverlo SI me concede acceso a su instalación.

En caso afirmativo, complete este formulario con la mayor cantidad de información posible.

—

Hi Javier,

A similar issue has been reported here, but I have not had the opportunity to look at it myself.

Unfortunately I don’t yet know what the cause for this is.

But I am happy to figure it out IF you will grant me access to your installation.

If yes, please fill out this form with as much information as possible.

[stevland]

Hi Onur,

osTicket / osTicket Awesome doesn’t support PHP 8.3 yet. Please downgrade to 8.2 or 8.1 asap. (I have no idea if that is the reason you are having an issue with SVG icons, but running an unsupported PHP can create unpredictable results).

If that doesn’t resolve your issue please fill out sections 1 and 2 of this form and I will take a look.

[stevland]

Hi Aaron,

It sounds like you are doing everything correctly. I haven’t encountered this issue.

When you are on the plugins page press SHIFT + O on your keyboard to switch to vanilla osTicket. Let me know if that allows you to configure the plugins.

[stevland]

Hello @devops,

It seems that through the renewal process you somehow registered a 2nd account (with a new username and password) which is the one that now has access.

Have you figured this out? I assume you have and you’ve started using the new account.

If not I will delete the new account and apply the access your original account.

Let me know what you prefer.

[stevland]

Hi Koen,

osTicket Awesome fully supports the OAuth plugin, but that’s not exactly what you asked.

You’re wondering if the plugin will continue to work after migrating to osTicket Awesome without any further intervention.

That is a good question, and unfortunately I don’t know the answer. I haven’t used OAuth myself in years.

But I would assume that all of its settings are stored in osTicket’s database, which will remain the same.

If you follow the instructions, the URL for your installation will remain the same as well. So that shouldn’t be a problem, either.

And, given that the subject of OAuth arises so rarely in this forum, I would guess that it requires minimal fuss—if any—after migrating.

The only additional advise I can think of would be to go into the plugin settings before migrating and record / screenshot all of your configurations, just in case you run into any issues.

I hope this helps!

[stevland]

Hi zwing,

You don’t run into this issue while using the 1.18.1-1 Demo, correct?

So the question is: what is wrong with your environment or installation?

Troubleshooting on a mobile device is quite limited.

So visit the installation using a desktop browser (I recommend Chrome for this).

Press Control+Shift+J to open the Console (Command+Option+J on a Mac).

Resize the left panel (containing your installation) until the navigation icons disappear).

What errors (if any) appear in the Console?

Also check your apache logs for relevant errors.

Let me know what you find.

[stevland]

This is definitely not an osTicket Awesome issue.

I recommend you either research this as a vanilla osTicket query, or ask for advice in the osTicket forum.

Good luck! 

[stevland]

Which language pack? 

[stevland]

Hi Erick,

This is just a quick message to let you know I will look into this soon and get back to you.

[stevland]

So that suggests to me that this isn’t actually an issue with osTicket Awesome, but rather something amiss with your installation / web server.

500 Internal Server Error is very generic. The only way to get more information is to look at the Apache logs for clues. Look for entries that were recorded at the time you tried to create the ticket.

But often the cause is wrong permissions.

Please refer to the 500 Internal Server Error and What file and folder permissions do I need? sections on the Troubleshooting page.

[stevland]

Press SHIFT + O to switch to vanilla osTicket and try creating a test ticket. Does that work?

[stevland]

Sorry to you both, but I cannot reproduce this issue and I have absolutely no idea what could be going wrong.

In order to try and figure this out I will need access to one of your installations.

Emily or Javier, if you’re willing to let me log into your osTicket please fill out Sections 1 and 2 of this form:

Assistance Request Form

[stevland]

Hi guys,

If you switch to vanilla osTicket by pressing SHIFT + O you will see that this is not an osTicket Awesome issue.

 

See also:

https://github.com/clonemeagain/attachment_preview/issues/63

[stevland]

Hi servo,

Fair enough. Sorry again for the oversight. 

osTicket Awesome for osTicket 1.17.5 (Revision 2) is now ready on the Downloads page.

[stevland]

Hi @servo,

I apologized for the inconvenience. 

The truth is that I don’t test 1.17.x versions as rigorously because very few people download it. Most users stick to the latest stream—which currently is 1.18.x—and that is what I recommend to use.

Having said that, I should have caught this issue. Thank you for bringing it to my attention. I will need to prepare a osTicket Awesome for osTicket 1.17.5 (Revision 2) release to address this. So please standby for that (I will update this forum entry when it is ready) or consider upgrading to osTicket Awesome for osTicket 1.18.1 (Revision 1).