b3 b0rn.. c0nf0rm, b3 si|3nt .. di3

noted earlier while at work that 1.2.2 was officially released.

decided to upgrade tonite. quite apprehensive about it

followed the instructions given in the download page on how to upgrade.

1. backup database (just in case you screw up your upgrade – at least you managed to salvage your posts)
2. delete all previous installation files (quite right! out with the old ~)
3. upload the new WP files ( ~ in with the new!)
4. run the upgrade file (nearly there)
5. check that everything is in order

i got stuck at no. 5

the index page was complaining – had this whole load of mutterings in php speak

kept calm. read the error again. kept seeing repetitions of the word wp-comments.php.

ahh. so i managed to leave out 1 file in the upload (step 3). had planned to keep my old file but accidently deleted it (in step 2).

uploaded the default file. reloaded the page

and here you have it. epistle reloaded.

can’t spot the difference?

me too

time to read the changelog then.

managed to recall my login to blogger.

transferred the entries made there. carried this out manually as i only created 3 entries – then i switched to using wordpress on my own site.

read the entries in September. if you even bother. not that there’s any earth-saving ideas there anyhow

some ppl just take for granted things are going to be prepared for them. a
few colleagues are currently holding training sessions to introduce our new
users to the system.

i understand that sometimes the information provided by our clients come at
the very last minute. which is why you should always have on hand some form
of backup. in our case, we’ve had only recently conducted UAT sessions for
the previous phase and the data used are still available in the server. i
am supposed to be working on some other tasks but would have assisted them
in locating the needed info prior to the training sessions IF they had
actually either opened their mouths to ask for it or even mail me (i’d
rather respond via email since i have a tendency to launch into a diatribe
when i get pissed off – which i currently am)

so here we are. on the day that the training’s supposed to be conducted.
apart from the fact that the application server in our testing system seems
to have decided to leave the building, there shouldn’t have been any
issues.

then smack when i was about to attend a discussion after lunch, came the
request to assist in changing certain recycled data to meet their training
requirements. &%$#^!! i made the necessary changes (not without mouthing
off the bearer of the message – sorry !) and rushed to the discussion on
the meeting room floors.

came back.. checked for any new mails .. and discovered that my blog has
turned nasty on me. so i wasn’t in the best of moods (which seems to be a
constant when i am at the office) when the same colleague came to me and
asked at 5.30pm whether i still have the reference data sheet.

to which i answered of course i do. said colleague muttered ok and then
left the office.

suddenly my phone rang and was greeted by another colleague’s voice.
apparently calling from the training room. asking whether i have some data
that they could use since they only had portions of it and couldn’t be
effin bothered to confirm the rest was ok or not. she asked for me to mail
it to her. which i did – with some warning to make certain changes so that
mails don’t get sent to the wrong people (we’re working in another phase
remember, so different set of clients)

then she responded to my email, asking for the same reference data document
which was enquired by the colleague that has already left the office. by
golly! what a load of bollocks! if my addled brain serves me correctly, the
colleague that left the office only asked whether i had the document but
never mentioned anything about wanting it sent to his partners-in-crime. i
very nearly lost it but decided to just mail the darned document cc-ed to
the rest again with more word of caution to ensure that the data is still
valid.

so here i am, still at the office – writing an entry about this, when i am
supposed to have gone home. a gal just has to let off her steam .. or i’d
end up biting off more heads tomorrow.

woooszahhhh.

ok. am calm. bye bye

i came back from a meeting earlier this evening and decided to post some thoughts that went through my mind during the discussion.

imagine my dismay when i was greeted with this error page

guessing worried that it may be something i did to the files (though i can’t recall any), i attempted to replace the ’supposedly’ erroneous files with the originals from my hard drive.

reloaded epistle and got the same error.

i was fast approaching panic while i browsed ever so casually to the support page of wordpress. a quick search on database error gave me a few hits.

apparently, i was not the only one hit by this seemingly hostile error (hostile to me since i don’t speak SQL speak). a few of the posts comforted me by stating that it had to be due to PHP upgrades carried out by respective hosts in response to this security advisory released to the PHP community

a quick email to my own webhost and hopefully this is rectified quick! am
actually mailing myself a few posts to update later. just in case i lose my
steam to write on this.

Update:
got the response from my host. it was due to the PHP upgrade that they were carrying out. techie informed that they have received quite a number of complaints and have reverted to the older version til they can figure out how to ensure the errors don’t occur.

i am just happy that it wasn’t me.