Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with non-WikiWord pages and symbolic links #820

Closed
ALuckyGuy opened this issue Oct 13, 2015 · 2 comments
Closed

Problems with non-WikiWord pages and symbolic links #820

ALuckyGuy opened this issue Oct 13, 2015 · 2 comments
Milestone

Comments

@ALuckyGuy
Copy link

FitNesse allows a user to create page names that aren't camel case but these cause problems with Symbolic links. For instance, you can create pages named "Databases" or "Environment1". However if you do this, in several scenarios FitNesse will not work properly.

First, consider the following:
fitnesse - test suite

and the following pages setup with environment variables defined and symbolic links to the test suites:
fitnesse - env links

SuiteSetUp works when testing Env A.
fitnesse - symlink camelcase works 1

It does not work when testing Env 1:
fitnesse - symlink camelcase issue 1
Notice too that the content of Test Page 1 actually gets pulled into the failed link. The page should have the content "Test Page 1", but instead it's just "Page 1" and the word "Test" appears at the end of the Suite Set Up link. It works fine in Env A

Additionally, if you name symbolic links without camelcase names, those fail too.
fitnesse - symlinks wo camelcase fail too
Results in this failure:
fitnesse - symlinks wo camelcase fail too 2

These problems aren't new - they've existed for quite a while.

One other problem I am seeing today with the Oct 10th release and appears new is related to creating SymLinks. I've noticed that if I create new links with a non-WikiWord name, as soon as I click "Create Link" the Properties page refreshes and the link is gone. In practice, the link has been created and if I force a refresh on the normal page, the symlink shows up. Re-opening the Properties page it does not show up, at least not initially. Eventually it does in fact appear on the properties page - it seems to be a caching problem. However I've only noticed this particular caching problem occuring with symlinks named as non-WikiWords - others seem to be working fine. That might be a coincidence because I've only been working with the Oct 10th release a few hours and most of the time has been spent documenting the other issues above. Edit: Scratch that - I've now seen it happen with WikiWord symlinks too. It just seems to be a general caching issue and not related to non-wikiword support.

@amolenaar
Copy link
Collaborator

I added some fixes for the October, will dig into this.

@amolenaar amolenaar added this to the Next release milestone Oct 16, 2015
@ALuckyGuy
Copy link
Author

Just be clear, this problem didn't just start occurring. It happens with the Aug 14th release and was occurring before that too. I just never got around to documenting it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants