If you have a WordPress site, and you keep your blog updated, you probably want to spread the word through the Internet. A good place to start is Facebook. You can actually sync your WordPress and Facebook accounts so that, every time you post an article on your WordPress site, a link is automatically shared on Facebook.
Using Jetpack to Link your Facebook Account
If you have a WordPress.com site, you have Jetpack installed. If you have a self-hosted WordPress site, you can easily install Jetpack by creating a WordPress.com account and then syncing your self-hosted site to WordPress.com. In either case, Jetpack can be found or activated by clicking on Jetpack on the menu on the upper-left side of your WordPress dashboard page.
After switching from being an addon domain to the main domain, the moving of files were rather smooth-going. Most of the WordPress continues to work. However, there’s one issue that borders me.
Whenever I upload a graphic file, WordPress would create a new folder under the root directory – wp-content/uploads/YYYY/MM/imagefiles.png.
That was not what it should have been. I had move the subdomain to a new DocumentRoot, so the uploading of graphics should be inside the new DocumentRoot and not create a new directory under the root directory.
Though the upload was successful, the files were added to but not showing up in Media Library.
As expected, nothing shows up when I try to insert the image file into a post.
I was rather puzzled. Days of searching for a fix produced no results.
No forum could supply the answer. But from what I gathered, the problem lies with the .htaccess. It may just requires a slight modification, but I do not know how to.
I need a working sample to copy from, I can’t write one myself. The .htaccess is one file I dare not meddle with unless I know exactly what I’m doing.
Further search for “change path media upoad of wp in subdomain” point me to these files:
Close, but not exactly what I was searching for. I wanted the default setting, not help on change to default setting:
It was a search phrase like this “WordPress at subdomain moved to documentroot now upload cannot work” that I got me into this arcticle:
When I read to Step 5, it says,Select “Settings,” “Media” and then change the URL in “Store uploads in this folder” to represent your new URL.
That’s it. I didn’t know there’s a setting for media in the Admin area.
I’ve never seriouly explore this area as different version of WordPress installation shows up differently though they’re updated to the current version.
In the past, I have never depend on this mode of media uploading. I had always upload image files to my manually created images folder and code the path in my post.
This is the first time I am using the drag-and-drop mode to upload images.
Anyway, in the Setting – Media – Uploading files of the Admin Area, I found 2 blank boxes waiting to be filled:
- Store uploads in this folder
- Full URL path to files
I filled in the absolute path including the document root and did another upload. Now it works.
Home Page finally done, though it’s a temporary home page. Cannot name it index.html. It’ll make the multisites “unlinkable”. Clicking those subdomain sites lead it to the home page, except for those standalone WP installations.
The template for the static pages is done.
It looks exactly alike, which is good.. and bad.
To let you know the difference, I changed the background, but I could hardly tell the difference myself.
The difference was not so obvious – It still looks the same.
The next day, I had this crazy idea – move the navigation to the left.
It took 20 minutes to get it done and another half hour to make it looks right for mobile viewing.
Go Webmastering’s website, take a look and let me know what you think.
I am not a fan of WP plugins, never have been. I used only a few and on some sites, I use only Akismet. That’s all.
This is my latest addition – the Googe Sitemap Generator, and I don’t really know what to say… I never had a sitemap that was created in an instance.
In case you need one, here they are:
Google sitemap generator 3.2.9 for single site
Google sitemap generator for multi site4.0b11
If you need to read for more information or questions:
error and problems.
It’s that easy
Before you active the plugin, just save 2 blank files and upload to the root directory.
I started to use these plugins only in 9 July 2013. Prior to that, I have never use a WordPress Sitemap Generator.
In fact, I’ve never submit sitemap for sites created under WordPress.
Only static sites, and I manally create each sitemap. It was more fun.
But, let’s face it. When you let a program do it, it’s way much faster…
Well, it’s only partially completed.
As this domain is an addon domain, multisite on subdomain could be set up successfully but virtual subdomains cannot be added. Any site added will simply be linked to http://maindomain.tld/wp-signup.php?new=addnewsite.nsk.sg
WP multisite requires the domain to be installed on the public_html.
An addon domain will looks like this instead:
So how should I proceed?
I have 2 options:
- To treat it as a stand-alone install or
- to stick to the multisite install.
The multisite is not a must-have, but I’ll just need it for later showcase and as I’ll be recommending the hosting I am using, it will kind of show you what the level of support the hosting is providing in terms of support and technical help.
I’ll have to call the hosting company to help me make the switch: to place this domain as the main account and move the main to the addon.
If you do not understand this part, just ignore. You may not be ready for WP multisite. If you are new, a regular WP is good enough for you.
Even if you need to upgrade to multisite at a later date, it will still work, except that you’ll have to settle with additional sites on subdirectories instead of subdomains.
nsk.sg/site1/, nsk.sg/site2/, and so on instead of
site1.nsk.sg, site2.nsk.sg/, etc…
Personally, I prefer subdomains on this site. That’s the reason why I go for a 3-letter domain. For a longer Exact Match Domain(EMD), I’d have opt for subfolders for multisite.
I have on another site several instances of WordPress installed on subdomains which work just fine. More work on upgrading but less problems. Less sitewide problems.