#Id_card

1 messages · Page 1 of 1 (latest)

peak olive
#

Just moved over to Qbox and trying to buy an id_card or driver_license and im getting this error

peak olive
#

yeah not sure what i messed up, even tried a fresh install of qbox id and im still getting the same error

gusty meadow
#

What script? I'm guessing the id card item isn't being created properly (with the right metadata)

peak olive
#

qbx_idcard

gusty meadow
#

I mean what script are you using to buy it

peak olive
#

its just the standard qbx cityhall

gusty meadow
#

May not work well as the script is WIP. Take a look at how core gives you id card as a starter item for reference on how to do it.

peak olive
#

yeah it looks fine to me so i will have to do some more digging

gusty meadow
#

Believe this is actually a regression of v1.18.0, try downgrading your core and ox_inventory version and seeing if it works

peak olive
gusty meadow
#

Start over? That shouldn't be a big deal to switch between versions. We'll most likely release a new version in the next few days with fixes for this if you just want to wait

peak olive
#

i use zap hosting so the only way i know to switch is to re install the server which wipes what is already on

#

but i can wait for a fix, not a huge issue tbh

gusty meadow
#

Ok. ZAP doesn't give you access to your files?

peak olive
#

yeah it does

gusty meadow
#

Ok, for future ref you would re-upload qbx_core ignoring the config files to downgrade.

#

You'll have to do that when upgrading as well.

peak olive
#

ah so i dont have to use txadmin template? cos thats how i installed

gusty meadow
#

That's good for getting all the resources initially setup, but then when you want to upgrade or modify an individual resource, it doesn't make sense to change everything. You can just change that one resource.

peak olive
#

yeah i wasnt sure if it was all linked, im still new to all this so very much learning as i go

#

at least i know its not a me issue and that u guys are aware of it

peak olive
gusty meadow
#

Thanks for confirming. We identified the root cause and a fix is waiting for next release