This will come as a surprise to no one, but I’m officially ending support for Post From Site. If anyone wants to take over, let me know & we can discuss it.
I really want to make something simple & easy to use, and Post From Site as it is now just isn’t that. It doesn’t help that it was the first plugin I ever wrote, with zero experience in writing software for others to use.
So I’m starting development on Post From Site 2. It will have the same core functionality, plus WYSIWYG support (which I’ve been asked about ever since I first released it), with anonymous posting as a lower priority (that will be brought back before it’s submitted to the plugins directory). You can follow development at the github repo, but it’s currently just an outline, really- I’ll update when I have something worth installing, and of course again when it’s in the WordPress.org directory.
This release is a major rewrite of the plugin code. A number of features have been added, some of these include widget support, hooks for theming, the ability to have unregistered users post (using recaptcha [recommended, but not required]). More documentation at the end of this post.
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.
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.
This post is the last test of PFS before release. If you’re reading it, then v1.6.20 should be available for download sometime tomorrow (Saturday). Some new things:
- Proper image support
- Ability to create custom links for posting to individual categories (like suggested here)
- Better documentation and cleaner code
Probably more things too, but it’s near 3am and I can’t think. So, look for the release tomorrow!