Making WordPress.org

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#4851 closed enhancement (fixed)

Update internal link to Text Editor within https://wordpress.org/support/article/glossary/#ide

Reported by: nielslange's profile nielslange Owned by: nielslange's profile nielslange
Milestone: Priority: normal
Component: HelpHub (wordpress.org/documentation) Keywords:
Cc:

Description

Steps to reproduce:

Expected behaviour:

Current behaviour:

Change History (3)

#1 follow-up: @nielslange
5 years ago

  • Keywords needs-testing added

@SergeyBiryukov I stumbled upon #4846 and fund the issue that I highlighted in this ticket. I fixed it right away. Nevertheless, I created this ticket for documentation purposes. Is this the correct approach or should I just have gone ahead and fixed the incorrect link right away? Do you want to give it a quick look and close this issue if the link had been fixed as expected? Or shall I close this ticket?

PS: Sorry, in case I'm asking too many questions, Sergey. 🙄

Last edited 5 years ago by SergeyBiryukov (previous) (diff)

#2 in reply to: ↑ 1 ; follow-up: @SergeyBiryukov
5 years ago

  • Keywords needs-testing removed
  • Resolution set to fixed
  • Status changed from assigned to closed

Replying to nielslange:

I stumbled upon #4846 and fund the issue that I highlighted in this ticket. I fixed it right away. Nevertheless, I created this ticket for documentation purposes. Is this the correct approach or should I just have gone ahead and fixed the incorrect link right away? Do you want to give it a quick look and close this issue if the link had been fixed as expected? Or shall I close this ticket?

PS: Sorry, in case I'm asking too many questions, Sergey. 🙄

No worries! :) The link looks good now, thank you for fixing it and asking about the approach.

For small issues like this, I think it's fine to just go ahead and fix it right away. For more substantial edits, it might be a good idea to drop by the #docs channel on Slack, just in case.

#3 in reply to: ↑ 2 @nielslange
5 years ago

Replying to SergeyBiryukov:

For small issues like this, I think it's fine to just go ahead and fix it right away. For more substantial edits, it might be a good idea to drop by the #docs channel on Slack, just in case.

Thanks for clarifying this!

Note: See TracTickets for help on using tickets.