Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options
Using/ in discussion does crash the discussion
elja
New
I did install and I am using Vanilla forum for the first time.
This is my forum :
http://senioren-reisgenoot.allerbest.nl/forum/
With testing everything did look fine.
I did get my first visitor that registered and posted. And then things went wrong. In the discussion title he posted :
Zeilzwerftocht Friesland 7/10 augustus 2014
And at that moment when you try to read the discussion : The forum get a File not Found problem.
I started thinking. And got the Idea that the slash could be the problem. Changed the title, and than it was OK.
Is it possible to solve this problem. I think that more people would put a / in the title in my forum.
Thanks,
Elja
Tagged:
1
Comments
I use Vanilla version 2.1
I have a test site set up. You can see the problem on the test site in discussion "weg van 4/4"
http://40pkus-reisgenoot.allerbest.nl/discussions
that is a server 404 not a vanilla 404 you can tell the difference:
http://40pkus-reisgenoot.allerbest.nl/discussion/8
That mean it is your server rules that aren't resolving the url, vanilla hasn't been reached.
grep is your friend.
And a % in the title gives a Internal Server Error
@x00
And how can I solve the problem?
I´am just a simple person. When I install a CMS and do nothing special I have the expectation that something basic as starting a discussion would work well
@elja
Vanilla 2.1 works fine 'out of the box'.
You must have done 'something' or it would be working.
Did you move any files/folders after your testing?
I did not move file´s or folders. I only installed and removed theme folders, plugin folders and installed application folder
And I have the same problem with both installs, When I would have deleted something accidentally, I would have made the same mistake twice? I do not think so.
Total clean installation. Done because the of the questions here. Nothing else done. Only did the installation.
Same problems
http://testen.allerbest.nl/
Sorry url is here http://testen.allerbest.nl/
sorry to be clear, it doesn't matter what you do with vanilla becuase it hasn't got to vanilla yet. This is a server level issue.
http://stackoverflow.com/questions/9206835/2f-in-url-breaks-and-does-not-reference-to-the-php-file-required
grep is your friend.
@elja
As you probably saw, I registered on your test site to have a look.
As you can see from here:
http://barspetsa.org/whu606wayback/
there is no problem with / in the title of my install, so this issue has to do specifically with your setup.
@whu606 is to do with url encoded slashes, and the restriction is to do with apache security.
grep is your friend.
I just dit install WordPress http://oef.allerbest.nl/
And I can put slashes and % in the titles of posts. So It is possible to make a programm that works with % an slashes in titles
you are not using any url scheme just post numbers, yet it is possible but you have to substitute the slash with something else.
grep is your friend.
http://codex.wordpress.org/Using_Permalinks
grep is your friend.
@elja
And as I showed you, it is possible to do with Vanilla.
See here, where there is a random mix of both / and % in a title, with no problem:
http://barspetsa.org/whu606wayback/discussion/7183/this-discussion-has-a-two-a-single-and-a-followed-by-a#latest
Unless you accept that the issue is to do with how your set up is relating to Vanilla, rather than an issue specific to Vanilla, you will not be able to resolve it.
Sure then can change the slug function
Gdn_Format::Url()but this is relatively minor issue, so may no get into any update in 2.1 of course you can post a ticket here:https://github.com/vanilla/vanilla/issues
otherwise change your apache settings
grep is your friend.
I thank you @x00 and @whu606 for trying to help me.
So you know what the problem cause is. It takes some time to look at all you wrote.
@elja
I can't say what is causing it, but if you look at this file (attached), you can see that the link to your discussion (which doesn't resolve) contains %20 in place of spaces, whereas mine (which does resolve) contains -
I don't think it is the issue, but in config.php do you have:
$Configuration['Garden']['RewriteUrls'] = TRUE;My link ignores the / sign, but your link translates it to %2F