Wiki Farm specific test planThese are the things that we need to make sure work to sign off on the current changes. Donald’s replies are in blue. David’s replies in green. John’s comments in red.
Issue: new farms are created with their own PmWiki group as part of the farm - see link below for list of default pages in a newly created farm: http://intranet.affinity.co.nz/tertiary/NearFarm?pagename=Main.HomePage&action=search&group=&text=+ Farms start off with the same content as any other PmWiki instance: do you want them to start off with any content at all? Obviously would need to start with some content - in terms of physical pages - there seem to be about 4 required pages to start an initial group. How about starting with just the Main group and we write up a customised home page that says that you have successfully created a new farm - go to a help for more info on setting up your form. Create new groups by … and anything else absolutely basic to getting started. This will require some thinking. By default, it starts at the Main.Home Page that’s in the core distribution. Any upgrade will over-write this. And because Main is not shared, any edits we make to the Main.Home Page are only visible to the home field. And we don’t want a new field to “home” to a shared group, because then if someone edits that page, they are editing a page in the home field, not the local field. Off the top of my head, the only thing I can think of is including a wikifarm/wikilib.d/ directory that contains a minimum set of custom Main pages (I think it’s the 5 from wikilib.d). That’s the way you’d have to do it. Has been implemented. Looks OK. Adding farmtrail markup at bottom of default Home Page would be helpful.
Issue: on farms, the Tertiary Wiki link at bottom left goes to ThisFarm/Main not TiWiki/TiWiki Probably a template issue - looks like John’s fixed this already. Fixed. Works.
Issue: on the farm trail - there is a link called ‘Farm’ which links to the TiWiki/TiWiki page - we need to (a) decide if that link should be in the farm trail, as it is the central home, not the active farms and (b) what we call it - ‘farm’ is not very clear, TiWiki would be better. Now fixed in my development version: the link is the name of the default page in the main farm, i.e. TiWiki. New scripts installed. Should be fixed. Works.
Successfully made TESMon a shared group - but had to put a pagename as well as group name in the link on the farm management page - is this right? Just saying GroupName/ or GroupName. isn’t valid PmWiki link syntax. But was TESMon shared even when PmWiki didn’t render the group reference as a link to the group? have tested it with TES Doc and even though it doesn’t show as a valid link on the farm management page - it does create it as a shared group on the farms. If you want the links to look nice, of course, you probably want to say TESDoc/TESDoc rather than just TESDoc/
Created a shared profiles group on the main farm. On the main farm Recent Changes, the author names links point to Profiles/AuthorName. Tested it on a farm, and found on recent changes that the author name links point to ThisFarm/Profiles/AuthorName - ie the local farm profiles group - not the shared profiles group. This sounds really wierd: it looks like the Profiles group isn’t being shared at all. And I can’t reproduce it on my development server. Will investigate. Replaced all scripts with the current versions. Should be fixed. Works - points to shared group. The problem was a {{ }} around the link to Profiles.
uploads appear to be disabled on new fields - is that right? Could we have the default to be uploads enabled? Uploads are enabled and it has created the uploads directory correctly. It may be a permissions problem. What exactly happens when you try to upload a file? this time got to the uploads screen. specified the file to load and pressed upload. After a while got a PM Wiki? error message about directly permissions. I recall this has been an existing issue - that the first upload in a new group requires the administrator to change the permissions for the upload directory to be created. It is a permissions problem. I seem to have it working on my development box, but it requires chmod 2777ing the wikifarm/FarmName.upload and wikifarm directories. It appears to be going through the uploads process now - getting to the upload screen and then being told that it has been successful. But no picture on the page and no list of existing uploads when I go back to the uploads page - so might still be a permissions/directory problem somewhere. (No picture on page could be a problem with our web connection)
edit password is working on different farms. Created Duck Pond as a new farm after the password was enabled and password works fine. However, everytime you edit a page in a different group, it asks for the password. A little annoying in doing testing across fields and groups - but probably no so bad in ‘real life’ as mostly people will be editing within one group at one time. Is this an effect of the way it is set up? This is supported in the 0.6.15 version of PmWiki — see http://www.pmichaud.com/wiki/PmWiki/ReleaseNotes6. Once these tests are complete, we’ll upgrade to the latest version and re-test. Try it again now (I reconfigured the local setup). Working fine now - just had to enter the password once in the session and was able to edit pages in different groups and fields without having to enter it again. Additional questions and issuesThese are questions and issues that arose during testing that don’t need to be addressed for sign off. But they do need to be considered before sign off in case of any implications for fundamental design.
Test page: http://intranet.affinity.co.nz/tertiary/AFarmTooFar/MyLand/Paddock Working correctly: T: mark up, para referencing within fields, including across groups, page trails that go across group. Not working: references to pages in other fields - but need to decide how much of this is a requirement. Putting pages from other fields into a trail is likely to be unusual - but using [[para: ]]] to reference a page in another field may be more common. The I expected it would be something like that. Lets leave as is. Question: page trails seem to have turned into rings - was this intended? If you link to the first stop a second time in the list, the trail turns into a ring. This is a trails feature. which is exactly what has happened on the test page - where I have tried out six different markups for the same trail.
Works fine within a page and across groups in the same farms. It also works fine with shared groups from the main farm. Doesn’t work at all between farms. Not a major issue - but would be nice to be able to link to a position on a page in another field - particularly for reference pages that have a whole series of items and explanations on them - eg a definitions page. This may be do-able. It is do-able. Done, even. Not quite - links point to the page OK but loose the #anchor reference. A work around for this is to put all reference pages that might have wider value to projects in to a shared group. Takes a little foresight and cooperation - that’s all! btw have incorporated this idea into proposal for monitoring field - ie to created a shared reference group for lists of common acromyns, definitions etc.
Presumably each field can run its own calendar. I tried to create on on ‘A Farm Too Far’ but came up with a standard edit screen. Does this mean it is a field specific customisation? And a reasonably straight forward one? This is a configuration option, now changed. It had been configured to load the calendar script only for the home Calendar group. It now always loads the calendar script, but the style sheet only loads for groups called Calendar. It works now. Check out the blogging features. working fine. Have set up both a shared calendar and a local calendar in a farm too far - and able to create links to both.
If a group doesn’t have a page called HomePage, then the ThisGroup link at the bottom left of the page will go to the Main group’s home page as a default. We assume this is a configurable behaviour, if for some reason we wanted a group’s ‘home page’ to be called something else - ie could add something to the group config file to define the home page. The default PmWiki behaviour is to look for a page called Group, then for one called Home Page. This is configurable through the group.php and field.group.php files, using the $DefaultTitle variable.
Should we be able to use ThisFarm as markup within a link? what would the correct markup be? Try ThisFarm:/Group/PageName — it works for me
Can we have the shared profiles group as a default and then choose to operate a local profiles group for an individual farm if we want to? |
|