Archive for the ‘Database’ Category

How to Migrate wordpress SU to wordpress MU

March 23rd, 2010 No comments

Bagaimana sih caranya bermigrasi dari wordpress SU ke wordpress MU? Mungkin Anda sudah tahu caranya, atau ada yang belum tahu? Berikut ini langkah-langkah migrasi dari wordpress SU (single user) ke wordpress MU (multi user)

Langkah-langkah migrasi wordpress ke wordpress MU :

  1. Download dan install wordpress MU
    Sebelum penginstalan, backup semua file dan database yang ada. Instalasi wordpressMU ada 2 cara:
    1. Install Manual.
      • Download paket wordpress MU kedalam hosting Anda.
      • Ekstrak paket wordpress MU, Override file wordpress yang sebelumnya.
      • Install wordpress. Seperti menginstall wordpress SU. Next, Next, Next, dan Finish 🙂
    2. Read more…

Manual Upgrade WordPress 2.7

December 15th, 2008 3 comments

Kemarin pas mau upgrade WP ke versi 2.7 dengan menggunakan plugin WP Automatic Upgrade tidak dapat dijalankan di webserver tempat hosting saya sehingga saya memilih upgrade manual. Berikut cara upgrade dari WordPress 2.6.5 ke WordPress 2.7.

Read more…

Categories: Dailly, Database Tags:

Username and password do not match

August 7th, 2008 1 comment

Here’s a tutorial on video on how to recover and change your password for joomla administrator.

Tutorial tersebut dah nggak bisa. Coba deh artikel di

Recover Super Administrator Status of Joomla! 1.0.x and 1.5.x

There may be times when due to database or other issues, the Super Administrator assigned for a Joomla! installation may lose their super admin status and cannot login into the admin backend of the installation. One of the common situations used to be with the user synchronization procedure of the Joomla-SMF bridge. With new versions, that incidence has reduced, but this tutorial is useful for any situation where a super administrator cannot log in into the Joomla! admin backend.

So, sometimes, it is possible that there are NO super administrators left to administer the Joomla site! This sounds terrifying, isn’t it?

However, this tutorial will teach you a way to recover that “position” after being bethroned 🙂

Click on the Joomla! version you have trouble with: Joomla 1.0.x | Joomla 1.5.x

Thsi tutorial expects that you have access to phpMyAdmin. How to go there?

In the cPanel access given by your webhost (usually Unix/ Linux), click on MySQL databases. You will be taken to a list of all databases in your site. Go to the extreme bottom of the page and you will see a link to phpMyAdmin.

Basic SQL database knowledge is helpful in carrying out this recovery, but it is really not necessary and I will make it simple for you.

So, now you are in phpMyAdmin. Look at the left sided frame. There is a drop down list of all databases. Select the database of your Joomla! installation. As soon as you do so, you will get a list of all tables within the that databse listed in the left frame.

Joomla 1.0.x admin login problem and solution:
Database tables

There are a lot of tables in the Joomla MySQL database. But we will focus on three of them. If fact we will focus on three tables, three “id”s and many numbers!

Three tables:

Two “id”s:
user id (id)
group_id (also referred to as gid)

Many numbers
25, 18, 62, 10 etc… don’t get confused NOW.

Being an interconnected database, there are references to ids at different places and we have travel through them and correct them. It’s like a treasure hunt. What are we looking for? The “id”. The group_id of a Super Administrator in the database is 26. If you are interested in knowing the group_ids of different level of users in Joomla!, it’s just here for academic purposes:

GID or Group ID values:
17, ‘ROOT’
28, ‘USERS’
29, ‘Public Frontend’
18, ‘Registered’
19, ‘Author’
20, ‘Editor’
21, ‘Publisher’
30, ‘Public Backend’
23, ‘Manager’
24, ‘Administrator’,
26, ‘Super Administrator’ (IMPORTANT: Before Joomla 1.0.11, the group ID of Super Administrator was “25”)
Solving the identities

Lets take the tour now. First click on the “jos_users” list on the left. The table details will open in the right frame. Look for the link “Browse” on top. Click on it.

You will be presented a list of all users listed in the order of their “id” (user id). This id is NOT their GID or aro_id! They are different. Look for the entry with username “admin” or whatever username you had for the Super Administrator. In most Joomla! installation, it is “admin” by default. Usually, the user id (id) for the “admin” is 62. And it will be listed first. So, it should not be difficult to find. In this row, go to the column “gid”. For Super Administrators, it should be 26 (25 if before Joomla 1.0.11). If it is 26 (25 if before Joomla 1.0.11), fine. If not, click on “Edit” button on the left side of the row and change it to 26 (25 if before Joomla 1.0.11). Now, do this carefully – note down the “id” of the “admin”. It is 62 as I mentioned earlier, by default, in most cases. Anyways, note it down.

Now, we go to our next destination – “jos_core_acl_aro”

Click on this table on the left and click “Browse” as earlier. In the list, locate number 62, or otherwise if it was different, under the column “value” (usually 4th or 5th column). Now, note down the aro_id of the same row under the column “aro_id”. This aro_id for the admin is generally 10. Once you have noted down the aro_id, move on.
Final step

