Ticket #581 (closed new feature: wontfix)
Press page
| Reported by: | guaka | Owned by: | crumbking |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | BW General | Keywords: | press, wiki |
| Cc: | guaka |
Description
Create a press page.
http://bewelcome.org/press should be an integrated page coming from the BV wiki, http://www.bevolunteer.org/wiki/Press
Change History
comment:1 follow-up: ↓ 9 Changed 4 years ago by guaka
- follow_up changed from none to move to alpha
- Owner guaka deleted
comment:2 Changed 4 years ago by lemon-head
- http://test.bewelcome.org/press
- http://test.bewelcome.org/mediawiki/press
- http://test.bewelcome.org/about/press
don't work for me.
I set this to "test".
Anyway, wouldn't it make sense to make this part of the "about" application?
Also have a look at the "externalcontent" app - we can reuse the ExternalContentWidget?, which allows to replace hyperlinks (so far only works if the hyperlink is given as absolute link, as in WordPress?). See
- http://test.bewelcome.org/externalcontent (wordpress)
- http://test.bewelcome.org/externalcontent?http:;;www.bevolunteer.org;wiki;Press (mediawiki). Problems here: (i) Replacing relative hyperlinks does not lead to good results. (ii) picking DOM elements by id uses ids that only appear in wordpress. This could be easily adjusted to MediaWiki.
Other funny things could be:
- we make subpages in our mediawiki: "About/Press?", "About/Xyz?" etc. Then, given a request "about/press" or "about/xyz" in bewelcome, we can automatically display the page "
- Allow groups or members to have their own external content pages. We would have to approve every such inclusion, to make sure we don't run into legal trouble. See #320, "include member content from other sources"
- Create an admin backend to map request urls to external content pages. The mappings would be stored in a database table.
comment:4 Changed 4 years ago by lemon-head
- Type changed from unknown to new feature
- Component changed from unknown to BW General
comment:7 Changed 3 years ago by kiwiflave
What s still needed here? Texts? Or technical implementation? I can help with texts.
comment:8 Changed 3 years ago by midsch
- follow_up changed from test to review code
Still valid questions:
- who is working on this? how should it work?
- What s still needed here? Texts? Or technical implementation? I can help with texts.
(Set this to review until it's clear what has to be tested.)
comment:10 Changed 3 years ago by feuerdaemon
What is the status here anyway?
comment:11 Changed 7 weeks ago by crumbking
- follow_up changed from review code to none
- Owner set to crumbking
- version set to production
- Status changed from new to assigned
- Milestone changed from unassigned to 0.5.5 - bugfixing
I suggest to close this ticket.
As we have a press page with some content.
See: http://www.bewelcome.org/wiki/press%20information which is linked from http://www.bewelcome.org/about
An advanced version would be a page which we could translate. But as we are on bugfixing mode let's do this drupal. If you agree close the ticket.
comment:12 Changed 7 weeks ago by globetrotter_tt
- Status changed from assigned to closed
- Resolution set to wontfix
- Milestone 0.5.5 - bugfixing deleted
right, this has not high priority, but no need to include it in the next milestone.



in code: r5131
now waiting for wiki :)