Now with a blogging engine.
Oct 15 2019
I did some trial and error last week with Twitter via https://cards-dev.twitter.com/validator. That was for my personal blog, but some of it might apply here as well.
Sep 19 2019
og:title should probably be the post title.
Jul 31 2019
Jul 9 2017
Jul 6 2017
That use case doesn't strike me as compelling enough to justify a separate field or a behavioral change so I don't plan to adjust our behavior here.
Jul 5 2017
You must be able to view a post's blog to view the post, so the rule is effectively "view and edit".
Don't most places consider "Can Edit" to be weaker than "Can View"?
Mar 20 2017
@epriestley, I tested out the scenario with the change applied.
Mar 14 2017
Ah! That fixed it, thanks @epriestley. I'll let you know once I test out that configuration.
Remarkup is cached, so you'll need to run bin/cache purge --purge-remarkup (or make an edit, or create a new post) to purge the cache.
@epriestley, I wouldn't mind testing that scenario out this weekend (I'll have to change a couple of domain name settings to create the scenario, but that's easily undone).
Mar 11 2017
Happy to accept a patch for this (deleting that one line of code) if someone wants to claim that they tested the scenario above and it worked correctly.
Mar 9 2017
That is, the problem would be:
I guess we actually have to test this use case:
I can fix if it's one line, I just assumed it was something super hard with external urls or something.
I blame the fun police.
Macros are disabled in Phame posts, via markup engine. This originated in D2202.
Jan 20 2017
I did for now, will see what FontAwesome 5 brings, but the was never something I really liked for Phame anyways.
Jan 19 2017
Jan 17 2017
Jan 16 2017
Jan 15 2017
no no those are for the Meterology application
Theres like 20 thermometers for a health application.
also conflicts with Phabricator Health Records Application
Nobody loves making tasks and projects… what is this, a tool for PMs?
Or use heart for favorites?
Sep 26 2016
Thanks, Chad. I've just used the Administrators group and adjusted the EditEngine permissions, which is sufficient for us; anyone authoritative enough to create blogs is authoritative and technically proficient enough to have admin privs, too.
Yeah, it makes sense to not auto-subscribe and I'm afraid I don't have better plans ready for cases where you don't want everyone creating blogs. You could at least make a group like "blog creators" and delegate.
Sep 23 2016
My concern here is the specific request only solves a side-effect of the root problem, and not the root problem itself.
My concern here is the specific request only solves a side-effect of the root problem, and not the root problem itself. We do not expect admins to have to create blogs for people. I would like to understand better what we can do in that case.
Aside from that, I don't think it's too much of a stretch to say that as a general principle, permanent/irrevocable subscription to an object is tantamount to spam.
Specifically, a root problem would be how you got into this state to request this feature to begin with, not that you want the feature.
In my administrator/management role, I create a blog for someone else to write posts for
Sorry. I thought the root problem was obvious. I guess not.