The update to Post From Site on Sept 2nd was not supposed to go out as an actual update. If you downloaded it, it likely broke your site. What you should do is disable the plugin, and/or revert to 2.0.3. The plugin directory now shows the correct version.
As of Sept 5, 2.0.3 is the most current stable version.
If you’re interested in why this happened, my readme.txt – the file the directory uses to know where to find the current version of a plugin – was malformed according to expected format. So it didn’t know where to look, and grabbed the in-development version, which was a non-working screenshot of my code, basically.
In the past 12hrs I’ve added 3 bookmarklets to my browser. I don’t even usually use them, but these seemed too useful to not at least try out. So now I’m sharing.
- WhatFont Tool, by Chengyin Liu
- Inspect font on any site by hovering over the text, click on text to see the font stack. As someone who struggles with font stacks, this is an excellent way to see how other developers handle it.
- MIN, by Nathan Ford of Art=Work
- Strip a site of all color, borders, and background images. I haven’t used this enough to see if it’s actually useful to me -probably more useful to designers- but it is interesting.
The two above tools came from Sara Cannon’s Typography on the Web presentation at WordCamp Reno.
- Finally, Press This…
- …Which is actually what I’m using to write this. I’m hoping it will get me to post more often, and it’s working already. (It starts a post using the URL & title of whatever page you’re currently looking at, and copies in whatever text is selected).
A few weeks ago I gave a presentation on plugin development for the Northampton Web Developers’ WordPress group. At the end of my slides, I went through a simple plugin to ‘like’ posts. Below is the code I used, with some notes. Continue reading “Code from wordpress plugin presentation”
I’ve just released post-from-site v2.0.1, which fixes the unintentional bit of code left from development (that I left a path absolute from my dev environment). It should be working for everyone now, but let me know if something else is broken.
Any support questions should be asked here for v2.0.0+. I can only help if you give me information about your error: what error message you get, where in the process it’s failing, etc. I can’t do anything if you just tell me “it’s not working”.
And now I’m going to ask you all for help: I have this plugin installed here, but for some reason, the stylesheet is 404ing. It exists, and I’ve looked in firebug and the response text is the correct CSS, so I don’t understand why the browser is telling me the file doesn’t exist. Any ideas? I also had a similar problem with a JS file for a work project, and I never really solved it, just worked around it. They’re on different servers, so that’s not it. Any ideas?
EDIT 8/11/10 First thing: A co-worker figured out the 404 problem, which might be affecting others. The stylesheet calls a require_once on wp-blog-header.php which apparently does something to mess with the headers of the stylesheet (and the other files I had trouble with), so changing that to wp-load.php seems to include all the necessary functions. I’ll upload a fixed version tonight, also changing the div back to an a tag, since I got a few comments questioning that move (there honestly wasn’t much thought behind it, other than I usually ended up putting the link in a div so it would theoretically save code? Well, it’ll be an a again).
Second thing: Custom fields seem to be a much-requested item, so I’ll see what I can do. Widgetizing it also seems popular, but I’m not sure how that works so I’ll look into it before promising anything.
EDIT 12/07/10 Apparently I forgot to edit this post to say so, but I now have a forum for questions – one section is free community help, and the other is paid support where I promise to answer your questions. For that, however, you need to subscribe.
I wrote the first half of this on the train back from the city on Saturday night, so if tenses and time references are confusing, that’s why (though I tried to correct all). After a rough start (missing the 8:40a train by two minutes & having to wait for the 9:40, meaning I didn’t get to Baruch ’til 11:30, missing the morning panel I wanted to see), the first day turned out to be very nice. After lunch there was something I wanted to go to every timeslot, which to me makes the day a success.
So what panels did I go to, anyway?
Continue reading “My Weekend @ WordCamp NYC”