TCH-Dick

You can use the following regex for the IPs you listed: 5\.39\.121\.\d{1,3} If that doesn't work you can try: ^5\.39\.121\.\d{1,3}

Hi, We do not provide public copies of our config files nor do recommend you use a full copy of the servers php.ini as things can change on the servers and would break your site quickly. The best way to take advantage of using php.ini is only to list and modify the services you wish to change.

We understand the frustration with Fantastico and to be completely honest have consider replacing it over the past year. However, we chose to hold off for the next major version which starts its beta in the coming week. We are looking forward to testing this new version as it "makes it possible to upgrade as soon as a script update is provided by the script developer". This means we can roll things out from our end without having to wait on Fantastico to provide us with updates. We will keep everyone updated once we have full access to the new version and have done some testing.

Hi laurin, We would love to insure our servers are running the latest versions of services like PHP, unfortunately, the reality of that is we have always done what we can to insure the largest amount of our client base is always supported. The truth is that we could flip a couple options and have any of servers up and running on the latest version within minutes, however, that would result in an unacceptable amount of clients having sites that no longer work. We have made large changes in the past, such as the move away from PHP 5.2, which caused so many issues for clients that we rolled out our own dual version setup for PHP 5.2/5.3. This type of setup is not supported on cPanel servers and you will find very few hosts that do so. When we made this last major change to all servers, we defaulted all existing sites to PHP 5.2 via .htaccess and all new sites would default to PHP 5.3. While this solution itself still resulted in issues for some users, it gave all our clients an option on what version they would run. We have since run tests when introducing new servers to see what affect running only one version or forcing a change would do, and we were not happy with the results. Having said that, back in August of 2012, we received two requests for PHP 5.4 from clients who happened to be on the same server. One of those requests came from you in the way of a forum post made by you. At that time that server was rolled out to new setup running 3 versions of PHP and a notice was sent to those requesting the change. I personally sent the following notice to you about this via the forums PM system on how to make use of the separate versions. This testing setup for PHP 5.4 is still available on your server if you want to use it. We did our testing on this server as well and were not satisfied with the PHP 5.4 setup, therefore we never officially rolled out or announced the change back in August. We have since moved on to testing on our testbed servers and have rolled out two more separate setups based on the recent changes in cPanel. Our next step will be to decide if we want to continue on with a 2 or 3 version setup. I can not provide a clear date at this time on when we will begin our next roll out but we are in the process of planning that. I am sorry if this a bit long winded, I wanted to address this to you directly as well as cover things for others that may read this. Please let me know if you have questions about this or any of our server setups and I will gladly address them. Thanks.

I forgot to add, Server Name is just an identifier and can be whatever you prefer.

Hi sheryltoo, Here is a picture of my setup, let me know if this helps.

Welcome aboard Mike!!

It all looks OK my end. You try resetting the font options?

Unfortunately, I have to agree with you and I am reviewing this with our techs to insure it was handled properly and that you get a proper update.

Abraham Lincoln: Vampire Hunter

Welcome aboard Mike!

set the following in your .htaccess, adjust to your username and path to the php.ini you want to be global. With php.ini in root of site >suPHP_ConfigPath /home/CPANELUSER OR with php.ini in public_html >suPHP_ConfigPath /home/CPANELUSER/public_html

php.ini files only affect the directory they are in unless you set it site wide via .htaccess, It will also only affect php info in the same manner, as well as it will not affect the php info that is provided in cPanel itself. Please let us know how deep you want the changes to affect and if you are using cPanel php info option to look for changes.

All services related to this switch are now back online. If you have are still having issues reaching your site, please open a ticket.

We replaced a bypass switch that was not failing over properly and all network services have been back online for the last 30 minutes. We are still performing some maintenance but this should have no major affect on connectivity.

We are currently experiencing a network outage, which we are investigating now to return services to normal as soon as possible. We will post updates here once we have more information.

Yes, you can do that with no problem. In fact we no longer prorate sales and all new orders renew on the date of purchase versus the first of the month.

All images are now fixed

OK I see whats going on, I can correct that in the database for you. It just looking in the wrong place, the URLS for media and uploads should still point to the path /wordpress.

I added a blank index.html to this directory as it will override index.php, so we don't cause any actual issues to WordPress. Then I created a redirect for the index.html file only, again so it doesn't affect WordPress. Now any one visiting http://www.lauralohr.com/wordpress directly, should end up on the main page. I'm heading out for a while, but please check that out and let me know if you are still having issues.

Are they missing in the admin panel or on your post or pages? What is the name of one of the images that you can not see?

You are welcome and glad I could help, sometimes WordPress just needs a swift kick to get it to do what you want. As for that last error, it should be fixable and I will poke it at in a bit. One other thing though, I did see a couple of issues with your Reviews pages and/or links. They appear to be related to the Thesis plugin, you probably just need to check that any links you set up there now match the new URL.

OK, updated the .htaccess rules as they saved again from the first URL change. It's always something simple that you overlook. Clear your browser cache out or just close and restart it, then poke around. Except for some database entries that need to be cleaned up, reviewing that now, I think it is working as you want.

Yeah, I missed something, but it has been a while since I pulled this off. I am checking for a fix to that issue now.

http://www.lauralohr.com/3008/blogher-2012-my-thoughts-and-critiques/ should be working now but it will take some databases changes to correct the old links. I have some MySQL queries that I can run shortly to make those changes. Also, you can now change your URL settings back to what they were to support the new setup. Which was: WordPress Address (URL) http://www.lauralohr.com/wordpress Site Address (URL) http://www.lauralohr.com These settings translate to WordPress Address (URL) = Install path and Site Address (URL) = URL you want to display. To get to this point I removed all the redirects in your main htaccess and deleted the /wordpress htaccess. I then added the WordPress rewrite rules to your main htaccess. Finally I edited the main index.php in public_html to be require('./wordpress/wp-blog-header.php');