Closed
Bug 653203
Opened 14 years ago
Closed 14 years ago
[stage] Facebook message has our staging url
Categories
(Websites Graveyard :: markup.mozilla.org, defect, P1)
Websites Graveyard
markup.mozilla.org
Tracking
(Not tracked)
VERIFIED
FIXED
1.0
People
(Reporter: mbrandt, Assigned: brez)
References
()
Details
(Whiteboard: [stage])
Attachments
(4 files)
This may be intentional but I wanted to check (nudging is always better than assuming), the url in the Facebook message currently points to our staging environment.
"https://markup.allizom.org/en/#/linear/YtCx
https://markup.allizom.org/en/#/linear/YtCx"
Additionally did we want a more verbose message about Markup to be included in the Facebook post? Currently only the above urls are being posted to a users wall.
Please see screenshot.
Updated•14 years ago
|
Assignee: nobody → jbresnik
Target Milestone: --- → 1.0
Reporter | ||
Comment 1•14 years ago
|
||
And because more is merrier ... here's another screen grab :)
Comment 3•14 years ago
|
||
We should be adding a message. I'll upload one tomorrow morning.
Reporter | ||
Comment 4•14 years ago
|
||
Thanks Laura. Also (In reply to comment #3)
> We should be adding a message. I'll upload one tomorrow morning.
Thanks Laura. Do we also need to update the urls to point to prod?
Comment 5•14 years ago
|
||
Yes, they should point to production--as should twitter--but this is assuming all of this wasn't intentional. Tbg--can you confirm intention?
Reporter | ||
Comment 6•14 years ago
|
||
(In reply to comment #5)
> as should twitter--but this is assuming all of this wasn't intentional.
> Tbg--can you confirm intention?
Just for reference, here's the twitter bug 652891.
Comment 7•14 years ago
|
||
Message should be:
"The Web belongs to all of us. Make your mark and show your support for the
world's largest public resource."
Comment 8•14 years ago
|
||
In response to Laura's comment (#5), because we were testing, they were set to staging. However, now that we are updating, the URLs should point to production.
Comment 9•14 years ago
|
||
Ozten, please verify that the code is setup to use the production url once pushed? If this is not the case, please assign back to TBG. Thanks!
Assignee: jbresnik → ozten.bugs
Status: NEW → ASSIGNED
Comment 10•14 years ago
|
||
Ozten--just wanted to check in here
Comment 11•14 years ago
|
||
I have not started looking into this. I hope to look into it today.
Comment 12•14 years ago
|
||
It looks like we're using jquery-socialShare which uses the current url.
On my dev instance, I see it sharing my dev url.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 13•14 years ago
|
||
Thanks ozten! I'll wait to close this once I'm able to verify on prod.
Reporter | ||
Comment 14•14 years ago
|
||
Testing on dev, the url in the facebook message updates correctly however I'm not seeing the updated message in comment 7.
"The Web belongs to all of us. Make your mark and show your support for the
world's largest public resource."
Reporter | ||
Updated•14 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Updated•14 years ago
|
Assignee: ozten.bugs → jbresnik
Assignee | ||
Comment 15•14 years ago
|
||
As long as you are testing on staging, you will see staging URLs, after all that is what you are sharing.
Assignee | ||
Comment 16•14 years ago
|
||
Re. the text we're setting the 't' variable but facebook isn't using the data - the likely cause is because it is behind the basic auth for staging, i.e. FB can't get back to the URL to scrape meta tags (which we have in place) - best option is to just put into production (or turn off basic auth which isn't recommended) - closing this because there's nothing more to do and will magically fix itself once in production
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Comment 17•14 years ago
|
||
Updated the copy here:
https://github.com/mozilla/markup/commit/b884aa6abe9ecdcce985669473b160035e718bdc
Verified FIXED on production:
https://markup.mozilla.org/
Status: RESOLVED → VERIFIED
Updated•3 years ago
|
Product: Websites → Websites Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•