Question removed as it was 'sorta' answered/non-answered.
It still has some teething problems. I use a Linux system which is very similar to a Mac system in they both have the same core code (but Apple adds a few extras of their own), and had no issues with my system, just ran into some minor problems with the story upload system Lazeez and I have been working on as he has time.
That's what I was afraid of. Since it wiped my system password (never seen that before), I was afraid I might be facing something major (like system file corruptions). Now that my system is finally up (to a system backup performed about two weeks ago), all of my new password manager passwords are also gone, so I've got to have to reset EVERY password I own on a one-by-one basis. I'd back that up too, but once again, hadn't gotten around to backing it up to another machine.
If it WAS due to an issue on the site, it was likely because I was trying to load a cover which was just a 'bit' over the recommended size, so it may be an unhandled error processing issue.
But, as it'll be another day before I recover (as I have to restore my saved files via a separate Time Machine restore), I'm a bit gunshy about trying it again. :(
I'm a bit gunshy about trying it again. :(
Rightfully so. You may have restored your system but the problem their site's code appears to have caused you is still on their site.
If it WAS due to an issue on the site, it was likely because I was trying to load a cover which was just a 'bit' over the recommended size, so it may be an unhandled error processing issue.
I tried that myself and all I got was an error message saying the image was too large. If anything on the site was causing the issue it's likely to be a cross issue of how your system is handling the site code itself. I've hit a few snags with the system and worked with Lazeez to identify and fix them, but it's not caused any problems on my Linux system. Both Linux and Mac are based on Unix so much of the core code is the same and many of the routines are the exact same modules and code. If anything Lazeez was doing on the Bookappy site was causing your issue it would also affect mine, unless it was something that only affected the Mac specific code Apple have. I doubt that as Lazeez is very Mac centric and tests for those things.
I've NEVER had that happen (machine-wide app failures) on a Mac EVER, and I'm at a loss as to which resource the site was chewing up. I was trying to post a 'almost-the-right-sized' cover, so you'd THINK it was memory. Even Adobe and M$ don't mishandle resources that badly, and they both have well-deserved reputations for screwing with OS resources and crashing programs left and right.
That's not caused by the site. the site has barely any javascripting going. The submission system is mostly html and css. The categories and the calendar are the only steps with javascript.
So whatever happened on your system is purely coincidental to you being on the book upload system. It's definitely not caused by the system. I develop using the Mac so if it was a problem with the site, it would have crashed my computer way before you got to test it.
Also, if you're going to participate in an alpha test, please report issues to me. Nobody on the site here can help you as only few even seen the site.
That's not caused by the site. the site has barely any javascripting going. The submission system is mostly html and css. The categories and the calendar are the only steps with javascript.
I never claimed it was due to javascripts, since my Mac disables them by default, and I have browser add-ons requiring permission for most things. What I suspected (at least initially) was some funky misallocation or a refusal to free resources when done (though that shouldn't impact your site, as that's down by the Mac's browser engines which html utilizes.
For now, I haven't a clue what triggered it, or what corrupted by login database.
As for reporting it to you, I suspected it was likely triggered by something on my end, though again, I've never had a Mac be unable to open ANY app, including Finder, so it's something other than a simple loss of resources. What it may be, though, is beyond me.
That said, I should have done as I often do, and take the discussion off-line, since I figured that both Switch and Ernest would be involved in the program. But again, I didn't want to report a bug if it was triggered by something else entirely. (I'm guessing some system file block got corrupted, screwing with a number of individual system files. When I restored, the bad block would have been isolated and marked as bad, clearing up the issue, but without knowing WHEN the passwords were lost, I couldn't savely restore from a recent backup. As it is, all I lost were a BUNCH of TextEdit notes (I looked up where they were stored the LAST time I lost a newly changed password, but couldn't locate it on a dead system).
I haven't been able to log into it yet. Lazeez tried several things and said I'm in the database, but I still can't log in to test it.
Lazeez tried several things and said I'm in the database
Same email, same password as SOL in the database. I double checked.
You should be able to login. It has the exact code as SOL's log in page too to boot.
You should be able to login.
Ok, I'll try again when I have the time. My wife just found out she needs a knee replacement so I'm kind of involved with comforting her.
I'll respond through the messaging system, though.
Did I just run into a single BAD instruction, or is the entire site that buggy? I had a list of issues, but alas, it was on my Mac (though I had the foresight to save it before doing a forced restart, I didn't have enough to save it on a separate machine!)
I'm a pure Mac user and other than bugs I've reported to Lazeez, I haven't seen this kind of behavior in Firefox or Safari Technical Preview.
(Don't ask about the problems with Catalina! Do not run Beta Software unless you have to, or enjoy pulling your hair out!)