wolstech
-
Posts
17,966 -
Joined
-
Last visited
-
Days Won
675
Everything posted by wolstech
-
The regular mysqli library doesn't do that, it gives an error that doesn't include the actual line of code...can't speak to PDO, but if it really dos that, that's some poor design of PDO's errors.
-
I've never viewed it, so I don't know. The TOS and Wiki didn't even exist when I first came around back in 2009. I was here for a few months, left, came back in 2011 and been here since. The TOS Wiki page was written right around the time I got my 2011 Stevie account. I wouldn't be surprised if it was though. In other news, looking at the history, I thought the examples under what won't be tolerated in this TOS rev were a bit funny: http://wiki.helionet.org/index.php?title=Terms&oldid=284
-
I actually checked in that backup already. The whole directory tree where that content should be is there but empty (except for a license for a font). No luck there (guessing the files failed to back up). Wayback Machine and the like don't have it either (robots.txt told them to not archive it). The only thing I've found that's a "Support FAQ" was this old forum post: http://www.helionet.org/index/topic/5055-support-faq-read-this-first-updated-050111/ (most of this is already on the Wiki now).
-
That's what I figured on the Terms. Otherwise random person would come along and add a clause allowing phishing or something. The main page is probably just to prevent defacing... Either way, it works now. Thanks again @bdistler: The support FAQ link has been removed from the Terms. If anyone manages to find that content, let me know and I'll stick it on Area52 and put the link back
-
Yes I can. Thanks.
-
Nope. Still says I don't have permission. The two pages I can't edit are the two on this list: http://wiki.helionet...:ProtectedPages (and it won't allow me to unprotect them). It looks like you might need to either remove the protection or give me the ability to edit protected pages...
-
I don't even see the Edit tab. I see "View Source" instead when I look at those pages. If I click that it says:
-
You have to create a database called barcode in cPanel first. You cannot create databases through PhpMyAdmin.
-
If you're on Johnny, that's normal. Johnny server is not very fast and can also be unstable at times. Johnny is meant for testing/experimentation. We allow unlimited registration on that server, but this also makes it prone to overloading and being abused. Notice the load and response times of Johnny vs. Tommy on this chart: http://heliohost.grd.net.pl/monitor/ Johnny has suffered 3 different high load events today. If you need fast and reliable service, you should sign up on Tommy instead. Tommy doesn't typically see such events because we limit the number of users that register per day, limit the number of load-inducing features available (ASP.NET is request only, no Rails support) and more tightly control how many resources can be used before accounts get suspended. The server is also significantly more powerful (Tommy runs on much newer hardware than Johnny).
-
If that's the concern, just put @ in front of the connect statement line (e.g. @mysql_connect. (An @ prevents a single line from producing errors). I run numerous websites in production (several of which are hosted here), all have their errors publicly visible, and have never had an issue. Also, I've never seen a password appear publicly as a result of a crashed/erroring DB server, something which, back when we had Stevie, was a very common occurrence. The errors just show usernames, usually dbuser@localhost. We do not consider usernames to be sensitive information (we ask people to post them all the time).
-
There's probably no way to do it, but you can test to see if the log still generates with this option set: See if an error_log file appears in your script's folder after there's an error. Then delete the log, add the error_reporting(0); and try it again. Many of us prefer the errors shown anyway (you're actually the first in a long time to ask to turn them off), since it helps users report bugs in applications. Would you rather get an email saying "It doesn't work when I try to log in" or an email saying "I tried to log in but it gave me an error about some unexpected ')' on line 37"? The latter is much a more useful report than the former in my opinion...
-
Accounts on Tommy can take up to 24 hours to start working again once they're unsuspended (Apache has to restart, which generally happens around midnight UTC when registrations open, or when any user adds or removes a domain).
-
That account is not actually suspended, but it probably needs an apache restart to get rid of the suspended page. Did you just renew it? Give it 24 hours, if it's still showing suspended after that, I'll escalate it for you.
-
Add this to the top of your PHP files (I recommend doing it in an include that's used by everything in your application, like a DB config file, so it only has to be done once): <?php error_reporting(0); ?>
-
Users are still getting the server crash message when they attempt to renew Johnny accounts that have gone inactive. http://www.helionet.org/index/topic/27899-suspended-fjjodor/
-
That script should've been fixed over a month ago. That message is no longer applicable. Manually Unsuspended.
-
HTTP. You have to set up SSL in cpanel if you want to use https. It is working now for me as well. Please clear your cache if you still see the queued page.
-
That account is indeed inactive. It can be renewed at https://heliohost.org/renew/
-
You signed up today. It takes up to 24 hours for domains to start working on Johnny.
-
This is a known problem with PhpMyAdmin through cPanel. The best way to make PHPMyAdmin faster seems to be to install it on your account through Softaculous.
-
The queued page is gone on that account now. Please clear your cache if you still see it. The software in question is broken though. We no longer support XCache: http://www.helionet.org/index/topic/27712-xcache-on-tommy/ (This currently applies to Johnny too, though Krydos does say it might be installable on Johnny).
-
Done.
-
Yeah, going over the limit will get your account suspended. You'll also get suspended if we get an abuse report for your email (which typically is a result of your email being flagged as spam...AOL addresses are especially well known for being report-happy). It is possible to have the limit raised, but you'd need to specifically request it and have Krydos approve of the reason for the increase and show it's necessary (hitting the limit with non-spam email would qualify). We can also throttle the email on your account instead if it becomes an issue (e.g. limit to a few emails per hour). We unfortunately have to be very picky with the email service since our servers (especially Johnny) sometimes get abused to send spam or set up phishing sites (which typically also send spam to get people to visit them). We're one of very few free hosts that actually offers usable email service though. Most either disable it entirely or limit it to something unusably low (I know one with a limit of 1 email every 6 hours).
-
I merged the old iAbdullah account into the abdu1 account. I then renamed abdu1 to iAbdullah. Please let us know if you need anything else
