Freecodecamp: Read-Search-Ask links broken all over the place

Created on 30 Oct 2016 · 11Comments · Source: freeCodeCamp/freeCodeCamp

Challenge Name

any algorithm challenge, eg. Roman Numeral Converter

Issue Description

Remember to use Read-Search-Ask if you get stuck. Try to pair program. Write your own code.

_Read-Search-Ask_ points to a Wiki page, and it looks like your Wiki does not exist anymore. Thus, users are sent to your GitHub page without any help.

Source

Kwpolska

Most helpful comment

I'll work on this. edit: Looking at the code seems it should be working, forum links are there.

alanbares on 30 Oct 2016

🎉2

All 11 comments

@Kwpolska Thanks for the issue, VarCI got excited because it picked up on some keywords in your post that could indicate a code help request.

We need to change this link (which links to a wiki that isn't there anymore) to the forum with this link

Many thanks and Happy Coding! :+1:

Bouncey on 30 Oct 2016

I'll work on this. edit: Looking at the code seems it should be working, forum links are there.

alanbares on 30 Oct 2016

🎉2

@BerkeleyTrue this is weird the master branch has the links updated:
https://github.com/FreeCodeCamp/FreeCodeCamp/blob/master/seed/challenges/01-front-end-development-certification/basic-bonfires.json#L275

But the challenge in production doesn't reflect the same:
https://www.freecodecamp.com/challenges/title-case-a-sentence

Could you have a look?

raisedadead on 31 Oct 2016

I bugs that are fixed in staging are still reoccurring in production. Is it possible to have a partial release for the bugs related to challenge seeds?

Bouncey on 31 Oct 2016

Speaking about broken links, I'd also like to add that the link mentioned in the "Recovering Unresponsive Code" section in the forum, now just redirects to the FCC repo.

Not sure if this is already a known issue, and my apologies, if it is!

Manish-Giri on 2 Nov 2016

@Manish-Giri thanks for confirming

raisedadead on 2 Nov 2016

Quick note - I have temporarily turned the GitHub wiki back on until we can update these.

Depending on how long it will be before we push staging to production, it may not be worth the effort of tracking these down and updating them, since they are already fixed on staging, as @Bouncey and @raisedadead pointed out.

QuincyLarson on 4 Nov 2016

What should our next step be in this?
Can this be closed as it is fixed in staging and currently also working in production?

systimotic on 18 Nov 2016

nope we are keeping this blocked for releasing staging. keeping the issue open until then.

raisedadead on 18 Nov 2016

👍1

This should be resolved. I've completely switched off the GitHub wiki.

QuincyLarson on 2 Sep 2017

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:

[email protected]
Domain funtasticlabs.com has exceeded the max emails per hour (120/100 (120%)) allowed. Message will be reattempted later

------- This is a copy of the message, including all the headers. ------
Received: from mailin-01.elitehosts.com ([108.60.141.228]:60354 helo=offsite.elitehosts.com)
by neo.internetwebserver.net with esmtp (Exim 4.87)
(envelope-from noreply@github.com)
id 1dnx7E-0004ef-KA
for [email protected]; Fri, 01 Sep 2017 21:20:52 -0400
Received: from github-smtp2-ext1.iad.github.net ([192.30.252.192]:46189 helo=github-smtp2a-ext-cp1-prd.iad.github.net)
by offsite.elitehosts.com with esmtp (Exim 4.69)
(envelope-from noreply@github.com)
id 1dnx6x-00024L-3E
for [email protected]; Fri, 01 Sep 2017 21:20:35 -0400
Date: Fri, 01 Sep 2017 18:20:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1504315229;
bh=ujOOAEAYbeDGGHZnJsb+GUlzK9Iwh2BMXmjJ/ngHPfY=;
h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=KpUED3TeNb0XnRvrxGPbuq2jnRlO2gfWiE0MRtF/F2sGi+/qukN1w07cZRoe/DUui
AT+XwZ0R78n+gj7swBgL5+v0LBQfHg5zAwZ8e5wmyW1vi9Bn2WZb7VuQAVWSYxo8z0
FYlIQvJhlThBCexazST8Cqs7pHQ7MXqrjIF/0PMw=
From: Quincy Larson notifications@github.com
Reply-To: freeCodeCamp/freeCodeCamp reply@reply.github.com
To: freeCodeCamp/freeCodeCamp freeCodeCamp@noreply.github.com
Cc: Subscribed subscribed@noreply.github.com
Message-ID:
In-Reply-To:
References:
Subject: Re: [freeCodeCamp/freeCodeCamp] Read-Search-Ask links broken all over
the place (#11465)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa075db06ce_793e3fda6c3d7c381554d7";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: manzilo
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post: reply@reply.github.com
List-Unsubscribe: ,
https://github.com/notifications/unsubscribe/AL1KCrEqctrpJ9LxB_8il2SWAneHCFeQks5seK1dgaJpZM4KkdvR
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: [email protected]
X-MAILIN-01-MailScanner-Information: Please contact the ISP for more information
X-MAILIN-01-MailScanner-ID: 1dnx6x-00024L-3E
X-MAILIN-01-MailScanner: Found to be clean
X-MAILIN-01-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=-1.695, required 10, AWL 0.16, BAYES_00 -1.90,
HTML_IMAGE_ONLY_20 1.55, HTML_MESSAGE 0.00, KHOP_THREADED -1.50,
SPF_PASS -0.00, URIBL_BLOCKED 0.00)
X-MailScanner-From: [email protected]
X-Spam-Status: No

----==_mimepart_59aa075db06ce_793e3fda6c3d7c381554d7
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit

This should be resolved. I've completely switched off the GitHub wiki.

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/11465#issuecomment-326712838
----==_mimepart_59aa075db06ce_793e3fda6c3d7c381554d7
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit

This should be resolved. I've completely switched off the GitHub wiki.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/freeCodeCamp/freeCodeCamp","title":"freeCodeCamp/freeCodeCamp","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/freeCodeCamp/freeCodeCamp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@QuincyLarson in #11465: This should be resolved. I've completely switched off the GitHub wiki."}],"action":{"name":"View Issue","url":"https://github.com/freeCodeCamp/freeCodeCamp/issues/11465#issuecomment-326712838"}}}
----==_mimepart_59aa075db06ce_793e3fda6c3d7c381554d7--