Make WordPress Core

Opened 4 years ago

Closed 2 months ago

#18586 closed enhancement (wontfix)

PHP errors in plugin-editor.php do not &scrollto

Reported by: Doggie52 Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.2.1
Component: Plugins Keywords: ux-feedback needs-patch
Focuses: administration Cc:


When invoking a parse error in the plugin editor, one is not scrolled back using the scrollto-parameter. Although trying to parse the error and find the line it is caused at could be overkill, one should at least be scrolled back to the line one last was working on -- this is the most likely place at which the error was caused.

Change History (6)

#1 @solarissmoke
4 years ago

  • Keywords close 2nd-opinion added

Few thoughts:

  • This will only happen if you're editing an active plugin (which some might say is a bad idea in the first place).
  • We would have to track the last line edited using JS, and in any case there is every chance that someone will have edited several lines, in which case scrolling back to the last edited line isn't much help.
  • The error dump already tells you which line the error occured in - I think this should be sufficient for most developers to work out where to look.

Suggest wontfix?

#2 @Doggie52
4 years ago

  • Keywords close removed

To answer your opinions:

  • Rather irrelevant imho - if you can edit an active plugin then that's the end of the story. If some might say it's a bad idea (which I personally agree it is), then we should let the user know of this OR scrap the option altogether.
  • The tracking is already done, and is not of the last edited line but rather the last position of the cursor. It's more of a help to scroll back to the last position of the cursor than to bring you to the start of the document for the reasons I outlined in the ticket.
  • The code editor shows no line numbers - therefore telling the developer what line the error occurs at will not help.
Last edited 4 years ago by Doggie52 (previous) (diff)

#3 @SergeyBiryukov
3 years ago

  • Component changed from Editor to Plugins

#4 @chriscct7
7 months ago

  • Focuses administration added
  • Keywords ux-feedback dev-feedback added; 2nd-opinion removed
  • Severity changed from minor to normal

#5 @chriscct7
7 months ago

  • Keywords needs-patch added

#6 @DrewAPicture
2 months ago

  • Keywords dev-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

No activity or interest in 4 years. Also no patch. Closing as wontfix.

Note: See TracTickets for help on using tickets.