[allura:tickets] #7213 Discussion edit/reply non-functional in IE11 (at least) [ss6846]
- **status**: validation -- closed --- ** [tickets:#7213] Discussion edit/reply non-functional in IE11 (at least) [ss6846]** **Status:** closed **Milestone:** forge-apr-4 **Labels:** p3 support 42cc **Created:** Mon Feb 24, 2014 05:41 PM UTC by Chris Tsai **Last Updated:** Thu Mar 27, 2014 09:42 PM UTC **Owner:** nobody [forge:site-support:#6846] In IE11 (didn't test other IE versions), if you click edit or reply on a discussion, it'll change as expected, but shortly after, it'll refresh, go back to the top of the page, and the edit/reply section is closed again. See: http://screencast.com/t/FSkNZwKMcKE0 --- Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7168 Wiki macro to load content from repository
- **status**: code-review -- in-progress - **Comment**: This is pretty awesome! I love it that it is only a few dozen lines of code, reusing logic that's already elsewhere in Allura. Some feedback: Project queries should always include the neighborhood (since the same shortname can be used in multiple nbhds). `M.Project.query.get(shortname=parts[0])` Probably use the current nbhd. We could enhance later if you want to reference across neighborhoods. Can you add a repo example or two to the Includes section of the markdown formatting help? Minor: I wonder if the `app.repo.is_file` check could be avoided thus save a little time from hitting the repo twice. Could we just catch any error from `get_path()` or something like that? --- ** [tickets:#7168] Wiki macro to load content from repository** **Status:** in-progress **Milestone:** limbo **Labels:** for-community 42cc **Created:** Wed Feb 12, 2014 05:36 PM UTC by Chris Tsai **Last Updated:** Thu Mar 27, 2014 10:10 PM UTC **Owner:** nobody It would be really nice to have a wiki macro that could pull content from a repository. If we had this, we could include general end-user usage docs of the Allura platform (as opposed to the more operator geared docs at allura.sf.net), which would be distributed along with the Allura platform. This would also make it easier for general Allura docs to live side-by-side in a wiki that also contains more site specific information (like SourceForge). I believe this would also be a viable alternative to feature requests such as https://sourceforge.net/p/forge/feature-requests/58/ and https://sourceforge.net/p/forge/feature-requests/31/ --- Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #7168 Wiki macro to load content from repository
Oh, and also it seems you can remove the `|safe` from the `text` output since `h.render_any_markup` and `g.highlight` return a Markup object (aka string flagged as safe). --- ** [tickets:#7168] Wiki macro to load content from repository** **Status:** in-progress **Milestone:** limbo **Labels:** for-community 42cc **Created:** Wed Feb 12, 2014 05:36 PM UTC by Chris Tsai **Last Updated:** Fri Mar 28, 2014 06:18 PM UTC **Owner:** nobody It would be really nice to have a wiki macro that could pull content from a repository. If we had this, we could include general end-user usage docs of the Allura platform (as opposed to the more operator geared docs at allura.sf.net), which would be distributed along with the Allura platform. This would also make it easier for general Allura docs to live side-by-side in a wiki that also contains more site specific information (like SourceForge). I believe this would also be a viable alternative to feature requests such as https://sourceforge.net/p/forge/feature-requests/58/ and https://sourceforge.net/p/forge/feature-requests/31/ --- Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
buildbot failure in ASF Buildbot on allura-site-staging
The Buildbot has detected a new failure on builder allura-site-staging while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/allura-site-staging/builds/13 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-cms-slave Build Reason: scheduler Build Source Stamp: [branch allura/site] 1582854 Blamelist: brondsem BUILD FAILED: failed compile sincerely, -The Buildbot
