[jira] Assigned: (FOR-1168) Sample pages that fail validation
[ https://issues.apache.org/jira/browse/FOR-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian M Dube reassigned FOR-1168: - Assignee: (was: Gavin) Removing assignment to emeritus member. Sample pages that fail validation - Key: FOR-1168 URL: https://issues.apache.org/jira/browse/FOR-1168 Project: Forrest Issue Type: Bug Components: Documentation and website, Plugin: internal.dispatcher Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.10 The main 'sample.html' passes validation fine, however some other pages fail xhtml 1.0 strict validation. Mainly due to the use of the + symbol in name anchors. Not a problem for sites validating to HTML4.01. These pages include (but check for more) samples-b/usemap.html samples-b/xinclude.html samples-b/static.html samples-b/linking.html samples-b/howto-wowto.html samples-b/embedded_html.html samples-b/ascii-art.html locationmap/index.html samples-c/subdir/index.html samples-c/showonlywhenselected/page1.html samples-c/showonlywhenselected/page2.html pluginDocs/plugins_0_90/index.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FOR-1183) Forrestbar search of Jira issues broken, perhaps changed Jira search syntax
[ https://issues.apache.org/jira/browse/FOR-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian M Dube reassigned FOR-1183: - Assignee: (was: Gavin) Removing assignment to emeritus member. Forrestbar search of Jira issues broken, perhaps changed Jira search syntax --- Key: FOR-1183 URL: https://issues.apache.org/jira/browse/FOR-1183 Project: Forrest Issue Type: Bug Components: Tool: Forrestbar Reporter: David Crossley When searching our Jira Issues using Forrestbar, the upgraded ASF Jira now seems to intercede with smart query. However, it seems to lose our search terms, and just finds all Forrest issues. Perhaps the Jira search syntax has changed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FOR-1213) remove required plugin org.apache.forrest.themes.core from various plugin forrest.properties
[ https://issues.apache.org/jira/browse/FOR-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian M Dube closed FOR-1213. - Resolution: Fixed Fix Version/s: 0.9-dev Updated affected forrest.properties files. remove required plugin org.apache.forrest.themes.core from various plugin forrest.properties Key: FOR-1213 URL: https://issues.apache.org/jira/browse/FOR-1213 Project: Forrest Issue Type: Bug Components: Plugin: internal.dispatcher, Plugin: themes.core Affects Versions: 0.9-dev Reporter: David Crossley Fix For: 0.9-dev The plugin org.apache.forrest.themes.core resources moved to the DIspatcher plugin. Various plugin websites are already using the Dispatcher, and so need their project.required.plugins changed to remove themes.core -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-1214) Fix Dispatcher documentation: old org.apache.forrest.themes.core
[ https://issues.apache.org/jira/browse/FOR-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977891#action_12977891 ] Brian M Dube commented on FOR-1214: --- grep results for themes.core: src/documentation/content/xdocs/dispatcher-glossary.xml: definitionHooks are applied currently in the themes.core plugin as src/documentation/content/xdocs/int/index.xml: a) custom implementation of the themes.core plugin src/documentation/content/xdocs/int/index.xml: b) themes.core plugin src/documentation/content/xdocs/how/howto-dispatcher-quickstart.xml: ,org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core/li src/documentation/content/xdocs/how/howto-dispatcher-quickstart.xml: FORREST_HOME/whiteboard/plugins/org.apache.forrest.themes.core/note src/documentation/content/xdocs/how/howto-dispatcher-quickstart.xml: space. Forrest finds the default contract in its core (the themes.core src/documentation/content/xdocs/how/howto-dispatcher-contracts.xml: org.apache.forrest.plugin.themes.core/themes/common/html/blank.ft/code./p Fix Dispatcher documentation: old org.apache.forrest.themes.core Key: FOR-1214 URL: https://issues.apache.org/jira/browse/FOR-1214 Project: Forrest Issue Type: Bug Components: Plugin: internal.dispatcher, Plugin: themes.core Affects Versions: 0.9-dev Reporter: David Crossley The Dispatcher plugin documentation still refers to the old org.apache.forrest.themes.core -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-1168) Sample pages that fail validation
[ https://issues.apache.org/jira/browse/FOR-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978013#action_12978013 ] Gavin commented on FOR-1168: I am still a committer. No time to do anything currently so what you did was ok, but don't assume I have left the project altogether. Gav... Sample pages that fail validation - Key: FOR-1168 URL: https://issues.apache.org/jira/browse/FOR-1168 Project: Forrest Issue Type: Bug Components: Documentation and website, Plugin: internal.dispatcher Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.10 The main 'sample.html' passes validation fine, however some other pages fail xhtml 1.0 strict validation. Mainly due to the use of the + symbol in name anchors. Not a problem for sites validating to HTML4.01. These pages include (but check for more) samples-b/usemap.html samples-b/xinclude.html samples-b/static.html samples-b/linking.html samples-b/howto-wowto.html samples-b/embedded_html.html samples-b/ascii-art.html locationmap/index.html samples-c/subdir/index.html samples-c/showonlywhenselected/page1.html samples-c/showonlywhenselected/page2.html pluginDocs/plugins_0_90/index.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
