allyngibson

I noticed the same thing with the Tag Cloud — if I specified the same size for my minimum and maximum it ignored it and still generated different sized tags, albeit with slight differences.

What I discovered through experimentation is that I needed to include &unit=px at some point in the argument string for wp_tag_cloud. Why that should make a difference I don’t know.

I might look at these:

The Da Vinci Code theme.
The Lord of the Rings theme.

Both of these have a medieval parchment look to them, and if you remove the graphics they’d probably work for your needs.

If I’m understanding what you want, do you want a calendar widget that has the month and year as a header rather than as a caption that the built-in widget does?

I’ve reworked the calendar code into a widget to make the WordPress calendar work better as a widget, to match the usual sidebar formatting.

If you’d like, drop me an e-mail at [email protected], and I’ll send you the widget.

You can do what you want. But it’s going to take some work.

First, with all of your LJ entries entered into the WordPress database, you go through and delete all your LJ entries. I don’t know if there’s any fast way of doing that, but you need to delete them.

Then, if you edit each WordPress entry — say, to add tags — the entry will get cross-posted back to your LJ.

At that point, the two databases will be linked again.

I held out on Widgets for a long, long time.

What finally swayed me was people asking for a plug-in I’d written as a widget. Which meant I had to use widgets to learn how they worked so I could write the correct code.

I generally like the Widget system.

Some Widgets, however, are bears to work with as they don’t display well on certain themes. That’s the trade-off — simplicity of sidebar management, versus getting the sidebar items to look right.

At the very least, I’d recommend playing around with widgets. ??

This is the important paragraph:

Luckily for you, we’ve coded a replacement widget. Simply put that code in a file in wp-content/plugins/widgets, activate it in your Plugins pane, and finally select the brand spanking new ‘Tarski Links’ Widget.

Open this file, save it as tarski_links.php, and upload it to your WordPress widgets directory and activate. Then install the Tarski Links widget, replacing the default links widget. ??

Tarski has a special sidebar links widget that works better with the Tarski theme. You can read up on it here, and that should take care of the formatting issue.

I also rolled back to version 1.0 on Automattic Stats, as I didn’t care for links on the stats page opening in the frame. :/

The thing is, the error isn’t actually a problem as far as I can tell. The post still goes live on my blog, and it goes live on my LJ. It just takes a little longer to show up.

And it’s been a recent thing, within the past week. I’d upgraded to Opera 9.21 two weeks ago. I’d upgraded to WP 2.2 long before that. So I’m not sure what’s changed and why it would suddenly generate, unless it’s a problem on LJ’s end. They did have that spasm of sorts this week. :/

So, I don’t know. Things still work. It’s just an annoying error that’s not particularly helpful in diagnosing the problem.

I’ve been trying to figure this one out, too.

I thought at first it was an Opera problem, as I’d just upgraded to Opera 9.21, and I didn’t seem to have the problem in Firefox. But a downgrade to Opera 9.20 still generated the error.

Then I thought about what I’d done recently. Why, I’d upgraded my version of Spam Karma. So I disabled that and switched to Akimset, and still got the 32300 Transport Error.

My current working theory? I also use the LJ Crossposter–my gut feeling is it might have something to do with that.

I’m thinking that’s a normal feature. The Bookmarklet area doesn’t just not render in Opera, if you look at the source code it’s not there at all. At a guess, I’d say that the WordPress code is programmed to do some browser sniffing, and if you’re on Opera it doesn’t serve the code to create the Press-It bookmarklet area of the “Write” screen.

In WP1.5 I remember that Press-It worked very well in Opera. I didn’t like how it worked in 2.0–rather than open a new tab where I could write the Press-It feature took over the active tab which really defeated the point.

With Opera’s tabbed browsing, though, I’m not sure you even need Press-It. It’s just convenient enough to open a new tab and go right to your WordPress dashboard and start up a post. And on Opera 9.2 when you open a new tab you’ve got the “Speed Dial” feature built in where you can pre-define up to nine webpages for quick access. My dashboard is number uno. ??

However, it should not pull up all 1100 posts of yours. It should be limited to however many posts you normally show on the main page, like all other pages.

Otto42, that helped me out tremendously. I took a look at the Tarski loop, and I saw there was an option for pagination. I didn’t have that set, so anything–category, tag, you name it–was loading everything.

Now it’s good. ??

I’m running Opera 9.2 and have no problems with the formatting bar on the editor page.

Is it possible that you’ve turned off Javascript in Opera, either for all webpages or for your own site? I’d check this by:

Bring up the Write page.
Right-click mouse.
Go to “Edit site preferences…”
Go to the Scripting panel.
Make sure “Enable Javascript” is checked.

(I suggest this because in another webforum I accidentally turned off Javascript for that website in Opera, and then couldn’t post <i>anything</i>. It took a little while to figure out what I’d gone and done.)

I’d give that a try.

Here’s the print.css file I use for my webpage. It works well in IE and Firefox, and mostly well in Opera. (Opera has some issues with rendering print.css coding properly.)


a:link, a:visited {
color: #520;
background: transparent;
font-weight: bold;
text-decoration: underline;
}

body {
background: white;
background-image: none;
font-size: 10pt;
}

form {
display: none;
}

h4 {
display: none;
}

p {
text-indent: 1.5em;
margin-top: 0;
margin-bottom: 0;
}

#content {
text-align: justify;
font-family: "Book Antiqua", "Times New Roman", Times, serif;
font-size: 12pt;
margin: 0px;
color: #000000;
padding-left: 10px;
padding-top: 0px;
padding-right: 0px;
padding-bottom: 10px;
width: auto;
}

#footer {
display: none;
}

#header, h3, h4 {
border: none;
font-weight: bold;
margin: 0px;
padding: 0px;
width: auto;
}

#main {
float: none;
margin: 0px 10%;
padding: 0px;
width: auto;
}

#menu {
display: none;
}

#navmenu {
display: none;
}

#postcomment {
display: none;
}

#side {
display: none;
}

#subnav {
display: none;
}

.feedback {
display: none;
}

.meta {
margin-bottom: 10px;
}

.storytitle {
margin-top: 10px;
font-size: 16pt;
font-weight: bold;
}

Open the .php code in a text editor and strip out the [li] tags, and replace the [/li] tags with maybe something like <br>. If you want to try this file, I’ve made that change.

Sorry, I should have thought of something like that. I wrote the plug-in so it would look nice with my own set-up, not realizing that other set-ups are different.