neville

It’s very odd. I had a tweet from a Twitter friend who said Twitter’s disabled some things that affect tools like TT. I can’t find any info about this, though.

In any event, TT’s just not updating tweets. So I’ve now deactivated it and am using Javascript direct from Twitter. That works.

Pity, I really like TT.

Running TT 1.0 for the past month on my WP 2.2.2 blog. Everything working fine until today.

TT hasn’t been displaying updated tweets for the past 24 hours. I’ve tweeted a *lot* since yesterday! Manually refreshing in TT options does nothing.

Other than reinstall, any ideas on what else I ought to check?

Figured out what the problem was in my case. Nothing to do with 2.2 or in-built widgets. I think.

I had the separate widgets plug-in installed for version 2.1. When I upgraded to 2.2, that plugin was still there, albeit not activated. The fact that it’s there must do something, somewhere, as I could not get widgets working at all.

I’ve now deleted the widgets folder and all files from the plugins directory – and widgets now work.

I just upgraded one of my blogs from 2.1 to 2.2. This is a sandbox blog with no plugins at the moment other than those that come with WP.

Checked the plugins list, saw Sidebar Widgets version 1.2.1.20070210b. Not activated so clicked on activate.

Result was this text at top of screen –

Plugin could not be activated because it triggered a fatal error

No idea what the fatal error is/was.

Blog functions ok but without widgets at the moment.

Just downloaded it. The upgrade instructions page on the Codex hasn’t been updated yet, though – still shows 2.0.7 as the latest release…

I just had something very similar:

Warning: require_once(/home/.filou/ehobsonc/www.nevillehobson.com/wp-content/themes/k2/) [function.require-once]: failed to open stream: Success in /home/.filou/ehobsonc/www.nevillehobson.com/wp-includes/functions.php on line 2172

Fatal error: require_once() [function.require]: Failed opening required ‘/home/.filou/ehobsonc/www.nevillehobson.com/wp-content/themes/k2/’ (include_path=’.:/usr/local/php5/lib/php’) in /home/.filou/ehobsonc/www.nevillehobson.com/wp-includes/functions.php on line 2172

Lots of head scratching. My blog runs WP 2.0.6 and, before this error, I’d been able to see the blog perfectly fine. I had changed nothing in the WP files nor the K2 theme.

What I had done, though, was update a couple of plugins and install a new one.

Updated plugins: PodPress 7.0, Live 0.4, Diagnosis 1.2.
New plugin: View All Comments 0.1.

First, though, I switched themes back to the Kubrick default to see if this was theme specific, given the ref to K2 in the error message.

Same error resulted, referencing ‘default’ in place of k2. So, not theme specific.

Next, a process of elimination with the plugins.

First I deleted PodPress 7 and reverted back (re-uploaded) to version 6.8. Prime reason was 7 produced other errors in the saved PodPress config settings relating to the iTunes configuration. Reverting to 6.8, those errors disappeared.

Once I’d done that, I viewed the blog and the same warning/fatal error mentioned above error existed. So PodPress doesn’t seem to be the culprit.

Next, deactivate View All Comments. And that’s where the error stopped.

With VAC deactivated, the error disappears entirely and the blog works fine.

Now for a note to the plugin developer…

I upgraded from 2.0.2 to 2.0.4 over the weekend. Smooth as clockwork, no issues at all.

Just follow the Codex installation guide to the letter and you should be ok.

https://codex.www.ads-software.com/Upgrading_WordPress

I think you have to have separate RSS feeds. I’ve not seen an example of a podcast with a single feed offering different files.

Couple of examples:

Geek News Central – https://www.geeknewscentral.com/
(MP3 and BitTorrent versions)

UK Daily Telegraph – https://www.telegraph.co.uk/
(MP3 and iTunes versions)

In all cases, separate RSS feeds.

Doris, would you outline how you solved the problem? Lots of people in the forum asking questions about the upgrade.

Thanks!

knotty, I upgraded 2.0.2 to 2.0.4 yesterday and it went just fine. No dashboard issues you speak of.

You said you just overwrote your existing 2.0.2 install. Do you have any customized files in your 2.0.2 installation that you didn’t keep?

And, you did follow the Codex upgrade instructions to the letter, right?

andy_m, you need to be able to log in by FTP to the server that hosts your WordPress installation. Then you copy the files to your own computer for editing there.

Best if you’re able to speak to your site designer.

Worth doing the upgrade, mickemus. The Codex doc has a specific section on upgrading 2.0.3 > 2.0.4.

No I didn’t, Lois. It was unclear to me from that doc re 2.0.2 > 2.0.4. So I decided to upgrade as if I had 2.0 and followed the ‘full’upgrade instructions to the letter.

It worked fine.

Lois, I just posted re my experience upgrading from 2.0.2 to 2.0.4. No problems at all.

I followed the Codex instructions to the letter, ie, the detailed instructions.

Everything still works ??

Upgraded today 2.0.1 -> 2.0.2. Followed the 7-point list in the Codex. Dead easy, took less than 5 minutes. And it works ??