I understand that; my suggestion was for the way that this is handled to be modified so that the initial ID given when the theme is submitted is simply a temporary "pending" ID and that the final ID that is assigned to the theme (the one actually used when displaying the theme on the site) isn't actually assigned until it's approved. Basically, store pending themes and approved themes separately in the database.The value is automatically generated at the time the data is created in the site database in the ID field.
The process would continue in the same way.I understand that; my suggestion was for the way that this is handled to be modified so that the initial ID given when the theme is submitted is simply a temporary "pending" ID and that the final ID that is assigned to the theme (the one actually used when displaying the theme on the site) isn't actually assigned until it's approved. Basically, store pending themes and approved themes separately in the database.
It doesn't occur with any other browser and it obstructs the lower half of the page. Help?An error has occurred. Your useragent is Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
Script error. in at line 0
Well, it works fine if I use Inspect Element to remove it. But if I, say, run a search, it comes back! Just fix it please. Chrome runs slow for me, and I can't upload on my mobile device.@sks316 Probably because you're using Edge. I only support Chrome & Firefox