Priority: Urgent
Current State: Closed
Released In: 1.2.0
Target Release: minor
I just noticed there's no way to navigate to the wiki from configure (whether it works or not)
Reckon this is a release blocker, as it really does affect usability. Perhaps the link can open in a new window?
--
CrawfordCurrie - 20 Feb 2015
I've been tinkering with a tab that would hopefully have no cfg settings on it. I was thinking that it would have links to important topics in the wiki: Install guide & Part 2, User Registration,
SitePreferences, ... topics where someone would want to go from configure Then tabs would be:
- Core dependency report
- extension dependency report
- System information
- Environment info.
I've found I needed to call
Func::expandCommonVariables()
and
Func::renderText()
in
LoadSpec::_extractSectons()
. It works well, but needs some js tweaks:
- Don't hide these tabs when no variables are on them
- Don't insert the ...more link, which completely breaks the rendering of the | table | layout in the macro expansions.
- And the table layout is a bit rough, due to vertical centering.
- Maybe the plugin diagnostics output.
Or another option would be to use jquery to render the pages from the system web. I'm unsure as to whether this info belongs primarily within the system web, in configure, or in both.
--
GeorgeClark - 21 Feb 2015
Definitely in the System web.
LoadSpec almost certainly shouldn't make those calls. It may be OK - don't forget to run configure from the command line to check.
--
CrawfordCurrie - 21 Feb 2015
Added a link, leaving open for Georg in case he wants to do more.
--
CrawfordCurrie - 25 Feb 2015
I'd like to do more, but I'm not really sure how to go about it. As you pointed out, adding those calls to LoadSpec crashes command line configure. I think the other way to get complete rendering in a tag would be to add
RenderPlugin as a dependency. Not sure what else to do, so I'm closing this. More detailed in formation in configure can come in some future release.
--
GeorgeClark - 04 Mar 2015