Closed Bug 676335 Opened 13 years ago Closed 13 years ago

discussion: investigate removing phpbb altogether

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect)

Product:
developer.mozilla.org Graveyard
Component:
Wiki pages
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: groovecoder, Assigned: groovecoder)

References

Details

(Whiteboard: c=discussions p=2 u=visitor) 

      No description provided.
Blocks: 674788
Assignee: nobody → lcrouch
I don't see any turn-key solutions. I posted in phpBB support forum:

http://www.phpbb.com/community/viewtopic.php?f=46&t=2137372&sid=215c0880bbb39f4adda61c7465412df0

If we don't mind keeping the MySQL database, we could use django-phpbb classes (https://code.google.com/p/django-phpbb/wiki/UsingDjangoPhpbb#phpBB3_classes) to write our own archive in django.
John's comment from bug 676610:

"After we put phpBB into read-only mode (see bug 674788), we will want to archive forum discussions in the least-expensive way possible. In our 1.0 planning meeting, Les and Luke mentioned that IT would probably prefer that we do not continue to run the phpBB platform if the forums are used for reference only.

Investigate how to archive the forum contents as a static site."
In addition, if we keep the MySQL database around, we can add it to a sphinx index to make the archives searchable.
I haven't tried this yet, but would something like this work?

http://code.google.com/p/phpbb-static/

Seems like we only have a few hundred posts in the forums. The best option would probably be to reduce that to a pile of static pages with no running code to exploit.
good find. I vote for that if search isn't a priority - sphinx is tied to MySQL; though elastic could index static files too.
Target Milestone: 1.0 → 1.1
So here are the steps:

http://etherpad.mozilla.org:9000/WzfMsXW74S

We need to do this on stage9. Then we can play with the static .css styles as much as we want. I suggest we push the static forums WITHOUT updating the link from /discussion yet - so we can test the static forums by manually entering the URL's.

In a subsequent push we can change the forum link and turn off phpbb.
Bumping to 1.2 for triage, since we're at code freeze for 1.1 and these bugs are most likely not going to make it.
Target Milestone: 1.1 → 1.2
All-hands de-reailed 1.2. Bumping to 1.3.
Target Milestone: 1.2 → 1.3
Use the admin panel to add a waffle switch, 'static_forums' to True. Then go to https://developer-stage9.mozilla.org/en-US/discussions and follow the archive link - it should go to the new page with static pages in iframe. Browse the static pages and make sure everything is functional.

Craig/Jay,

We don't have to flip this switch unless/until we're happy with the design on the pages, so we might have a follow-up bug that addresses the CSS and design before we flip the switch on production.
Status: NEW → RESOLVED
Closed: 13 years ago
Keywords: qawanted
Resolution: --- → FIXED
Commits pushed to https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/087e4dc883c550e226dcbeeadd4b8fa6d55119a8
bug 676335 control forum archive link with a waffle switch

https://github.com/mozilla/kuma/commit/06839a67e8ce355761e8a2cc66b054876473c08a
Merge pull request #14 from groovecoder/bug676335-static-forum-archive

Bug676335 static forum archive

https://github.com/mozilla/kuma/commit/946f92a269f8e64704bac723c9749535ba23c099
bug 676335 typo in iframe src for forum archive

https://github.com/mozilla/kuma/commit/caab615570642d1e029677861be1980b85810a0b
Merge pull request #22 from groovecoder/bug676335-forum-archive

bug 676335 typo in iframe src for forum archive
Version: MDN → unspecified
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.