Siapa anda? Pembawa ember? Atau pembuat saluran pipa? Apa anda hanya dapat gaji kalau datang ke tempat kerja? Atau anda termasuk orang yg bekerja sekali saja kemudian dibayar terus-menerus? Jika anda termasuk orang kebanyakan, anda bekerja dgn pola pembawa ember. Saya menyebutnya Jebakan Barter Waktu dan Uang. Selengkapnya di sini… Pasif Income
screen shot data editor
screen shot data editor statplanet di libre office 3.4.5
di desktop kemarin setup shapefile bisa dijalankan,
saat ini kucoba di laptop, kok belum bisa jalan ya..
;;;;;;;;;;;
1 dari 10 cara TERBUKTI utk hasilkan minimal $10.000 sebulan online-> http://woro2.com/pasif-sejati/av1.ag.php?pasti=758
How to import a BlogSpot blog into WordPress
How to import a BlogSpot blog into WordPress
May 8, 2008 by ourtimes
I’ve used this process for Blogger but not the others. Although all the posts and comments get transferred, widgets in the sidebar are ignored. You would have to re-create those from scratch. Blogger ‘Labels’ are preserved as WordPress ‘Categories’.
To start the process go to the WordPress admin area and choose
Tools > Import. Then choose which blogging system you want to import from.
Please note: To use the importer with Blogger you must have a Google account and an upgraded blog. If you have an old-style Classic template you will need to switch to the new Blogger system (screenshot). The blog must be hosted on BlogSpot, not externally via FTP.
Step 1 – Authorize the transfer:
It would be helpful to login to your Google Account before you begin the import process. Then you can simply click the “Grant access” button and continue.

Step 2 – Select a blog to import:
If you have more than one blog attached to a single Blogger account all of them will be listed with an “Import” button for each blog. The example below shows just one.

Step 3 – Author mapping:
On Blogger you have one username, and on WordPress another username. The author mapping process allows you to establish an association between the two usernames.

Once these 3 steps have been completed the import proceeds automatically.
An experience of importing 2000+ posts
I was contacted by Kenny Smith, who wanted to replace a pre-Blogger-in-Beta blog on his self-hosted site. He sent a write-up of his experience:
“My Blogger blog was on an FTP-hosted site, so the first step was to temporarily convert that to Blogspot. That was easy to do inside the Blogger platform. I had more than 2,000 posts to move over to WordPress which was a problem because Blogger is capping the export at 500 posts now. Trial, error and Google searches taught me that I could export the whole thing to a WordPress hosted blog. So I simply created a MYURL.wordpress.com and exported everything from MYURL.blogspot.com – This was effortless.
The next problem, though, came when I tried to export to a hosted www.myurl.com/wordpress/ site. The step is to save the data from the myurl.wordpress.com site on your machine as an XML file. This is easily done within the WordPress platform. The problem was in trying to export that from desktop to www.myurl.com/wordpress/ After two days in tech support conversations with the WordPress folks (who were VERY helpful) we decided that my ISP was timing me out. So what I would see after trying to export 2,000 posts would be 1,734 or 1,722 or 1,755. This got frustrating quickly. Especially while deleting them all, 15 posts at a time.
The answer is a fairly simple one… … Take that XML file and segregate the data, perhaps by months or years if you’re dealing with thousands of posts, into several XML files to prevent the time out. WordPress’ tech people helped me break mine down into three XML files instead of the one I’d been trying and it all uploaded on the first attempt thereafter.
And now, the only really problem I have is an issue of the dates. Everything is written like it took place one day later than it really did. However, I seem to have 2,053 posts on the wordpress site, and I was trying to import 2,055. 99.9 percent is a nice success rate thanks to this extra step in the workaround and a little help from Nick at WordPress.”
Why switch to WordPress.com?
On another site there’s a table which summarizes the features of the two systems: WordPress vs. BlogSpot.
Advantages:
- Quite a few BlogSpot features added after 2006 depend on JavaScript. They won’t show up in older types of mobile device or browsers in which JavaScript is disabled. Google services rely heavily on client-side scripts which add significantly to download times. Outside towns and cities in America, Europe, and wealthy countries in South East Asia, broadband penetration has been minimal. Elsewhere, it’s confined to major cities (ditto for mobile broadband coverage). A 2007 article in PC World magazine noted that Rural America is doomed to Dial-Up. It looks like Google only cares about catering to city slickers in prosperous nations.
- Photo bloggers get a better deal with WordPress.com. In individual posts you can add a photo gallery with a single tag. You can also use a Photoblogger Theme. There are several to choose from.
- There’s always the risk that Google may require users to set up a Google+ account (real names mandatory) in order to continue using the Blogger service.
- I got fed up with a constant stream of spam comments for deletion in my WordPress dashboard. Especially as there were very few genuine comments for moderation. It’s true that if you ignore the Akismet spam queue they’ll be deleted automatically after a while, but it’s difficult to ignore them as a few might have been falsely tagged as spam.
- Blogger makes it easy to change fonts and colors in every theme. None of them are restricted to a limited set of options.
- It has been said elsewhere, but the dashboard Blog Stats don’t really compare to free third-party tracker scripts such as StatCounter and Google Analytics. The graph looks nice, but it’s done with a script so you can’t right-click to save it.
Link pembelajaran
setelah langsung tak coba testing install database mysql di mandriva 2008.1, memang mysql yg terinstall ga langsung jalan nih, karena user password root nya ga ada..
berikut troubelshootingnya
1. install mysql (bisa dilewatkan kalo sudah pernah diinstall)
- Code: Select all
urpmi mysql-common
urpmi mysql
2. edit file /etc/my.cnf, hilangkan tanda comment (#) di depan baris
tmpdir = /tmp/
- Code: Select all
$ su
password:
# kwrite /etc/my.cnf
3. matikan service mysqld bila saat ini aktif
- Code: Select all
service mysqld stop
4. buka konsole baru jalankan perintah ini (maksud perintah dibawah adalah menjalankan mysql server tanpa proteksi sekuriti user dan password)
- Code: Select all
/usr/sbin/mysqld --skip-grant &
- Code: Select all
mysql_install_db
5. buka konsole baru yg lain jalankan perintah ini.. (menambahkan user root ke dalam table user di database mysqlnya dengan password: password)
- Code: Select all
$ mysql -u root
mysql> use mysql
Database changed
mysql> insert into user set host='localhost', user='root', password=password('password'),
select_priv='y', insert_priv='y', update_priv='y', delete_priv='y', create_priv='y', drop_priv='y',
references_priv='y', execute_priv='y';
Query OK, 1 row affected, 3 warnings (0.01 sec)
mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)
mysql> exit
6. matikan service mysqld
- Code: Select all
service mysqld stop
7. jalankan kembali service mysql
- Code: Select all
service mysqld start
8. coba lagi login ke mysql dengan username: root dan password: password. kalo bener harusnya udah ok
Pada Kasus Saya langsung saya coba langkah ke 7, kemudian saya jalankan # mysql_secure_installation bisa jalan, sebelumnya tidak bisa dienter saat minta pasword.


