PKP Bugzilla – Bug 1292
Help topic IDs should be assigned in templates, not code
Last modified: 2013-05-29 14:48:42 PDT
We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.
I placed the help topic ids in the code because templates were getting reused by
multiple sections of the system. For example, the section editor's and editor's
share the same templates (e.g. metadata) considerably. I thought that inserting
the help topic id in the code would give a better account of what topic to load.
The logic to determine which help topic to load in the templates were getting
messy if 2 or more sections were reusing the same topic.
I don't mind moving the help topic ids back into the templates so I'll just wait
for your thoughts after my explanation for doing so.
Will defer this for reconsideration in the future based on Jason's comments.
I will be trying this out as part of the PKP platform redesign. Objectives will be
-- to move help file calls from class files to template files;
-- for each template to have some sort of clickable help widget as appropriate;
-- to possibly cull XML help files from one larger, more easily maintained XML file (eg. Docbook). This last point will probably merit a new bug entry.
Suggest deferring to 2.3 release -- no need to overhaul this for a stable release.
Deferred, to my chagrin.
DB Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Mai, your error message in comment #6 has nothing to do with this bug entry; please search through the support forum at http://pkp.sfu.ca/support/forum and post questions there.
Existing inline help is deprecated.