-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom form missing #56
Comments
Did you look at other closed issues? It sounds similar to some others that have been resolved. |
Thanks for responding. I actually did try a number of possible resolutions which I compiled below. Apparently, the issue I'm getting isn't related to most of it. I tried to reinstall osTicket and installed the latest version of the plugin, however, whenever I enable the plugin I keep getting the database error and there's nowhere to find the equipment form as shown in the attached screenshots. The error is most definitely not about an outdated MySQL instance as I have the below server information in place. Server Information Possible solutions tried: After working on the possible resolutions, I'm still stuck with the below error implying an incorrect SQL syntax as show below. Not sure where to start but given that it is your code, perhaps we can get it fixed as I see it to be common on most installation. Thanks for your help.
|
Sorry for a late reply. I was out for holidays. So this one sounds exactly like #54 which was fixed in the upstream. Are you sure that you are using upstream code correctly? |
I WAS getting this error as well. I believe the only difference between the release version and the current commit is where some of the SQL prefixes were changed from hard coded "ost_" to %TABLE_PREFIX%. which would have caused the problem for anyone using non-default table prefixes. That was not the case with me, however. Turns out, /scp/system.php->Information shows that my dev environment is running version 1.8, because I had cloned it from the wrong repo. |
^ hmmm, same error after reinstalling v1.10, "Table 'osticket.ost_ticket_event' doesn't exist". Is this an artifact from a previous version that exists when you upgrade but doesn't from a fresh install? |
|
I get this error also. Can someone help me on this. Thanks |
Good day! I just did a fresh install of osTicket and the latest version of the Equipment plugin. I believe I was able to follow the installation instructions religiously but for some reason, I wasn't able to locate the equipment form. Any help is much appreciated.
Below are the specifics of my environment in case you need it.
osTicket:
Server Information
osTicket Version v1.10 (901e5ea) — Up to date
Web Server Software Apache
MySQL Version 10.1.14
PHP Version 5.5.35
EquipmentPlugin
OSTEquipment Plugin 1.9.4
Additionally, I also bumped into a database problem. For some reason, the below error is visible on all the pages in osTicket.
"[ALTER TABLE
afa5_equipment
CHANGE COLUMNname
asset_id
VARCHAR(255) NOT NULL , ADD COLUMNstaff_id
INT NULL AFTERis_active
, ADD COLUMNuser_id
INT NULL AFTERstaff_id
DROP INDEXname
] You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'DROP INDEXname
' at line 5[CREATE VIEWafa5_EquipmentTicketView
AS selectafa5_equipment_ticket
.equipment_id
ASequipment_id
,afa5_equipment_ticket
.ticket_id
ASticket_id
,afa5_equipment_ticket
.created
AScreated
,afa5_equipment
.category_id
AScategory_id
,afa5_equipment
.is_active
ASis_active
,afa5_ticket_status
.state
ASstatus
fromost_equipment_ticket
left joinost_equipment
on(ost_equipment_ticket
.equipment_id
=ost_equipment
.equipment_id
) left joinost_ticket
on(ost_equipment_ticket
.ticket_id
=ost_ticket
.ticket_id
) left joinost_ticket_status
on(ost_ticket
.status_id
=ost_ticket_status
.id
)] Table 'u973160515_vemeq.ost_equipment_ticket' doesn't existError parsing SQL schema! Get help from developers (#4)
Upgrade configuration error. Unable to upgrade database tables!"
Thanks in advance!
The text was updated successfully, but these errors were encountered: