That sounds strange. Your apache/nginx error log should give some insight
into what's happening. A white screen means it probably died before Bugify
was able to log anything - but still worth checking the Bugify log.
I apologise for the lack of response. Bugify is an after-hours thing, and
since having a baby and building a house my time has been very sparse,
which isn't fair for purchasers of Bugify.
I don't know what the issue might have been sorry, but i'm glad it works
with a fresh install. You can use your other db with the new install. If
it's SQLite just copy the old db to the new install location, or if it's
MySQL just update the config with the db name etc.
Yeah, I get it man. Just went through something similar (got a 3 year old now...yikes!) so I get it. But without knowing that, it's hard to sit around without getting somewhat irritated. Communication is everything!
I love Bugify because it's the only quality, self hosted ticketing system out there (RedMine is clunky) so I am bummed to hear it's not a major focus for you guys. Is it still in active dev or is it going to eventually peter out? Just planning ahead before I invested too much more data into the platform.
I'll try the new install with the old DB...great suggestion. That will rule out one or the other! I'll post back with my results.
Ok, just tried the old DB with the new install...same issue! So that rules out file corruption and leads to some kind of DB issue. Be damned if I know what it could be, though. I suppose I'll cut my losses at this point, unless you have a light bulb turning on as to what what cause something like that...
If SQLite, are the permissions on the db file the same as other files in
the Bugify folders? Is MySQL an option for you? MySQL is going to be much
more reliable than SQLite just because of the nature of the database and
how the different technologies work. It is possible to dump the data from
SQLite and import it into MySQL.
Well, the plot thickens. It was working, not I'm getting the white screen again. It's a standard MySQL DB hosted on a shared hosting account (SiteGround).
I'm wondering if perhaps it's a memory issue? Are there any specific php config attributes that are required, such as a minimum memory or post size that I can adjust via php.ini? It's really odd because it does post, but just gives a white screen. Large images are truncated, which made me think it might be a memory issue.
I suppose I should have been forthecoming that this all started when I migrated to Siteground from another host, but I figured it was something I did during the migration process, especially since the error logs are clean.
Sigh. I understand this might be outside your support...so if you need to get back to daddy mode, it's all good on this end. I suppose I need to take this up with the host...oh joy...you know how that goes!
Ugh that makes things much more difficult. Nobody likes being told it's an
issue with your host.
Bugify checks what the max upload size is and doesn't let you upload
anything larger than that. Anytime you get a white screen though, you would
expect there to be a log in apache (or nginx, whatever your web server is).
That would be a good question to ask SiteGround (how you can turn on error
logging for apache, or why you see a white screen but nothing is logged).