facebook: the Meta app is LIVE (R-915 closed); website lockup entry
gates / gates (push) Successful in 5m47s
gates / gates (push) Successful in 5m47s
R-915 closed and moved to CLOSED-ITEMS in the same commit. What it had waited
on was R-813's Terms of Service URL, which did not exist until the closed-test
legal set went live this morning.
Filled in the app's Basic settings and verified they persisted across a full
reload (not from the save toast):
Privacy policy URL https://felhom.eu/adatkezeles
Terms of Service URL https://felhom.eu/feltetelek
Data deletion instructions URL https://felhom.eu/adatkezeles
Category "Vallalkozasok es oldalak"
THE APP ICON WAS NOT REQUIRED. The original row listed it among the Live
blockers; Meta answered "All required app settings are complete" with it still
empty. Recorded so the next session does not go hunting for one -- and it
could not be uploaded from here anyway: the icon control creates its file
input only on click, and clicking opens a native dialog the browser tooling
cannot drive.
Published, and READ BACK FROM A FULL PAGE RELOAD rather than the success
toast, because Meta's toasts have lied on this Page before: the badge reads
Published, the string Unpublished is gone, and the page now offers Unpublish.
Nothing was granted. No permission added, no use case changed; the scopes stay
"Ready for testing", which is all a system user needs for the business's own
Page. Going Live changes WHO CAN SEE what the app posts, not what it may do.
R-917 and R-920 are unblocked by this -- both were waiting on posting starting.
R-813's next action (a) is spent.
Also carries the marketing CHANGELOG entry for the header/footer change pushed
in 625d38645c.
CI for the three commits before this one: #875 SUCCESS (after a re-run -- the
first attempt was R-887's lost-job flake, "Set up job" 11m48s then every step
0s), #876 SUCCESS, #877 SUCCESS.
This commit is contained in:
@@ -47,6 +47,25 @@
|
||||
- **Still to prove:** the lost off-site copy alarm (Tester 1's next clean-up
|
||||
window, about 12 October), and the failed-restore hold (needs a scratch off-site store).
|
||||
|
||||
## Facebook is live (2026-10-09): the Page can now post in public
|
||||
|
||||
- **The Meta app is switched on.** Until today anything the Page posted was visible only to people with a role
|
||||
on the app — effectively nobody. It is now **Published**, so posts are public.
|
||||
- What had been holding it up for a day was the terms page, which did not exist until this morning. I put both
|
||||
addresses into the app's settings, chose its category, and switched it over. **The app icon turned out not to
|
||||
be required** — Meta accepted it without one, so that item is off the list.
|
||||
- **Nothing new was granted.** The app can do exactly what it could do yesterday; going live only changes who
|
||||
can *see* what it posts.
|
||||
- **You can start posting whenever you like.** The two texts we parked — the long description and the four
|
||||
Messenger answers — were waiting on exactly this, and are ready to go out as posts.
|
||||
|
||||
## Website (2026-10-09): the header says the name once, and the footer links look like links
|
||||
|
||||
- The header showed „felhom.eu" twice: once baked into the logo picture and once typed beside it. Now there is
|
||||
one lockup — the symbol on its own, larger, with the name next to it **in the logo's own lettering**, not a
|
||||
typeface that merely looks similar. The footer's legal links now match every other link on the site, and no
|
||||
longer turn purple after you have read them once.
|
||||
|
||||
## Done and still owed (2026-10-09): the published password is dead for Gitea — but it still opens a dozen other things
|
||||
|
||||
Following up the finding below, I measured what that password actually was. It was **your Gitea admin login**,
|
||||
|
||||
Reference in New Issue
Block a user