TCH-Dick

I am reviewing your redirects and general .htaccess setup now. I may be able to sort what you want based on the settings you have listed, just by adjusting your .htaccess and index file.

There could be an issue with how you have you redirects setup so that your install loads from /public_html/wordpress(which is your install path) versus just /public_html. If /public_htm/wordpress is were you originally installed your WordPress, then you having changed your install path. Check out what you have set for WordPress Address (URL) and Site Address (URL) in your wp-admin under General options. As for the .htaccess entries, they should have been added by WordPress, with no interaction from you. If they can not be added by WordPress, you would have received a notice on the permalinks screen. If you cant find the root cause, please open a ticket with your WordPress admin information and I will gladly review the setup for you.

There are so many options and reason to use each option for permalinks that I am hesitant to really suggest one, as it really depends on your needs and desires. However, I recommend reading this excellent article on permalinks, which touches on SEO as well as some caveats that affect things like getting listed in Google News. http://docs.appthemes.com/tutorials/wordpress-permalink-structure/ Concerning that plugin, unless you have changed your domain name or your install path/directory, then I highly recommended that you don't use it. The WordPress permalinks settings and mod_rewrite rules in your .htaccess will take care of everything, That is WordPress will automatically do the work of changing/redirecting http://www.lauralohr.com/?p=123 to http://www.lauralohr.com/sample-post , if some one follows the old style URL. You can see this in action on the WordPress news blog at http://wordpress.org/news/?p=30 .

I am unable to locate a recent ticket for either of your hosting accounts nor should we have any outstanding tickets needing a reply after 3 days for hosting support. Is it possible you sent an email to our domain department for this request? If it was to our hosting desk, then please let me know the ticket # and we will get it sorted for you asap. If you didn't receive a ticket #, then please open a ticket at https://support.totalchoicehosting.com (you do not have to login to submit a ticket) and request that the domain be parked on your hosting account.

We run the latest recommended cPanel version, which removed the user settable "rewrite header subject" option years ago as well as SpamAssassin v3.3.1. If your other host is displaying the "rewrite header subject" option, they are either running an older cPanel version or they are running SpamAssassin in the legacy transport based mode, which is not recommended. We also have the default option of "Global Subject Rewrite" enabled and set to prefix " ***SPAM*** " onto the subject of detected emails. If you see these marked emails will depend on what options you select in SpamAssassin, for example if you choose to Auto-Delete Spam or send them to a Spam Box, then you may never see these emails. There are also additional filter options in the mail section that allow you to further filter emails based on SpamAssassin header information. As with any spam software, SpamAssassin will not catch everything, however, if you still have issues with spam then please open a ticket and we will gladly take a look. .

Did you get this resolved? From what I read the plugin itself adds entries to .htaccess, did you check to see if that occurred?

Congrats, again!!!

The only shared servers we have that are not running PHP 5.2 are those that have recently been restored or migrated, and Alderaan is not one of these servers. However, PHP 5.2 was not working on this server due to recent standard Apache update, which has now been corrected. While we were corecting this issue, we commented out the the PHP 5.2 option from your .htacess so the site would load and it appears to be running just fine on PHP 5.3. Since the site has no issues running now, we have left it on PHP 5.3. I reccomend you leave it running on PHP 5.3, but If you do need 5.2 it is there, just unncomment the line in your .htacces file. I still stand by my statement that "I assure you when the time comes that we choose to no longer support dual versions on any of our servers, and it will, we will make a full announcement." Until then we will look into the source/reason for the blanket upgrade statement by our staff.

Great tip SteveW! We actually see this a lot and sometimes I wish cPanel would force not allowing use of the main cPanel user as a MySQL user. I always recommend that you create at least one separate MySQL user for your databases. If you choose to use the main cPanel user for MySQL, just remember to update your scripts if your password changes. For reference, the following are services that are affected when your cPanel password changes: system(cPanel user password) ftp(only affects access via main cPanel user) mail(the default mail account cPanelUser@) MySQL(only affects access via main cPanel user)

No argument from us on that. If your issues were related to the recent defacement attacks, which I can see that appears to be the case on your Joomla ticket, then our techs should have informed you of such. Failure of that sort will be deserving of some head knocking on our end, that I assure you. However, I do see one recent incendent, that while that site would have been affected by the defacement, the other isssues were due to a site level attack, like ftp or a script. Regardess of the reason on either, if you feel you any of those tickets are not fully resolved or answered, please update them again and requesst review from a mananger.

Thanks to all of your reports and further review, we were able to identify what files we didn't restore during our initial fix. Which as you have seen would be any index file that was not named index.php. We have now completed a new run to restore these files. In order to not undo changes or restores you have already done, this run to into account the following before restoring. -was the file one we logged during our initial fix -if so, was the file missing in public_html -if so, was the file not equal to index.php -if so, was the backup file clean of the defacement -if so, restore Thank you all again for your patience and please let us know if you continue to have issues.

This maintenance was delayed but has now been completed.

Due to this issue we are going ahead with kernel reboots that we had scheduled for June. These reboots are rolling out now 10 servers at at time, A-Z by host name and should have a downtime of less than 5 minutes per server. As always, if there reboot takes an excessive amount of time, we will post to the appropriate server forum.

Mail issue should be corrected, please check it out and let us know if it doesn't work.

Please check now and let us know if you still have issues.

Please check now and let us know if you still have issues.

OK, Checking that now.

Please try your site now and let us know if the issue is cleared up.

While we are planning to phase out PHP 5.2 on all our servers, we have currently only made this move on new servers and those that have been restored recently. We will be making an effort to not have it set as the default for all accounts, however, this would not cause the issues you are seeing. I am now reviewing this with our staff to determine the cause, so we can get your site in working order. As for PHP versions and updating scripts, we always recommend that everyone keep their scripts up to date and do so as soon as possible. We have never moved our systems from one major version to another, such as 4 to 5 or 5.2 to 5.3, without proper announcement or a stop gap solution. I assure you when the time comes that we choose to no longer support dual versions on any of our servers, and it will, we will make a full announcement.

The short answer is, no, vista can not do this. However, there are tools out there, just search for things like vista taskbar shuffle or vista taskbar hacks and you will find a few tools just for this.

Hi jberg, You didn't miss an announcement, as this was supposed to just be routine updates on the servers related to the latest release of cPanel. Unfortunately, it had a negative side effect of updating all DNS zones to our name server clusters, that it in all honestly we just did not expect. Once we were aware of it we stopped the mass updates to our shared servers and are allowing the DNS updates to run out. At this time DNS services are not down, however it may appear down from some locations depending on what DNS server you hit. We do apologize for this and I will look into changing our notifications for even routine thing in the future.

At the time this option was added and I am not aware it changing, SPF can have a negative affect on external forwarding if the recipient does not check the headers properly. Other than that, you should have no issues nor do you need to make any changes to your email client.

Fantastico is maintained by a Netenberg, and they can be a bit slow on adding new software at times. Especially in cases for things like Joomla 2.5.1, as it is not a simple upgrade and requires more of a migration. This is the same issue we seen with Joomla 1.5 and why it is listed as separate installs in Fantastico. We have sent off a notice to Fantastico at this time regarding the newer version of Joomla, but as usual I am not expecting to receive an ETA from them. If they respond, I will update you here.

They sneak up on me every year, so I went for three years this time. Sorry for any issues.