This is follow up update on original post here
I was doing maintenance today and WOW! I now see that PHP 7.0 and 7.1 are now supported by goDaddy
THANK YOU
Off course we have to check site to run under latest PHP version and off course there could be some work required to fix issues if detected, but one need to move with the progress and be modern.
It is unfortunate that it takes goDaddy months of complains to catch up with rest of the industry, but better later than never.
SPOILER: This is intended to be rant
Yes, GoDaddy was around for many years and have thousands if not millions customers using them.
Yes, I am using and was helping with their hosting on number of sites and for number of years, hence first hand experience.
Yes, pricing could be considering being good.
No, I would not recommend them to anyone.
No, they are not competitive offering anymore.
No, I would not trust them to represent my best interest hosting my site.
This is why:
<end of rant>
Conclusion: if you are looking for web hosting, don’t look at GoDaddy, look elsewhere. There are more modern offerings around there from other reputable companies and with more bang for the buck
+ Translation improvements: CZ, LV, NL
+ Bootstrap CSS updated to 3.3.7
+ ADMIN: Small css improvements
+ Fixed issues with menus in various modes
+ CSS: Fixed issues with login page colors for controls
+ Added ID for download link
This is really a short note but may require some thinking when one run into it… so there you go.
Let me start by saying that I do have strong preference sub domain based WordPress Network instance over sub-folder.
In my opinion it is easier to maintain, and allow to manage stronger security.
Ok, “what is the problem?”, you ask.
Let’s say you have setup your blog as sub-domain to your main site. It may be the same machine or different instance altogether.
You run it for a while and there come time when you decided you want to host second blog and want to share the same WordPress instance.
Multi site support in WordPress is for a while and it is easy to setup and easy to maintain.
For most part that is it – simply follow these steps.
But there is a catch, if you run blog on the sub-domain, network setup wizard would warn you that you cannot enable network using sub-domain.
Not a problem – modify your wp-config.php by adding the following lines
/* Multisite */
define( 'WP_ALLOW_MULTISITE', true );
/* Multisite */
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
define('DOMAIN_CURRENT_SITE', '<your-domain-name>');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);
Now you can logoff and log back in and you should be able to create new sit using different sub-domain.
This is not all – what you will most likely run into is inability to use the same users across both sites.
Note: It is important to understand that by using the same names across multiple sites you may slightly reduce your security protection.
So make sure that you are:
- Keep your Network instance up to date with updates
- Using Security plugin like iThemes Security
- Change admin user to something other than “admin”
- Protect site from brute force attacks
What could happen is that when trying login to second site or switch between sites from Admin panel you would get message that your browser does not support cookies or you will not be able navigate to second site’s Dashboard.
What is the problem? Problem is how WordPress maintains user session using cookies.
To fix it add one more line into your wp-config.php file
define( 'COOKIE_DOMAIN', $_SERVER[ 'HTTP_HOST' ] );
Now you should be all set
If you one lucky user of GoDaddy shared hosting, well… you are in luck…
GoDaddy uses most awkward Control Panel setup on the market when it comes to site setup.
Usual site setup consists of two common tasks:
Usually if one wants to have more than one domain one would make deployment of each site in sub-folder of the root FTP.
Grand idea of GoDaddy is that they want you to have only one site per one domain associated with any hosting package by disallowing association of the top level domain with sub-folder as mentioned above.
Technically you are not prohibited from acquiring more domains or doing anything else, but you would run into situation that support team would play coy about how to set everything up.
You will be out of luck of trying and escalate issue – “this is how it is done, and you cannot do anything about it”…
Once in a lifetime you may run into support tech who may spill the secret steps:
Enjoy
+ ADMIN: New option – Include “Click to Enter” link for Root Page
+ ADMIN: Small style improvements for styles and menu support
+ CSS: Added theme-<colorpack> class to body element allowing individual styling with 3rd party plugins
+ CSS: Small style improvements
+ Translation support: Added he_IL, th_TH, el_GR, zh_CN language
+ Added support for translation of Home Page Quote
+ Bootstrap CSS updated to 3.3.5
+ ADMIN: Small style improvements
+ ADMIN: New Main Menu Mode: Static Menu – Header Right
+ Translation support: 46 languages added
+ Bootstrap CSS updated to 3.3.4
