[stevland]

Hmmm. I can’t seem to reproduce this issue.

Within the demo I am able to successfully create new users, register them and then delete them. 

I have done so, without issue, using Chrome, FF and Edge.

Are you using Safari by chance? I can’t think of what else to try at the moment but I’ll keep thinking about it.

[stevland]

@thomas.mccall

This is my first time encountering anyone using an alternate table prefix. I wonder why you guys decided to go with that? Anyway, it appears that osTicket itself can accommodate that but my sloppy less aware code cannot.

The fix should be simple enough, and I’ll bet you have already figured it out yourself.

Simply add the xy to all instances of ost_ticket__cdata. It only appears twice between two files:

\include\staff\templates\priority.tmpl.php
\scp\priority.php

I’ll try to figure out how to call this table using the same method that the osTicket’s devs use. Hopefully I’ll have a fix integrated into the next release.

[stevland]

@astrialearning

Please see the 2nd item on the following page to resolve your issue:

https://osticketawesome.com/troubleshooting/

[stevland]

Sorry for the delayed response.

I can’t seem to reproduce that issue using 1.10.1-v.1.4, so I would suggest upgrading to that version or something newer.

You can verify that the Register and Delete User buttons work on your end by using the demo:

https://osticketawesome.com/1.10.1/scp/users.php?id=1825

I hope this helps.

[stevland]

Using the \support-old installation, do the pages also have trouble loading or does the system perform as one would expect?

[stevland]

I am happy to help, @cbasolutions.

But for this type of sinereo especially I really feel that you need a working osTicket core installation.

All you need to do is download the 1.10.4 .zip, upload the /upload directory, rename it (optional) and copy over your working /include/ost-config.php.

BTW I also have some other tips for working with mods.

[stevland]

I’m sorry, you were correct… I was confused about what I was meant to be checking and my screenshot is actually from login.php.

You are also right with regard to the auth button/ link not showing up in view.php. I hadn’t noticed that the auth function was not present from this page.

However, I also installed the Google oAuth plugin in a unmodified osTicket 1.10.4 installation.

Here also the Google oAuth function is not available on the view.php page.

Here for your reference:

After considering this my interpretation is that the osTicket devs excluded the auth code from view.php intentionally… the page is meant for looking up a ticket using the ticket # and, I assume, if the user wants to select a different authentication method the idea is a) they will click the “Sign in” link and b) they would not likely have ended up on the view.php page in the first place.

I hope this helps.

[stevland]

So I installed the stock Google oAuth plugin into a copy of osTicket-Awesome-1.10.4-v1.0, configured and enabled it. It appears to be cooperating with the theme, so I don’t suspect that the theme is breaking anything. I hope this help you narrow down your focus in your effort to also have your custom plugin work with osTicket Awesome.

 

[stevland]

I’ll install the Google oAuth plugin and have a look.

[stevland]

Are you trying to use the LDAP plugin, HTTP/Webserver authentication or…?

[stevland]

@sgps,

UPDATE: This issue occurs on both of my unmodified 1.10.2 and 1.10.4 installations which both use my demo database.

https://osticketawesome.com/u-1.10.2/scp/tickets.php?a=open
https://osticketawesome.com/u-1.10.4/scp/tickets.php?a=open

Therefore I thought it was pretty clear that the issue is with these versions of osTicket core.

But ntozier (from the osTicket Forum) tested a 1.10.4 installation and reports that there is no issue on his end.

So I am confused as the source of this problem and actually I am mortified.

As it happens I am about to board my 2nd flight and I am starting a two-week vacation. I will have limited connectivity but I will try to look into this deeper as soon as possible.

In the meanwhile, unless you can think of a work-around I imagine that this would prevent your agents from working efficiently. The only suggestion I can offer is to revert back to osTicket-Awesome-1.10.1-v1.4 for now.

I am sorry for the inconvenience! 

[stevland]

@sgps

Thank you for pointing that out. I can’t believe I hadn’t yet noticed that the user search is broken.

It isn’t an osTicket Awesome problem though… it is also happening in osTicket 1.10.2 core and osTicket 1.10.4 core.

I may not have time to open an Issue on Github as I am catching a plane this afternoon. But I will as soon as I can if you don’t beat me to it!

[stevland]

I’m sorry, I’m at a loss. I can’t see anything wrong or think of any reason that your system is loading irregularly.

I see that your osTicket Awesome is installed into a directory called \support.

Did you follow the installation instructions, and do you still have your old osTicket installation in a directory called \support-old?

[stevland]

It is hard to explain what CSRF Tokens are, but it is an osTicket security function. And those warnings are competely normal in osTicket. Notice that you bought osTicket Awesome on July 10th, but the first warning on that page is July 9th. The CSRF tokens have nothing to do with osTicket Awesome or this issue.

I only see one DB error, so that seems okay. But please post what it has for details.

[stevland]

You posted the same information as before. Please post your System Logs (Admin Panel > Dashboard > System Logs).