Last table: “jos_core_acl_groups_aro_map”

Click on this table and on the left and click “Browse”. Its getting to the final steps now. Look for the entry 10, or otherwise if it was different, under the column “aro_id”. Once you get there, note the number under the column “group_id”. Is it 18? That’s why you have the problem 🙁 It should be 26 (25 if before Joomla 1.0.11).

Remember 18 means registered user and 26 (25 if before Joomla 1.0.11) stands for Super Administrator. All you need to do now is to change the group_id to 26 (25 if before Joomla 1.0.11). Click on the “Edit” button on the left side of the row and change the group_id to 25. SAVE IT.

TADA! You must now have been reinstalled as the unquestionable king/ queen of your Joomla! website 🙂 Please try to log in into your Administration backend. If you can login, do not forget to come back to this page and write a line about your experience. We love feedback.
Joomla 1.5.x admin login problem and solution

This is even simpler. However, let us describe the symptom correctly first. This is the most common scenario if you landed here because of a Joomla 1.5 related issue: You type your ‘correct’ username and password, the login page appears again without reporting any errors! However, if you type a wrong combination, “Username and password do not match” error is reported. Strange, eh?! No worries…

You will need access to phpMyadmin here too. “Browse” the jos_plugins table. Look for the row that has “User – Joomla!” under “name”. In the same row, check the value under “published”. It should be “1”… if it is “0”, that’s the problem!Check the screenshot image below:

Now edit the row and change the 0 to 1 and save. Try logging in and voila! You are in 🙂

Categories: Database Tags:

Can’t Select the Databases

July 16th, 2007 3 comments


Tiada kata yang terucap. Hanya syukur kupanjatkan. Akhirnya update ulang database blog ini selesai. Walaupun 2 bulan (Juni – Juli) ini postinganku hilang nggak bisa dikembalikan. Nggak ada backupan lagi. 🙁 Hiks hiks. Gara-gara banwidth limit exceded selama 2 bulan, database mysqlku ikut ter-dump. Ough Terpaksa puasa ngeblog deh selama 2 bulanan lebih. Untung saja aku sempet backup database di drivehq, walaupun data yang aku update cuma sampai dengan bulan April 2007. Jadi postingan bulan Mei , Juni, Juli hilang deh :(( Tapi nggak papa lah yang penting ada dari pada hilang 😛

Semaleman nguplek-uplek cpanel nggak bisa-bisa. Dari membuat database baru, delete database, uplek^2 file php ampe teler qeqeqeqeqe. Pusiiiing. Tapi aku nggak begitu saja menyerah dengan kondisi yang demikian. Kucoba menghubungi pihak webhosting tempat blogku nangkring. Nggak ada masalah dengan database server, Cuma untuk server PostgreSQL nya lagi down. Jadi nggak ada masalah sebenernya, Cuma saja aku belum tahu apa penyebabnya. 🙂

“We were able to connect to the database server (which means your username and password is okay) but not able to select the wiwinweb_coba database.

Are you sure it exists? On some systems the name of your database is prefixed with your
username, so it would be like username_wordpress. Could that be the problem? If you don’t know how to setup a database you should contact your host. If all else fails you may find help at the WordPress Support Forums.”

Begitulah error yang aku dapatkan di blogku. Padahal scriptp config.php sudah bener. Baik itu nama database, username database, maupun passwordnya. Kenapa e kenapa ?…

Alhamdulillah bisa juga ngatasin masalah ini. Tentu saja dengan bantuan mbah google :D. Baik, untuk mengatasi masalah yang demikian:

  1. Silakan login ke cpanel
  2. Masuk ke MySQL® Databases
  3. Buat database dan user database
  4. Edit file config.php yang ada dalam wordpress
  5. Contoh :
    define(‘DB_NAME’, ‘namadatabase’);
    define(‘DB_USER’, ‘userdatabase’);
    define(‘DB_PASSWORD’, ‘passworddatabase’);
    define(‘DB_HOST’, ‘localhost’);

  6. Setelah edit, jangan lupa save.
  7. Kembali ke MySQL® Databases, disana lihat bagian Add user to your database, option Privelages.
  8. no cek

  9. Hilangkan tanca cek pada Previleges All, kemudian cek semua bagian select, insert, update, delete, index, create temporary tables, create, alter, drop, lock tables, dan references.
  10. cek

  11. Kemudian klik Add User To Database
  12. Coba sekarang akses website/blog anda yang menggunakan wordpress. Masihkah error? Jika masih error mari kita diskusi bareng. Wiwin juga masih nyubie
  13. Semoga tutor ini bermanfaat bagi semuanya.

Categories: Database Tags: ,

Important Database Maintenance!

November 18th, 2006 2 comments

Untuk sementara aku harus sabar dulu. Padalah udah pingin banget lihat hasil blogku yang telah aku buat. Yaa walaupun masin memakai wordpress, tapi semoga aja bisa bermanfaat. Hari ini serverku –awardspace– lagi diperbaiki, jadi untuk sementara nggak bisa diakses. lagi ada perbaikan database MySQL. Semoga saja maintenance-nya cepet sehingga blogku bisa Online lagi.


Bad Behavior has blocked 1015 access attempts in the last 7 days.