Wedge

doesn't hurt to try ;) Also, I've never seen the term "cPanel" applied to my account.

Only way I can fix this (or at least try to find out what caused this) would be, at this point, to have FTP + forum admin accounts to your forum.
Sorry about that, but... Dunno what it's doing for you, really.

I've created an account for you and sent you a PM with the details. Please let me know what you find.

I mostly need ftp access to play with htaccess ;)

Don't worry I'm not going to abuse it. If anything you can just give me a custom account limited to your wedge folder.

oh yeah... that's what I get for posting after having a few drinks with a buddy... :P check your PMs

Ah yes, thanks..!
I'll look into it tomorrow. I'll have to juggle with House of Cards too, it's quite tempting, but I think I'll focus on Wedge first, because I have yet to commit all of my big changes from the last couple of days... (The 'hey' bit in the members table; changes to the settings file; modular main htaccess; and most importantly, the upgrade script!)
Remind me if I haven't been there by tomorrow night!

No problem. Thank you, sir, for your personal attention. I know you must be busy.

Hello all ;D

I have the same problem with the clean or pretty url, but I know that with rewrite mod over apache get better. So make that wordpress and another software too. But I am no a dev ...

Here a link to a wikipedia artice ;D
http://en.wikipedia.org/wiki/Clean_URL

Greetings

Gerriet

Okay, so here's what happened...

*If your Wedge forum is installed in a sub-folder*
And
*If your server is Apache 2.2.16 or better*

Wedge is falling back to the FallbackResource /index.php line in the htaccess file.

However, /index.php is an absolute URI, and thus it redirects to your www root's index.php, rather than your Wedge root's.
I used to do index.php without the slash, but it actually uses the current requested path as relative path, instead of the htaccess file's path. What does it mean..? Well, doing /wedge/profile/me/ will attempt to load wedge/profile/me/index.php, instead of wedge/index.php...

The solution (which I applied to eolith's forum):

Well, err... As stupid as it sounds, just get rid of the FallbackResource lines. And the version testing lines. Basically, below the "# Pretty URLs" line, just keep this:


It obviously takes more time than just FallbackResource... :-(

Now it all comes down to the fact that I've been working on making Wedge create the htaccess file automatically.
If I can't get the Apache version number (eolith's server doesn't disclose it >_<), I'd have to print the above code instead of the easier FallbackResource. But what if you then upgrade your Apache server..? You could then use the faster FallbackResource, but Wedge wouldn't know. Well, I guess you could 'simply' remove your htaccess file from time to time, and Wedge would recreate it with the latest available code, but... Anyway.

Sometimes, a compromise has to be found between ease of use and ease of development... Hmm.

I think I understand about 83% of that... :P

Thank you very much for that modification and the work to make it happen.

I took the easy way out (i.e. the coward's way), by removing all traces of FallbackResource, but it really hurts... :lol:
Still, first impressions are more important than later optimizations.