WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#42638 closed defect (bug) (duplicate)

Edits can not be save both for page and style sheet

Reported by: rehankhanasc Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.9
Component: Editor Keywords:
Focuses: Cc:

Description

after v4.9 update, I am unable to save my pages, styles once I edit them. First I thought it's a browser issue but it is happening for all browser now.

For instance, I was updating my styles from appearance>Editor which was working fine a week ago but now when I edit some classes and hit save it tells me
"Sorry, that file cannot be edited"

Change History (6)

#1 follow-up: @birgire
3 years ago

@rehankhanasc Thanks for the report.

Is your WordPress 4.9 running on Windows? See #42609.

#2 in reply to: ↑ 1 @rehankhanasc
3 years ago

Yeah, it is, luckily we update it on our testing website and for now, we are restoring to an older version using one of our copy from backup. How long you think this issue will be addressed?

Replying to birgire:

@rehankhanasc Thanks for the report.

Is your WordPress 4.9 running on Windows? See #42609.

#3 follow-up: @birgire
3 years ago

  • Resolution set to duplicate
  • Status changed from new to closed

I will mark this ticket as a duplicate then.

It has been patched in #42609 and it has been marked for the 4.9.1 milestone.

There's no date/timeline yet (afaik) for the shipment of 4.9.1, but hopefully it will be soon.

#4 in reply to: ↑ 3 @rehankhanasc
3 years ago

Sure, I believe reverting back to an older version is the only best solution for now, right? Also, how can we compare the next update, like whether we should have it or not, can you suggest the best way to compare updates and avoid such bottlenecks.

Replying to birgire:

I will mark this ticket as a duplicate then.

It has been patched in #42609 and it has been marked for the 4.9.1 milestone.

There's no date/timeline yet (afaik) for the shipment of 4.9.1, but hopefully it will be soon.

#5 @birgire
3 years ago

Also, how can we compare the next update, like whether we should have it or not, can you suggest the best way to compare updates and avoid such bottlenecks.

Having a staging install were one can test before upgrading the live site.

Also check the status of the ticket in #42609, it should get the fixed status and have a corresponding changeset, when it's ready for shipment.

One could also check/diff the source of the function in question.

#6 @Clorith
3 years ago

  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.