sahaskatta

Interesting. W3TC wouldn’t recognize a pre-created Dallas Cloud Files Container for me. When I attempted to let W3TC create a new container for me, it made a Chicago one.

Camu,
Thanks for the speedy response.

You are absolutely right about the CSS thing. No clue why adding the class in the HTML wrapping didn’t cross my mind.

As I expected, you knew what you were doing! ??

It would be nice to have this supported too. Jetpack is nice, but I am sure many people do not want to tie their self-hosted install with WP.com. I also do not plan on using any of the other Jetpack features, so having just this plugin would be great.

I am also seeing errors when debug mode is on in WP 3.2. Anyone else?

This is a bug which has a very easy, but somewhat tedious fix.

If you go back and check, you will notice that only new posts are not using the CDN urls. The older ones are probably working just fine.

To solve the problem, I just go to the CDN section in the W3 Total Cache plugin. Select the “Unsuccessful file transfers” button. Then choose “delete queue” to solve the problem. You will probably have a list of files that the plugin thinks failed to upload, but they worked just fine.

Just a small glitch, but you have to repeat that process from time to time.

I’m glad I’m not the only one. I assumed that a lot more people were using this, but it might be a small user base.

I’m considering installing it on my own server. Hopefully that isn’t too hard. I briefly skimmed the documentation, but didn’t look into it much.

I’ll try to figure out a fix when I have a chance. I have never used multi-sites mode in WP, which is the main issue.

I apologize for the problem. If you find a fix, please feel free to share.

I would be happy to credit you entirely for the update.

I can’t imagine how hard it must be for the core WP developers to decide on new features. Just about everyone wants a new feature or something removed. Even minor changes can affect or break WordPress for tons of users depending on how they are using it.

I’ve just spent the last 3 months developing a major site on WP (Skatter Tech). I felt the experience was great, a few things were undocumented, but no major issues aside from that.

As for my thoughts for WP in 2011:

• HTML5 and CSS3 – While not all browsers support this entirely and although the specifications haven’t been standardized, there are MANY things that are 100% compatible and ready for use. I think the TwentyTen default theme and the Dashboard should start transitioning over carefully.
• Improve Search – Many people are using Google’s Search API as an alternative because the native search is fairly poor. It may get the job done if you only have a few articles, however there’s no ‘relevance factor’ in ranking results. Even some basic improvements to the algorithm would go a long way.
• Bundled Plugins – Akismet is an amazing plugin and I use/pay for it. However, that’s only because I use WP for the purpose of being a ‘publishing platform’ for my publication. WordPress is moving from Blog->CMS (right?). If so, commenting on many installs aren’t necessarily enabled or even visible (e.g. restaurant website). As for Hello Dolly, keep it. Why? It may serve no practical purpose, but it feels like a part of WordPress culture. It’s not bulky and it’s easy for users to remove. Keeping at least one plugin as an example is a good idea.
• Gravatar – Like Akismet, I’m also a fan and a user of this service as well. However, it feels like Akismet/Gravatar are the only two external/third-party service inside of WordPress. I’m not suggesting the removal in anyway. However, I think some major companies that may want to use WordPress might not want to rely on another service. I agree with the suggestion to implement ‘local user avatars’ to reduce dependence on Gravatar.
• Increased Security and Keeping Slim – I’m sure these are always a given no-brainier, but just mentioning it again.

Once again would like to say that WordPress is a phenomenal platform and the developers who I’ve been bugging over the past few months have been amazingly helpful. (And that’s coming from a guy who was an intern at Six Apart, which was an awesome company as well.)

P.S. My current dream-WP feature? Live collaborative editing, Google Docs style! I wish I could completely say goodbye to MS Word. After the Deadline is already a better spell checker in my opinion.

Philme,
Glad to see that people are using it and that you like it. This was my very first (very simple) plugin.

I unfortunately haven’t spent much time with WP Multi-sites, so I don’t know what is wrong. However, I’ll DEFINITELY take a look! I’ll add support for it in the next update.

So if I understand correctly, the Blog Name, Category List, and Tag List, are properly emailed to the Admin Email on Multisite? Are Author Name, Time Stamp, and Content missing?

Awesome!

I’ll give it a shot. Thanks for responding and releasing a fix so quickly.

Just also noticed it messes up the Categories widget as well.

Also noticed that you had added a custom column to the post page, which explains why you have the CSS file loading there as well.

Maybe load a secondary CSS file or inline CSS for just the classes you need for the post page.

Hey Camu,
No worries, it wasn’t the end of the world. Just caused a bunch of odd formating and spacing.

Here’s a screenshot: https://i.min.us/idUHPm.png

I noticed the issue with both WP 3.0.3 and WP 3.1 Beta 2.

Just wondering, why do you need CSS on the post page for example? Can’t you just limit the custom CSS file to just your plugin page?

@jmparsons

Thanks for that update. I actually didn’t have luck with the force overwrite mode. It still ended up with new uploads in the failed queue.

I will have to give tweaking the meta data a shot, which will hopefully work.

P.S. The developer of this plugin is looking into the situation. He is doing some tests with my current configuration. Hopefully he will find a proper fix soon!

@arne,

Some oddly good news. I posted a screen grab of my Webmaster Tools issue earlier. It has a ton of ‘X’s in the validation list.

I haven’t changed anything since and I’m still using beta 4. However, there are now many more check marks than before. I had already forced Google to update everything before, but not much had changed.

Here’s the results now: https://i.min.us/idjRj8.png

It looks like it’s almost fixed itself. It could be an issue on Google’s end. Your plugin might actually be just fine! ??

@arne,
Just deleted all the old beta3 files and uploaded beta4.

Once I did that and cleared my W3 Total Cache, I ran the Webmaster Tool again. After a hour or so, I had errors again.

Here’s a screen shot of the error messages:
https://min.us/ihjJm.png

Google is able to access my server, so that’s not an issue. Otherwise no sitemaps would have been detected. Some are working, others that have an X on it show this message:

We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit.

Let me know if you would like me to help you run any tests.

Thanks!

Sorry for the double update, but unfortunately the sitemap check failed with Google. The error message is the same as what I quoted above.

This plugin used to work perfectly in the past. However it stopped working about a month or so ago.