pixilated

@ alox
I actually wasn’t criticizing his use of profanity, merely stating that I wouldn’t read it at first because of that. It is my personal opinion that that kind of language is unnecessary in getting your point across and being taken seriously – he came across, in that first paragraph, as being exactly what NM said. My second comment was made in jest, in regards to ntt’s comment about the inarticulacy being deliberate.
We are all entitled to our personal opinions. We all have a right to express those opinions, whether other people think they suck or not. As Shushubh said, a diary/weblog is a personal thing. We all do it for our own reasons. Isn’t it as wrong to criticize that as it is to criticize the use of profanity?

Actually you could be right – I went and had another look and beyond the first blurb, things did change.
Do you think he’s saying that webloggers can’t spell (he’d be right, looking at my spelling of ‘eloquent’ above), and that we can’t construct grammatically correct sentences. Oh wait! I have trouble with that too. *VBEG*

I gave up after the first sentence. If he was eleoquent enough, he’d have managed to get the point across without having to resort to that amount of profanity.

litterstars, with this script, it’s best done on a new install.
I did find an alternate on the php-princess board, which seems a lot more intuitive. It wipes out your b2 database, so beware. It uses the mt export file.
https://board.php-princess.net/index.php?showtopic=857

https://tidakada.com/board/viewtopic.php?t=1145
Read the whole thread as there are improvements etc further through. It’s for b2 but it looks like it’ll work for WP.

I’m sorry your experience wasn’t as good. I did notice another couple of glitches. Some formatting was lost and apostrophes etc went missing. However, for me, it was just a test and nothing was to be lost from trying it.

Actually, it works as is. A couple of notes on my experience:
1. I only tried it on a fresh install, so I don’t know how it would go on an existing installation.
2. Don’t export the users, otherwise you won’t be able to log back in to WordPress. It’s easy to skip – just don’t click that link in the export script.
3. I had thought at the start that I would install b2, then upgrade that to WP to be on the safe side, but it’s not necessary. Just install WP, run the export script, then run the b2-2-wp.php script (in the wp-admin folder) to convert the database.

Since it won’t let me re-edit that post, it’s supposed to be replaced with the “br /” tag.
Finally, I understand the posting code requests! *G*

I’d be happy too as well.
I remember reading in another post that you just want the layout2b.css file altered though, not the index.php file etc. Is this still the case?

Try https://yoururl/wordpress/wp-admin/wp-install.php

I’d start by editing your php.ini file, which by default is set to show you all errors, warnings and notices.
You’ll find the error handling options starting around line 235. Comment out the line:
error_reporting = E_ALL;
Uncomment out the line:
error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR
This will set it to only show you the fatal stuff and most (if not all) of your errors will disappear.

It’s a browser issue (IE for the most part). Restarting the browser is usually enough to fix it, but occasionally a reboot is in order.

More like https://www.photosbylynda.com/pencam/ (uses pmachine) or https://www.sensitivelight.com/blog/ (uses mt). Of course, Matt has one too but I’m not sure what he uses.

I have a couple of versions already done. Not the prettiest, but there you go. Screenshots and text files are available in the post.
https://press.blog.net.nz/index.php?m=200306#post-4

You can edit the fonts and colours easily by fiddling with the b2.css file within the wp-admin folder. It’s not part of the core system, so you won’t screw anything up. If you’re nervous about it, rename the original to b2-old.css before you upload your new file.