qofe

I must have done, quite some time ago apparently. Unsubscribed now. Thank you! ??

Hmmmm… not sure how to attach here. But here’s a sample of the subject & body:

Subject: [WordPress Plugin][1419197] stops-core-theme-and-plugin-updates/trunk: Release 6.0.3 – Added translation logging.

Body (it goes on, with standard developer diff text, but here’s the top part):

Revision
1419197
Author
ronalfy
Date
2016-05-17 23:30:23 +0000 (Tue, 17 May 2016)
Log Message

Release 6.0.3 – Added translation logging. Fix array issue.
Modified Paths

stops-core-theme-and-plugin-updates/trunk/includes/MPSUM_Admin.php
stops-core-theme-and-plugin-updates/trunk/includes/MPSUM_Logs.php
stops-core-theme-and-plugin-updates/trunk/main.php
stops-core-theme-and-plugin-updates/trunk/readme.txt
Diff

Modified: stops-core-theme-and-plugin-updates/trunk/includes/MPSUM_Admin.php (1419196 => 1419197)

I got an email notification that my version of WP had been updated automatically, my reaction… WTF? I’ve never given ‘permission’ for such an update on my blog. The only reason I have/host the blog on an independent ISP is so I could have control & ownership of the content. I upgrade all the time, AFTER BACKING UP my dB, as the WordPress mantra goes… I would back it up anyway, having learned that lesson the hard way.

I just have one blog, I’ve had it for many years, since WordPress was in its infancy. I’ve been a web developer/programmer for many years (before there was a WordPress), so yes, it was easy enough for me to put the code into my config file. But honestly, why should I have to do that? It’s just like an OS — I mean, Apple doesn’t force me to upgrade to Mavericks because it’s better or more secure. I can wait until the kinks are ironed out and *then* update when ready. And I can back-up my computer first.

When I went looking for information on how/why this automatic update happened without my permission, without me even being notified before hand, I found and read that thread on the “developer blog”. Central Geek, I am with you 100%. I guess WordPress is going the way of all corporate. <sigh>

Cafeman, thank you thank you!

I’m going to mark this resolved ’cause now at the very least we know ‘why’. We know what to do at our respective hosts.

You sir, ROCK! ??

Hi Cafeman, thanks for the updated info, it’s much appreciated. I’m using Dotster to host my blog.

Yeah djr3110, it sure seems like it never really worked to begin with and no one wants to own up to it…

Sorry mellojoe, but that’s not what we’re on about.

We have valid RSS feed links, but the widget does not save them, it constantly gives us the previously mentioned error message.

Someone out there must know why, and what to do to fix this… maybe…

I wondered if it was something on the server preventing access to feeds from external sources. But server settings are not something I’m very familiar with.

I’m still holding out hope that someone with the answer will read this thread…

XML is the language that RSS is written in… even if the feed URLs were changed to be “.rss” it shouldn’t matter.

I validated The City Cook feed in the Atom/RSS feed validator:
https://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.thecitycook.com%2Fmisc%2Ffeed.xml

Also — beware of browser cache issues… you may have been looking at cached copies of your pages. Sometimes the reload/refresh button works but it’s usually best to clear your web browser’s cache, close it, re-open and then reload the page(s).

What I found was that it was in fact the CHMOD settings. The original ftp client I used was not applying my CHMOD changes… for whatever reason.

I changed ftp clients, re-did CHMOD and it was all good.

Can you tell me what you did to fix this? I just uploaded to WordPress 2.1.2 and have the same exact problem.

I’ve changed chmod to 755 for the theme folders/contents, I’ve cleared my cache…

I’m at a loss…

That’s my question too — need a way to sort the display of ‘Link Categories’ (not talking about sorting the individual links). It would be nice to be able to sort them by ID number.