New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unlimited comment/post editing #2826
Conversation
Witnesses don't seem to be ready yet. Closing for now, set a reminder to check back in 2 weeks. |
Last time I tested this branch, I received assert errors regarding changing permlink. Not sure if this was due to condenser logic or steemd pre-softfork-removal. |
5a1000d
to
1dcbc1b
Compare
Rebased to resolve conflicts, but appears as though adoption of 0.19.10 is still a few weeks away. Checking back in a few weeks. |
To all involved, We are delighted and excited to see this change on the verge of being released to the world. I must confess that we have been waiting very impatiently, having been lobbying for this change literally for years now... And so, I'm just popping in here today to say both "Hooray!" and to, if possible, gently appeal for adoption and release of this feature as soon as practicably possible. Thanks so much in advance! |
@creatorguy it is mainly a matter of enough witnesses applying the 19.10 changes. Currently only 5 of the top 20 have applied them. You can see the list here: https://steemd.com/witnesses. Once more witnesses have applied the changes, then this change will be taken off hold. |
Hello, @TimCliff, I really appreciate your reply and further explanation of what's holding this update back. Now I can use whatever influence I may have, especially with the witnesses that I support with my vote, to encourage adoption of these changes. Thanks! :D P.S. I would appreciate it if you could tell me exactly how many witnesses must apply 19.10 before the change is implemented? All of the top 20? Some percentage of all witnesses? Thanks in advance. P.P.S. Simply as a gesture of my appreciation for your kind feedback already given, I discovered that I had a poorly used witness vote, and am now supporting your witness. ;) |
Hey @roadscape, Also, has this been successfully implemented? From looking at the Steem Witness list (https://steemd.com/witnesses), it seems that some are already running 19.10. How many more need to be running this for it to be activated, and any idea when that will happen? Thanks! |
@genelamarellis This feature already works, it just hasn't been enabled on Steemit.com. With the number of upgraded witnesses/nodes, updating posts after 7 days works with some consistency. (the edits usually make it through the network, sometimes you need to try a few times). This would allow editing all posts ever made. |
Oh I see. Got it. Thank you! |
Is this still happening? |
@ajayyy Yep. Now that all witnesses are running AppBase, it should be ready to merge. |
This was tested recently and resulted in the same assertion error (cannot change permlink), need to find the cause. |
Now, |
Oh... formId is probably added in the advanced post settings change. Did
not confirm yet.
…On Tue, Oct 2, 2018, 16:36 roadscape. ***@***.***> wrote:
Now, ReferenceError: formId is not defined. Perhaps a new reference to it
was added since this branch removed it 4 months ago.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2826 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhVZ9tpm1MPXhn-NbYst1a0cKS4r2JDmks5ug85BgaJpZM4USPcJ>
.
|
@@ -324,7 +324,6 @@ class ReplyEditor extends React.Component { | |||
reply, | |||
username, | |||
isStory, | |||
formId, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the only line you need to revert to get it to work.
#3060 available as well. @roadscape |
Also question, should categories be editable? Seems like it's allowed, but just wanted to double-check. |
@eonwarped unless something changed in HF20, the category is set when the post is created, and is unalterable. |
@relativityboy Ah I meant other tags. The first one I didn't check but I changed the others. |
@@ -300,11 +300,11 @@ class CommentImpl extends React.Component { | |||
// hide images if author is in blacklist | |||
const hideImages = ImageUserBlockList.includes(author); | |||
|
|||
const showDeleteOption = username === author && allowDelete; | |||
const _isPaidout = comment.cashout_time === '1969-12-31T23:59:59'; // TODO: audit after HF19. #1259 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment here can probably be removed. We're post HF20 and the time hasn't been changed.
Were it within scope, that string '1969-12-31T23:59:59'
should be hoisted as a const and kept somewhere with good documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Dismissing my own review. I'd thought this code had been tested in dev before the PR was created.
Ok. After testing in other environments, looks like the issue may have been the dev env. We should be gtg. |
Minor cleanup of related fields and removal of comment-editing-after-payout restriction. Untested! Do not merge until majority witness upgrade to a compatible version is confirmed!