1

(63 replies, posted in Feature requests)

Rickard wrote:

If you're going to use 1.3 in it's current state, I would wait a day or two. I have a bunch of revisions to merge from the 1.2 branch.

Would you be so kind as to post a message here once those commits have been completed? I have a few site launches that have been on hold pending those revisions, and it would be great to get them up as soon as possible.

Thanks a bunch, Rickard!

--Justin

FYI, the new URI structure that Rickard has implemented in 1.3 is very well done. While Rickard's implementation does not include the topic name in the URI (as Connor already pointed out), it is still a flexible and well-built design. I suppose this mod might be useful for those don't plan on upgrading to 1.3, but otherwise I think the URI structure in 1.3 pretty much obviates the need for this mod.

Until LucidCMS supports a customizable URI structure and RSS feeds, it certainly wouldn't work for our needs. But it seems to be a nice start in the right direction.

As has already been discussed earlier in these forums, "search engine friendly URLs" are mostly an anachronistic misnomer. While Google previously did not index sites that passed more than one parameter in the URI, they changed that behavior a long time ago. If you want proof, do a Google search for the following keywords. You'll find that -- lo and behold -- this very forum topic is right at the top (even with it's "non-friendly" URL):

feedback wanted URL rewriting

Semantic URI structures are superior not because of search engine relevance, but for reasons having to due with URI permanence and aesthetic readability.

As to what to rename the file, something along the lines of "Apache-Directives.conf" would probably be the most accurate. As noted above, these directives should go into the httpd.conf file provided the site admin has write access to it. If not, then the user should upload the directives to the server and rename it .htaccess. There are several reasons why httpd.conf is preferable to .htaccess files, the most important of which is performance. If .htaccess overrides are enabled, Apache has to look for them in each and every directory, thereby increasing CPU load.

coaster: WordPress will only create the .htaccess file if the web server process has write access to the relevant directory, which for many people may not be the best arrangement from a security perspective. Of course the user could create an empty .htaccess file, give it the correct permissions, and then let WordPress edit it, but in that scenario you might as well just have the user paste the directives at the same time they are going to the trouble of creating an empty .htaccess file.

Just my two cents... smile

I agree that having everything in one place would be nice. In that case, however, I would recommend changing the file name in the distribution. If the Apache directives remain solely contained in a file named ".htaccess", the likely result will be a lot of very confused and frustrated non-Windows users.

Rickard wrote:

The problem with renaming the .htaccess file is that on windows, you can't name a file .htaccess.

Mac OS X works the same way -- you can't create a file that starts with a period unless you're comfortable with a command line. The standard GUI procedure here is just as you suggested: upload the file and then rename it on the server. I don't think too many people will have trouble renaming the file on the server end, as every FTP client I've ever seen can rename files in a snap.

That said, I see no harm in providing the information in more than one place. In addition to the .htaccess file, why not also include the needed directives in the readme/install docs? That way, non-Windows folks can simply copy and paste the directives into httpd.conf or an .htaccess file as needed.

I tested this as much as time allowed over the weekend, and everything worked flawlessly. I'll do more testing this week, in anticipation of launching the first site based on 1.3dev on Monday. smile

My only suggestion at the moment would be to change the name of the .htaccess file in the archive. On Mac OS X and other *nix-based systems, the .htaccess file is invisible and thus does not appear to be included in the distribution. One potential solution to this problem might be to name it "apache.conf" and then tell folks that they need to change it to ".htaccess" before/after uploading it to the server.

The reason I suggested "apache.conf" instead of, say, "htaccess" is that .htaccess files are only needed in shared hosting environments where you don't have access to the httpd.conf file itself. While many folks use shared hosting, many others run their own servers. As per Apache's recommendation, .htaccess files should only be used when you don't have the ability to simply insert the relevant directives directly into the httpd.conf file itself.

Once again, fantastic work, Rickard! big_smile

Scratch that... It's there. FTP server seems a bit wonky, however.

That FTP directory looks mighty empty to me.

How about today? wink I would love to utilize the weekend to give it a thorough test drive...

That's excellent news, Rickard! I look forward to testing this over the weekend. If all goes well, I'll soon be able to launch the three sites that are currently waiting for this feature! big_smile

I'm sorry -- my suggestion assumes that you have access to a crontab. Many hosts do not provide this functionality to their users, unfortunately.

It's probably also worth looking at MarkDown, which some people find to be more syntactically intuitive. Adding support for another "dialect" is relatively easy once the parse/replace code core is implemented, so many content management systems such as WordPress and Drupal support both Textile and MarkDown.

