When you add a custom block, with faulty PHP or HTML inside it, there is no way you can edit that block afterwards. The HTML of teh page itself is completely borken then.

Comments

Steve Dondley’s picture

Steve Dondley commented
Priority: Critical » Normal

This bug has been around long before 4.7.0. Not sure it really qualifies as critical. Although a hassle, users can disable the block by manually setting block status to 0 in database. Downgrading to normal.

chx’s picture

chx commented
Status: Active » Closed (won't fix)

Use a capable browser, like Opera where hitting back solves this problem.

Bèr Kessels’s picture

Bèr Kessels commented
Status: Closed (won't fix) » Active

This a bug. The priority is not that high. But it *is* a bug. maybe not for 4.7. But it *is* a bug.

chx’s picture

chx commented
Status: Active » Closed (won't fix)

Fixing this would mean adding special case to block_list so that on admin/block/* the custom blocks are not displayed, this is performance wise not good and I like to see immediately what I've done. If the block f!cks up the page, well, I use Opera. If you don't, you can edit the database and boxes table.

Yes it's a bug but I insist on not fixing it.

Bèr Kessels’s picture

Bèr Kessels commented

There are other ways: like checking the results of EVAL *before* save.

chx’s picture

chx commented
Status: Closed (won't fix) » Active

Well, that could help somewhat the PHP blocks, true.

Egon Bianchet’s picture

Egon Bianchet commented
Version: 4.7.0-beta1 » 4.7.0
magico’s picture

magico commented
Version: 4.7.0 » x.y.z
Status: Active » Fixed

The only problem remaining is when showing the block: it will give an error. But drupal keeps running and functional allowing the block configuration.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)