Well, the design of the ticket system sucks big time, I never claimed to be a designer. Having seen my software over the years you must have probably figured out that design and yours truly have taken a divorce. Any designers are more than welcome to help out, just like it happened with Kickstart :)
This ticket system is a huge improvement to the old forum, especially administrative-wise. Do you remember all the threads with people interjecting with an unrelated issue? That's no longer possible.
Regarding the navigation. It's a simple flat structure. Category -> Ticket. If that's difficult to navigate, please tell me why and maybe I can fix it.
The search feature does exist, on the top of the page. The old forum didn't even have any search feature, at all. I know that Joomla!'s basic search sucks (it's limited to 50 results per plugin and the way it mixes results is horrible). Unfortunately, Smart Search is actually Dumb Search: it doesn't support ACLs and ended up showing private tickets (containing passwords and stuff) to guest users. Thankfully, I only tried it with a local copy. In any case, you can always search on Google with "search terms site:www.akeebabackup.com" to fetch results only from this site.
The site is hosted on super fast servers in Dallas. I am across the world (near Athens, Greece) on a measly 7.6/0.9 MBps ADSL line and the site loads consistently in 3.5 seconds. Given the fact that I have a png roundtrip of 200ms to the server, that's blazing fast. Are you on 3G or something? I can't think why a fast site hosted on US servers is slow to load for US clients. It beats me.
Regarding your question, please would you read this page: https://www.akeebabackup.com/home/news/55-general/1453-admin-tools-and-j-2-5-updates.html And now I will explain why repeating myself is bad, quoting myself:
These issues occur because Admin Tools erroneously executes Joomla! update SQL files multiple times. This is a known issue. Please do not file support requests regarding those issues. Having to answer to your requests does not tell us anything we don't know and reduces the time we have available to find a potential solution.
Answering to this thread cost me 30 minutes. All I can tell you is that this is a known issue which is not solved yet. You don't have a solution to your problem. I need another 45 minutes to produce a solution. Wouldn't it be better for both of us if I hadn't have to reply to this thread? This is not sarcasm, it's just pure math. Writing code needs time. Replying needs time. Writing code solves issues. Replying doesn't solve those issues. If you were in my shoes, what would you do?
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!