Hey guys, long time! 🙂
Anyway I’ve got a new plugin for you to try: Faked Folders. It’s supposed to be my idea of static-posts done right…
- Creation of pseudo-folders for easier management.
- Custom templates.
- Enhanced plugin support allowing you to choose which plugins are activated for which folder.
- Supports comments in static-posts, allowing for quick guestbooks and such.
And more I’m sure once people start using it. Let me know what you think!
First note on this plugin: the edit-link for posts that are attached to a faked folder does link to your own site instead of to the get_settings(‘siteurl’). You maybe should switch that 😉
Additional problem: your plugin conflicts with the wpstats plugin. The call to the_stats does break when you access a static page. Actually this came into play by using the default template – you use the index.php page for this? You might want to elaborate a bit more on what to do with templates and where to place them.
Ok, more digging, more problems 😉
I now understand where templates are stored and how to work with them. I did discover though that there are some problems with plugins and faked folders. Somehow my plugins don’t get loaded, the defined functions in the plugins are not available.
Another problem I found was that the rewrite rules do create a p= parameter, but the plugin itself does try to use the p parameter, but it isn’t set from $_GET. You do check $_GET[‘static’], but you use $p directly. I don’t understand what the use of isset ($name) is in your plugin code where you “take over” wordpress, as that variable is nowhere defined. The $p not initialized problem is easily overcome by pulling it out of the $_GET array. But the problem with the plugins is still there.
I do use WordPress 1.2.
Weird. The plugins are now loaded correctly, the only thing that still is missing is the $p thing. Don’t know why and don’t know how, but it does work now. Nonetheless it’s exactly the plugin I waited for 😉
Thanks for the feedback! This should really teach me not to release plugins during hectic times…
Anon: The changes were made. Sorry about that! When I was coding that part I had other things on my mind I guess (ahh, mosquito… the perfect scapegoat!). 😉
Hugo: to be honest I’m not quite sure what’s going on with the variable scope in that section of code… My only thought is there must be some extract() or something similar hidden somewhere… I do know that my PHP installation is strict in that regard (well as strict about variables as PHP can be), so if it works here it should work there. 🙂
As far as your plugin problem, I’ve “fixed” that. New installations of Faked Folders will transfer their currently activated plugins over to any created folders (they can still pick and choose which plugins they want in the edit screen however).
And that brings us to v1.01. 😀
*adds this to my list of things to try out one of these days.*
I think I am having troubles installing this plugin.
the install seemed to go well, and so did activation. However when a Tried to assign a document to a folder, I was confronted with this error:
Warning: file(/srv/www/htdocs/bryan/.htaccess): failed to open stream: No such file or directory in /srv/www/htdocs/bryan/wp-content/plugins/faked-folders.php on line 355
Warning: implode(): Bad arguments. in /srv/www/htdocs/bryan/wp-content/plugins/faked-folders.php on line 355
Does HTAccess need to be present for this plugin to work?
Has anyone else encountered this error?
Unfortunately yah, it does run on .htaccess juice. If you have another method you want implemented, let me know because I’m interested in making this plugin as compatible as possible…
BTW: if you patch wp-admin/edit-post-advanced.php to include “static” as a status option for post editing, you will be able to edit static pages without the problem that the status is reset to draft on each edit.
Yes, Guvner, I was getting the same errors, but I didn’t know if I had done something incorrectly. I tried to change the permissions on all the files that I thought the folder may be using, but that fixed nothing. Any suggestions?
Parse error: parse error, unexpected T_CONSTANT_ENCAPSED_STRING in /www/xx/xx/public_html/1 on line 40
Im getting this kinda error? Any ideas why?
Dextrine: it looks like a template error, but that’s just me guessing. Where are you getting these errors? How much of the plugin can you get running?
And error pages. Love the idea, have no clue why I didn’t think of that before. 🙂
They are possible with this plugin (I got mine working) but they require a bit of messing with the .htaccess file itself. I’m not sure what caused the errors you guys got, but I’m curious what rewrite rule you used. To make things easier for the next batch that tries this I’m going to incorporate error pages into the next release. Thanks for the feedback!
That’s what I’m looking for I think. Thanks a lot, I’ll give it a try 🙂
Can I include PHP scripting in the text files?
I am still getting the errors as Guvner’s first post, and I checked out the code and it has to do with trying to write to /tmp .
For some reason that fails (I should have access to /tmp) and it won’t fall back onto the local file fakedfolders.txt.
I commented out using /tmp and forced it to use my 666/777 chmod’d fakedfolders.txt and it still says it doesn’t have access to write to the file.
- You must be logged in to reply to this topic.