Assuming you're able to run PHP via the command line, just call extern.php from cron every hour and save the output as a static HTML file. This technique is commonly used to reduce CPU load for RSS news feeds.

Rickard: Your ideas for the new post/topic URIs look pretty good to me.

Could you provide a bit of explanation as to the semantic purpose of these links? I gather than "tid" is for the topic ID, but I'm not sure what the "fid" and "qid" are for.

18

(25 replies, posted in PunBB 1.2 troubleshooting)

The sea of nested tables in that forum's markup is likely to win few converts. smile

I don't quite get it... Why does it have the potential to be better?

19

(17 replies, posted in PunBB 1.2 discussion)

Yup, lebel... CSS is just a load of hype. Umpteen nested table layers is soooo much more fun to navigate! Can you believe people want to control layout from a limited number of CSS files instead of dozens of HTML/PHP files? The insanity! And yes, the only reason PunBB switched to CSS was to gain a fraction of a second in loading times. Oh, by the way, pass the crack pipe, please.

[/sarcasm]

(Begins John Kerry rhetorical monologue...)

Could PunBB's CSS be streamlined and easier to navigate? Probably.
Would it be nice if PunBB supported drop-install theme packs? Yes.
Would we like to see your contribution to achieving the above? You betcha.
Do most knowledgable folks desire to revert to table-based layouts? Not a chance.

And now back to our regularly scheduled programming... wink

20

(17 replies, posted in PunBB 1.2 troubleshooting)

I'm confused. What does rss.php do that PunBB's built-in RSS generator (extern.php) doesn't do?

21

(28 replies, posted in PunBB 1.2 discussion)

Sunday is when Rickard's WordPress blog went up, so that's consistent with the time frame you mentioned, Paul. But it seems unlikely that comment spam bots alone would cause this, and if so, perhaps some changes on the server are in order. I've got a WordPress installation running with no server slowdowns, and that's on an older version (1.2) with fewer built-in anti-spam measures present than 1.5 has.

That said, I installed one anti-spam plug-in a while back, and I think that is probably helping a great deal: WP-HashCash. Realize that this only combats comment spam. For tips on fighting trackback spam, this section of the WordPress Codex should be useful.

22

(48 replies, posted in Feature requests)

Hmm... I use absolute CSS positioning all the time, and I have never had a problem with Firefox and the scroll wheel on my sites.

I wasn't suggesting that you should use UTF-8; that was only an example. I imagine the correct character set encoding for French is probably ISO-8859-1.

23

(48 replies, posted in Feature requests)

Glad you were amused by my comments, Rod. Guess I must have hit a soft spot. smile

For what it's worth, I wasn't trying to make this personal. I simply pointed out what appears (to me at least) a major inconsistency with your constant harping about putting users first. I never said Fantasya isn't a pretty site -- it is indeed a very nice looking site. Much better than I could ever design. But from a user friendliness perspective, it needs a lot of work. That's my opinion. I'm sure you couldn't care less. Great!

Your argument that "we" want boring sites is just silly. There are many fantastic looking sites that don't impede the capabilities of users' web browsers. I'm sure you have seen them before.

By the way, since when does one need to download a plugin to use the scroll wheel in Firefox? I'm not sure what you're talking about there. I have yet to see the need for that on any platform -- in my experience, if the OS supports the scroll wheel, so does Firefox.

Something to say about http://www.sortons.net/steac/ ???

Sure, if that is your wish.

Site design looks great. I'm guessing the site will render fine for viewers who have set their browsers to default to French, but on my browser (Firefox) the rendering was quite b0rked. You might want to include a Content-Type header to fix this. Something along the lines of...

    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

I can send you a screenshot if you like.

As I already tried suggesting once before, can we just agree to disagree on what's best for end users? I just don't think we're going to see eye-to-eye on this one.

24

(72 replies, posted in General discussion)

Glad to see that you're using the new WordPress release for your latest blogging foray, Rickard. I think you'll find out over time just how well-designed it is.

I tried to add your blog to my feed reader, but as Sander pointed out, it seems your rewrite rules are not active. Perhaps you need to restart your web server?

25

(48 replies, posted in Feature requests)

hcgtv: Classic! I'm definitely going to bookmark that site.

If you want some additional entertainment, check out the sites in Rod's sig. So that's what you call putting users ahead of webmasters? What a disaster. To cite just one glaring example on Fantasya... I hear it's really user friendly to intercept scroll wheel movements via Javascript -- preventing vertical scrolling via the mouse -- for the purpose of animating some bubbles. Yeah, I'm sure visitors to this site were clamoring to have their scroll wheel disabled.

The abject hypocrisy at work here is, as Rod put it, incredible (as in "not credible").