stevarino

Oh, and thanks for the heads up ieure. To be honest it was a typo on my part that implode was coded in that way, I didn’t even know that the string was optional! It will be fixed in 2.1, promise.
And my email is steve at stevarino with a dot and a com. Feel free to email me any suggestions, fixes, questions, whatever. ??

ieure: This is really why I need to get to documentation. I mentioned support for non-.htaccess weblogs. The trick is this: simply put “index.php” between your wp-install directory and your static file.
An example:
Your regular weblog is at “https://domain.com/blog/”. You create an about page using my plugin, and its URI should be “https://domain.com/blog/about/”. To get the same effect without using rewrites, try the domain “https://domain.com/blog/index.php/about/”. It looks like a normal redirected domain, but functions like a query string. ??
And thanks for the assistance with the support Guvner and ieure. One small note to what ieure said: if you want you could set “foobar” to be the folder’s index, in which case the uri would be https://mysite.com/static/

duches77: No offense, just manipulating a little peer-pressure ??
And my memory is absolutely terrible as well, however one nice thing about being a web-developer is the constant access to google.

If your host runs apache, try creating a file called “.htaccess” (no quotes or extension) in the same directory as your weblog. Then in the admin panel, click options and then permalinks. Set those options and then copy the code you recieve into your .htaccess file.
Not sure if you have apache or are allowed a .htaccess file? Try it anyway. ??

Your host should provide a mysql browsing tool such as phpMyAdmin. Once you find that simply browse to the options table and fix what you need.

ieure: What was causing the implode error? I developed this using PHP 4.3.6, so I should have recieved that too, right?
And everyone else: It seems the Guvner bug is immortal and there is no stopping it. However I’m working on 2.1 right now and that will have better debugging support for eliminating that meddlesome bug. ??
Also expect a better upgrade script (because the current one seems to be as useful as toast) and a “view page” method so you don’t have to worry about where your pages are.
all these bugs and requests… how can i ever expect to get this documentation done!?! ??

hm, so it was your browser that was doing it?

I’ve thrown together a rather complete static-posts plugin called Faked Folders. It’s compatible right now with 1.2 and 1.3 (so far), and I can’t see any incompatibilities arrising anytime soon. ??
If you need any help with it check out the support thread on it. ??

I’ve always been a fan of Churchill quotes:
“The best argument against democracy is a five-minute conversation with the average voter.”
“I have taken more out of alcohol than alcohol has taken out of me.”
Great man. ??

Well it’s perfectly possible to use one database for several wp installs. Simply alter the table prefix in wp-config.php.

Yes, even the Guvner Bug has it’s silver lining. ??
Okay, that info REALLY clears things up for me that you are getting these while trying to view your created static pages. In your last post about this bug you said you got the errors on line 837; are you sure that’s right? The way you describe it I imagine the line number to be >1040 or so…
I remember I once had a host who had their PHP installed in a really funky way in that what the ini-functions and phpinfo() would show wouldn’t necessarily be accurate. I’m beginning to worry that we have this case here. So if the error is between lines 1168 to 1176 (and only if) try making the following change:
if( ini_get('safe_mode') == '' &&
TO:
if( false &&
Hopefully that will bump you out of that error (and yes, I fixed the bug where people get stuck on the “create fakedfolders.txt” message). ??
To be honest I didn’t think you would have a template error. The way you were describing it and how you were handling it made me think that you would have figured it out by now.

“An explosion in a crayon factory” is right on… Very, ugh, colorful. I love it! ??
But while the colors are great (in their own special way of course), you don’t take advantage of any positioning or other such css attributes. I think that’s what will really persuade some table-advocates.
And right now I think WP has a bigger problem with the frame/iframe script-kiddies than ancient table fogies (IMO of course). ??

Boats?

“I’ll try installing 1.2 tonight and see if the plugin will work, then I can try and discover what change a€“ between versions a€“ is causing the plugin to fail.”
Sounds good! I’m going to install the 1.3 alpha tonight and we’ll hopefully find a solution. ?? But right now, work calls.

Why not try this… Enter /wp-comments.php and change this section:
foreach ($comments as $comment)
To this:
foreach ($comments as $comment_id => $comment)
Then anywhere in that loop you just have to call something like:
<?php echo $comment_id++; ?>. I’m sure if you wanted more control a plugin could enhance this, but it should work for now…
Try this:
<div class="commentnumber"><php echo $comment_id++;?></div>