bbPress

Simple, Fast, Elegant

bbPress support forums » Requests and Feedback

[sticky]

Dropping "MultiViews" support?

(17 posts)
  • Started 3 weeks ago by sambauers
  • Latest reply from bryan868
  1. One of the major stumbling blocks for implementation of permalinks is the creation of the .htaccess file.

    There is at least one ticket requesting automation of the creation process via the admin area of bbPress (just like WordPress does). But the problem with that is that we support both the "MultiViews" and "mod_rewrite" methods of creating permalinks.

    In light of this and some other problems with "MultiViews" I'd like to gauge the possibility of dropping "MultiViews" support in favour of "mod_rewrite".

    What do you all think? Do you use "MultiViews" or "mod_rewrite"? Why? Would you really miss "MultiViews" support?

    Posted 3 weeks ago #
  2. Drop MultiViews.

    Posted 3 weeks ago #
  3. Considering most people are probably on shared hosting, and hosts like to disable random things for their various nefarious reasons (in the name of security, usually), I would say keep on supporting both if possible.

    I know DreamHost, for one, has it turned off.

    Posted 3 weeks ago #
  4. bbPress needs the internal rewrite engine that WordPress has.

    Multiviews is unreliable and availability is inconsistent.

    Posted 3 weeks ago #
  5. _ck_: hear hear!

    phreakymonkey: Dreamhost has what turned off, mod_rewrite or MultiViews?

    Posted 3 weeks ago #
  6. I'm going to stick this to the front of the forums for a few days to get as much reaction as possible.

    Posted 3 weeks ago #
  7. Using .htaccess is more or less the standard now... any host that turns off .htaccess rewrites is surely going to turn off multiviews as well, so there's very little benefit to keeping both.

    Posted 3 weeks ago #
  8. Dreamhost does allow mod_rewrite. And technically they do support Multiviews, but as a .htaccess hack.

    However. I remember having terrible trouble trying to configure BBPress to use Multiviews, because it appeared to work, but didn't on certain pages. I ended up manually adding mod_rewrite.

    As an aside, in automating anything like this, keep in mind that people like to do strange things with their directories. One of the annoyances of Wordpress is that it assumes almost complete control of the layout of all directories below where it is installed.

    Posted 3 weeks ago #
  9. chrishajer: Ah, sorry. mod_rewrite

    timskii: I could have sworn they had it turned off at some point, but maybe I am misremembering. The point is that hosters tend to do stuff like that (often without warning), so as robust a solution as possible would be ideal, naturally.

    *I'm a designer, not a coder, so I'm mostly talking out of my ass.

    Posted 3 weeks ago #
  10. HowToGeek: I wonder if that's really true. I'd like to believe it is, but I wonder if there are really hosts that allow the MultiViews directive in an .htaccess file, but don't allow mod_rewrite. I'd like to believe it's true so that MultiViews goes away and bbPress gets proper rewriting via mod_rewrite, the sooner the better. And have bbPress generate the rewrite rules then create or edit the .htaccess file automatically, just like WordPress, while you're at it.

    Posted 3 weeks ago #
  11. Can you clarify the impact of disabling MultiViews? Will this impact only bbPress content on a site, or do you need it turned off for the whole site?

    I like to mix WordPress, bbPress, and plain content for some images, PDF manual downloads, etc., and really need content negotiation/MultiViews supported in directories outside of WP/bbPress.

    And why is Mod_Rewrite better than MultiViews for bbPress?

    Posted 3 weeks ago #
  12. This would not impact anything other than bbPress, it's just a question of choosing one methodology to support pretty URLs.

    MultiViews could still be enabled on the server, it's just a question of whether bbPress uses it or not.

    Mod_Rewrite is better for a couple of reasons. For a start it is better supported, and it is also a lot more flexible. We are thinking about running all requests through a single page (index.php) just like WordPress. This is called a front controller, and is not as easily achieved with MultiViews.

    There is also the desire to reduce the amount of support traffic around this topic and standardising on one approach may help that.

    Posted 3 weeks ago #
  13. > the desire to reduce the amount of support traffic

    That's the best reason right there. Convert to a front controller, mod_rewrite and create the rewrite rules automagically, like WordPress, and 1/3 of the posts on this forum would never have happened.

    Posted 3 weeks ago #
  14. For me, mod_rewrite is the standard... I just never heard about MultiViews :(
    I begun programming php things since 5 years, even if I don't do it professionaly

    Posted 2 weeks ago #
  15. i wish i knew enough to offer an opinion. i've known about mod_rewrite for years from trying to configure drupal and wordpress. never heard of/used multiviews... hope that helps.

    Posted 1 week ago #
  16. hmcnally
    Member

    For those using a 1and1.com hosting package, try adding..

    Options -MultiViews

    to the top of the .htaccess file, and append the mod_rewrite stuff after it. I guess with their shared serving packages, the MultiViews just goes nutty (apparently it's enabled, though), and needs to be turned off before using mod_rewrite. They actually document this behavior at http://faq.1and1.com/dedicated_servers/managed_server/3.html

    I guess this means I'm in favor of dropping MultiViews, though not fervently.

    Posted 3 days ago #
  17. Definitely drop MultiViews

    Posted 3 days ago #

RSS feed for this topic

Reply

You must log in to post.

Code is Poetry.