Fixing stuff, myself included…
WOW… unbelievable! Automatically = yes indeed. What a difference, maybe this means everyone will use WordPress. It’s easier than damn Facebook. I don’t like Facebook; however, I do like Woodpress upgrades automatic.
Getting ready to do another OS X netbook. This time it’s a Dell Mini 10V; last year I put Leopard on Dana’s Lenovo S10. Snow Leopard is going on the Dell.
Yeah, now time to fool around with FancyBox. Actually, it looks like WordPress Admin panel is using something like this when I click the link button.
jQuery is installed to the directory.
Switched lcd screen on one of the Thinkpads, only to discover that it has a jack problem as well. Taking apart laptops is not for the squeamish; you practically have to take it all apart to get to the input jack. Attempting entire dismantle after reading that some of the Thinkpads have wired, rather than soldered adapter jacks, and it may be possible to simply tighten a screw to fix the problem. Trying to remove the front bezel, and one damn screw, which of course is down a one inch hole has a burred head (my bad). Don’t know if I can get the sucker out, without resorting to extreme measures. Now you know why they charge $75 to fix a jack problem.
You knew it was going to be a bear; why did you do it?
I’ve got nothing to lose; these laptops were rescued from the dump remember. It’s a learning experience, but that damn screw is a roadblock at the moment. My next plan of attack involves taking the partially disassembled laptop to my local Hamden hardware store and begging for mercy.
Is there anything else you want to bitch about?
Yes, security screws.
What about them?
The idea of security screws just seems like a ploy to sell security bits! How secure is it really, if all I have to do is go to the electronics store, or buy the bit online? Only one step up from priority hardware. Irritating and costly for the consumer.
Only three months since I was here; perhaps a good sign, or no sign at all.
Sign of what exactly?
A sign of renewed efforts to expose myself to myself.
Never-mind, and it’s my mind anyway. So… lately I picked up about a dozen laptops (Thinkpad R40) at the dump. Got two good ones by combining parts; however, I still need hard drives for both.
Dam! of course my ability to post is not without problems. As I type the copy goes under the 3rd column. Must I update? Leave a bit of copy under the 3rd column and have a look.
Gezopezo now I see. The page needs to be minimum of width. duh… just stretch the page dimwit. It’s really true, if you don’t do something for a while you forget what you already knew.
Well… so two years gobye bye and here I am.
I’ve been gone again for so long there’s been a WordPress version update.
Oh screw it! Why don’t you just post and forget the damn update for now? Update yourself instead.
Yeah! Finally got Snow Leopard running on my Shuttle SG31G2. Spent the better part of the summer trying to get the developer Snow to install on my latest P4. It would not. Once the actual DVD was released on Aug. 28th, the OSx86 scene exploded with information. Armed with that new data, I set the P4 aside and without “too much” trouble hacked it for the Shuttle. This afternoon I’m fooling around with the P4 once more.
Setting up tags and catagories for posts.
Finish formating the posts themselves.
Removing comment tags.
Yes, finally. After talk, talk, talk it doesn’t stretch with browser size changes, and it’s valid CSS and XHTML. I have for the time being retained its retro look. Now I must figure out how to make my design work in WordPress. All of the site would remain static except the Blog page, which would replace/incorporate the Art Attack About page. In other words, that’s the only page that would have the post loop, but it would look just like the rest of my site. And more/most important it will be the only page that can be changed via the WordPress dashboard.
Yep, today on local machine WordPress could not find the database. Damn!
So what did you do?
Spent about an hour figuring out that the my.cnf file maybe should be my.conf. Now I have both of these files in the same directory and changed named host in Apache to “localhost.” Not sure if that was necessary. Once again ran the sym link, because although MySQL was running, it didn’t know where/which socket. I do hope when I reboot tomorrow it’s not the same crap happening.
What else did you do today?
Made some changes to the artattackcentral design. I scraped the 3 container + transparent art work design, but “what the hell” by spending time on that design I have a better understanding of the CSS box/container configuration.
I’ve just finished (once again=almost a year later) setting up Apache, PHP, MySQL and WordPress on my intelMac. If I’d thought more about it before setting up on the intelMac, I would have set up on the PPC MDD Mac.
I guess because, I’m a nervous Nell when it comes to my PC=Mac. In some ways it’s own environment seems fragile. It makes me queasy when I have to use the -f boot arg., and even more sick when she boots and has no dock and menu. However, mostly she’s pretty good, and when she’s terrible I use the OSx86 tools to fix the permissions. I do wonder if I might be better off with the voodoo kernel, but that’s another story…
What’s entailed with getting the development environment up and running?
Since it’s been so long ago, of course I’d forgotten some of the details.
So what happened with the MySQL install?
To begin with the start/stop preference pane doesn’t work in Leopard. So MySQL must be started via the terminal. Also PHP “thinks” MySQL is installed in a different directory so a sym link must be created, or the php.ini file must be edited. I chose the sym link method.
Where’s WordPress in this geeky menagerie?
Ah yes, WordPress “the 7th day” of open source CMS in the mess. Once everything else (PHP, Apache, MySQL), is working download the latest WordPress and let the fun begin. Extract the files in /Library/WebServer/Documents. In the brower call up http://localhost/wordpress (or whatever you want to name the folder the files reside in) wp-admin/install.php. If all has been done correctly you should be able to install WordPress.
Well… was it all working?
All is working; so now I can begin figuring out how WordPress can/is being used as a CMS. It seems WordPress is PHP, but not really > See this: Matt’s Explaination. I decided not to go with the virtual hosts, and multi blogs on one WordPress install this time, because last year I got sidetracked trying to make that work perfectly before entering the CMS realm.