TCH-Dick

Glad to hear you got an answer and sorry for the slow reply. Just in case anyone else comes across this, here is the short answer: -Log into your cPanel. -Locate and click the Email Accounts icon. -At the end of the fist text box(where you enter the new email@ name)you will find a dropdown box. -This dropdown will contain a list of any parked domains as well as any sub domains you have created. -Select the domain you want to use and complete the new Email Account setup.

Happy Birthday!

It's not so much a preference as it is a recommendation to prevent issues for the average user. This is because most of the time someone is looking to make a change to a specific script, were as setting a php.ini file can have a broader effect if set for the entire site. Depending on your needs you may use either, but note that there are caveats in using either method: - php.ini files are directory dependent, adding a php.ini to public_html will NOT affect directories below public_html. If needed site wide, you must add the proper entry to .htaccess ****using the site wide php.ini method via .htaccess can have an affect on cPanels tools such as the redirect editor. Once you choose this option you would need to edit redirects via the file manager. - .htaccess php flags do not directly translate to the same strings in php.ini, for example: htaccess php_value(upload_max_filesize 64M) is not the same as php.ini (upload_max_filesize = 64M) - .htaccess is limited in what options can be set - .htaccess files normally have a recursive limit of 2 directories, therefor for entries to affect a script deeper than 2 directories, a new .htaccess file may have to be added to the deeper directory.

Thanks for again for your patience during all this and we are going to start making more use of the twitter account. We have also started some changes to insure regardless of any issues, clients can still monitor things. We will complete those changes in the coming weeks and as always we will announce them.

Please see thread http://www.totalchoicehosting.com/forums/index.php?showtopic=41259 for detailed information.

I hope you don't mind but I split this off into its own thread. We are still working on this issue for a remaining server (ambria) and I assure you that we will post more information as soon as possible. Thanks for your patience during this issue and you can also find updates at http://twitter.com/#!/totalchoicehost

Reseller hosting is a bit of a different beast, therefore there were no price increases. However, the plans did increase the same day as the shared plans. You can view the new reseller plans at http://www.totalchoicehosting.com/web-hosting-resellers.html . If you are not seeing the increase please contact the help desk, as your account my not be configured to our current setup.

Suppressing with @ does work, but I prefer to use trigger_error() to output custom errors without exposing too much.

Due to the numerous requests to revert the change in the log in method, I decided to review this issue further with the entire TCH team. We have determined that is no no real security implication compared to the cookie only method. Therefore we are currently restoring the old "pop up" method at this time. Concerning issues with web mail, they are possible related to recent updates in the versions provided by cPanel, but are unrelated to the login changes. If you are still having issues with your web mail please drop a ticket in to us and we will dig deeper. Thanks

Hi jberg, Sorry for the late reply and you nailed the reason why. This change was part of the recent cPanel update and its new security policies. We know that sometimes these changes can be a real pita, but we do our best to insure we try to balance security with usabality. I appreciate your feedback though and hope you don't kill us for the change. Please let us know anytime you have concerns, like, or don't like something. I can't promise we can always change something or even revert a change, but I assure we will listen with an open mind.

Hi, You fill out that form for account cancellation. It only has a place for the domain of one package and only the package you list will be canceled.

You are not being a pain at all. As for billing department it is not open on the weekends, but it is checked occasionally. The most likely cause for not receiving an immediate welcome email is having an outstanding invoice. Unfortunately, this would include any invoice that is up for renewal for the upcoming month. This is something we are looking into to prevent and someone is reviewing your new order now to get your welcome email sent out.

You would use the path /home/cpanel_username/public_html/downloads/filename

Tim, Sorry to hear about your bad experience with Noah's Classifieds, but your post has been removed. Hijacking threads to post the same complaint you have posted all over the net, just doesn't work around here. You are more than welcome to join our community but please don't just use it to drive your little campaign. I seen your same post in the WordPress forums this morning. I man come one, really? What in the world does WordPress have to do with this? Good luck.

Happy Birthday

Have you tried the Web Disk option in your cPanel under the Files section?

Unfortunately that type of access is not provided in a shared environment as it just results in problems for other users. If you continue to have issues, feel free to open a ticket with the help desk. Short of trying to use htaccess to host more than one site, which is a TOS violation, we will gladly assist with any rewrite issues.

These directives are not allowed in .htaccess, please see httpd.apache.org/docs/2.0/mod/mod_rewrite.html#rewritelog . Most errors will show up in your cPanel under Logs > Error Log, if you are not able to find an issue there you will need to open a ticket.

When you say "doc" I assume you mean MS Office or one of its components? If this is the case, support for animated gifs was removed a few years ago when they replaced IE for rendering certian objects in Office.

We will get this fixed, however, please note that you can check the PHP version in your cPanel. This will be listed on the left hand side of your main cPanel page under the Stats section.

Sure and the only change will be on the back end. We will simply disable support of the old style passwords(temporarily so we don't break other users sites), then using the current database username and password, we will recreate the password using the new style mysql passwords. Once this is done your local setup will connect as usual with no change on your part and you will be able to properly connect using your external setup. This change is something you can actually run from phpmyadmin, however, since you cant actually disable support for the old style passwords, it would have no affect from your end.

Please open a ticket to my attention, along with the database name, user, and password. This issue is commonly related to the old style passwords, which we unfortunately can not disable or it would break a lot of sites. Once I have this information I can correct this issue for you.

No updates to the server should cause that specific issue as its reference to a configuration in the database tables(which are created at the time of install). Also that fix seems to be a few years old and may not apply to your version of phplist. Please open a ticket with the details of your install and we will gladly look it.

Greetings, We are now in the process of updating all shared/reseller to PHP 5.2.14, however, there are some major changes being made to our setup. The primary change being that we are migrating our PHP Handler setup from DSO to SuPHP for added security and to make the use of PHP more user friendly. So what does all this mean for you? PHP scripts will no longer be ran or owned by the user "nobody", you will now own all of your files and those created by your scripts. File & Folder Permissions are now easier to work with and more secure. You no longer need to have directories or files set to 777 and there is maximum supported permission of 755. Any scripts that require 777 should use 755 instead. Generally, set folders to 755. Generally, set files to 644. [*]php_value and php_flag options no longer work in .htaccess files NO! While this is standard for SuPHP, we found it to be an unacceptable compromise and have implemented an additional option to allow continued use of these options. To use these options they must be enclosed in the container element. Example: php_value register_globals 0 We plan to complete these updates by the end of the month, however, there are no specific dates set per server. Since the downtime will minimal or not all, we will announce each update in the appropriate server thread once completed. As with any server updates, we do expect a small of amount of accounts to have issues. We will do all we can to mitigate any issues, but should they occur we will be here to assist and correct. Thanks your for time and please let us know if you have any questions or concerns.

Hi pickupman, This issues seems to be even worse with the latest release and is something I have been discussing with rest of the team for the past week. We started testing the necessary changes to correct this a while back for other scripts and plan to proceed with testing on several servers this weekend concerning wordpress. Once we have more details, which will be very soon, we will update everyone here in the forums.