WordPress: Mgbake Ọdachi

WordPress agbajiri

Ọdachi HindenburgThe ikpeazụ ụbọchị ole na ole I've been working furiously on getting my good friend Pat Coyle's blog back up. (My vacation continues to get more interesting – today it's snowing slightly… in April! Whatever happened to Global Warming?)

Achọrọ m ịkọ ihe merenụ wee tụlee usoro mgbochi nke m weere yana etu esi degharịa ya.

Here's what happened:

  1. A DNS ihe nkesa gara na fritz. A DNS nkesa na-asụgharị okporo ụzọ na-abata na ngalaba aha ma webata ya na sava kwesịrị ekwesị. Na nke a na - eme, ọ gbaghaara ụzọ 2 nke iji ekwurịta okwu - ngalaba aha na saịtị ahụ na saịtị ahụ na nchekwa data (nchekwa data ya dị ugbu a na gburugburu ebe obibi).
  2. I complicated things by quickly moving his blog over to another server, not realizing that there was a DNS issue. This adds another level of complexity. Passwords in WordPress (and most other database applications) are uniquely encrypted by the server that they are on. If you move the site to another server, you've just disabled your ability to decrypt that password. Thankfully, WordPress (another great feature) has a password recovery system where you can reset your password via a link in an email.

Here's the immediate action that I took:

  1. Before this ever occurred, I have to say that I'm with a fantastic web hosting company who does comprehensive backups. I've never had an issue that they weren't able to correct through backups. I've heard nightmares from other folks on their blogs and sites being totally lost. I can't imagine what it's like to go through that. (Denye aha na ndepụta RSS m ma ị nwere ike nweta akwụkwọ ego maka afọ efu na ndị ọbịa m).
  2. Enwere m ike ịbanye na Web Server site FTP ma weghachite ma saịtị ahụ na nchekwa data. Akụkụ ọzọ nke ngwugwu ngwugwu m bụ na m nwere ike ịnweta dum VDS gafee websaịtị ahụ. MySQL na-echekwa ọdụ data na ndekọ faịlụ (/ var / lib / mysql /). Enwere m ike ibudata ọdụ data naanị site na ị copomi ndekọ mpaghara. Na-ekwu maka nnukwu nkwado ndabere! Enweghị mbubata, enweghị mbupụ, enweghị oke nha faịlụ iji mesoo… naanị FTP.

Ugbu a, enwere m saịtị ahụ na ebe nchekwa data dị na mpaghara, m kuru ume. A sị na m kwụsịrị ebe a ma nwee ndidi, nsogbu DNS ga-arụ ọrụ ya na Pat gaara alaghachi ngwa ngwa. M kwupụtara na ngalaba Aha ka na-arutu aka na ihe kwesịrị ekwesị Aha sava m usu tinye n'ọrụ Whois.net. Ọ bụrụ na ịlele ngalaba gị ebe ahụ, sava aha ahụ dị na ala nke akụkọ ahụ.

Nke a mere ka m kwenye na enwere ike ịbanye ebe nrụọrụ ahụ. Ihe nkesa aha ahụ ziri ezi mana peeji nke na-abịa bụ ụfọdụ peeji dị egwu nke dị ka spam. Ejiri m Ndụ nkụnye eji isi mee tinye to Firefox to ensure I actually wasn't being redirected – the typical hack that many people see. The site wasn't being redirected. I could have done some additional troubleshooting; however, I entered a support ticket with my host so their experts could begin investigating.

Iweghachi saịtị gị na akaụntụ dị iche ma ọ bụ onye nnabata:

M na-adịghị emelitere Pat ka ọhụrụ version nke WordPress 2.1, PHP, na MySQL ma, otú ahụ ka m kpebiri na ọ dịghị oge ka mma karịa ugbu a! M hichapụ akaụntụ ochie ya wee bido akaụntụ ọhụrụ. Enweghachi m ozi email ya ma tinye nchekwa data ahụ, WordPress 2.1 and Pat's content:

  • ndekọ wp-ọdịnaya bulite ndekọ - nke a bụ ebe ihe osise gị niile ebugo.
  • wp-content plugins directory - niile gị plugins (mee nke a ikpeazụ ọ bụ ezie na ịnwere ike ịnwe mbipụta mbipute.
  • ndekọ wp-ọdịnaya gburugburu - isiokwu gị.

I hope in a future release of WordPress that these 3 directories are root directories rather than sub-directories. It would make upgrading much easier! By this time, my host had found the DNS issue and properly redirected the site. Whew! Now Pat's page was coming back up with a WordPress Upgrade message. I clicked through to upgrade the database and he was back up… almost.

Remember the encryption issue I spoke about? Yea, Pat couldn't login because of it. His password no longer decrypted the value in the database properly so I had one more correction to make. I physically logged into the database and changed Pat's reply email address in the user table to my email address. I then utilized the “Lost my Password” feature to email myself a link to reset the password. After resetting the password, I logged in and changed Pat's email address back.

And now Pat is back up! Hindsight is 20/20… had I simply waited on my host, the issue would have been corrected. I really complicated the issue. However, Pat's now upgraded and running the best versions of everything. I'm sorry he was down so long, though. It doesn't take long to bounce back from downtime, but it is a nasty inconvenience! Sorry, Pat!

Ihe ndi mutara:

  1. Make sure you're with a host that has great backups.
  2. Weghachite saịtị na nchekwa data gị ma chekwaa ha na ebe nchekwa.
  3. If you're with a good host, rely on them to find and correct the issue.
  4. Ọ bụrụ na ịchọrọ, gaa na onye nnabata ma ọ bụ akaụntụ ọhụrụ ma ghọta otu esi eweghachi saịtị, nchekwa data, ma weghachite paswọọdụ gị.

Additionalfọdụ Ama ndị ọzọ

Naa ugbu a maka ngwa ngwa njikọ hasntanetị amụbawo manifolds. N'ezie, na ụwa a na-agagharị, nke ịntanetị, satịlaịtị ekwentị egosila na ọ bara uru. A bịa na ntanetị ịntanetị, ndị mmadụ ka nọ na nsogbu ma jụọ ikuku ịntanetị olee otú bara ezigbo uru maka ha. Karịsịa maka webmasters mkpa nke ikuku DSL abughikwa ajuju. Ọkachasị webmasters ndị a na-ahọrọ web imewe studio n'ihi na emebe na mgbe ahụ mkpa a na-agba ọsọ njikọ bulite ya. Dị ka a nzọụkwụ ọzọ a ngwa ngwa njikọ a chọrọ ke usoro nke ahịa search engine. Onye nwere Asambodo Microsoft nwere ike ijikwa nsogbu niile na ịkparịta ụka n'ingntanet nke njikọ ndị a.

Kedu ihe ị chere?

Ebe a na-eji Akismet iji belata spam. Mụta otu esi etinye usoro data gị.