as of about 2006-03-24 @ 04:11am GMT, the following changes were made. (if you don't have css enabled in your browser, it's going to be difficult to see this entry properly.)
(as of about 2006-03-25 @ 02:14am GMT, they recompiled some layers)
list of fubared layouts and functions:
note that these are the default system versions. if you've made your own version of these functions or your own layout layer, you may still have this problem.
core:
Page::print_entry()
FriendsPage::print_entry()
EntryPage::print_comment()
EntryPage::print_body()
ReplyPage::print_body()3 column:
EntryPage::print_comment()a novel conundrum: (fix broke neat
<br /> -> <p> conversions)print_entry()
EntryPage::print_comment()
ReplyPage::print_body()a sturdy gesture:
EntryPage::print_comment()
ReplyPage::print_body()boxer:
ReplyPage::print_body()
EntryPage::print_comment()classic:
EntryPage::print_comment()
ReplyPage::print_body()clean & simple:
EntryPage::print_comment()
ReplyPage::print_body()component:
EntryPage::print_comment()
ReplyPage::print_body()cuteness attack:
EntryPage::print_comment()
ReplyPage::print_body()digital multiplex:
EntryPage::print_comment()
ReplyPage::print_body()flexible squares:
EntryPage::print_comment()
ReplyPage::print_body()generator:
EntryPage::print_comment()
ReplyPage::print_body()gradient strip:
EntryPage::print_comment()
ReplyPagee::lay_print_replyto()haven: (solution for
format_entry() on 2006-03-24 @ 08:01:09 GMT)format_replyto()
format_entry()
EntryPage::print_comment()have a fix for
format_entry() but no others, requires that people migrate their function override of format_entry() to print_entry() which is, imo, not ideal. my hack altered format_entry() in a couple ways that, imo, would have been easy to describe to people. however, if they made edits and are unable to edit their layers because they had their paid time lapse... they're hosed. unless the lj guys allow someone to be able to edit such layers or they take note of their customizations, start over, and do the best they can with the wizard.magazine:
EntryPage::print_comment()
ReplyPage::print_body()nebula:
EntryPage::print_comment()
ReplyPage::print_body()notepad:
EntryPage::print_comment()
ReplyPage::print_body()opal:
EntryPage::print_comment()punquin elegant:
EntryPage::print_comment()
ReplyPage::print_body()smooth sailing:
EntryLite::lay_print()
Entry::lay_print()
EntryPage::print_comment()tabular indent: (updated in cvs on 2006-03-24 @ 08:09:16 GMT)
print_entry()
EntryPage::print_comment()
ReplyPage::print_body()tranquility ii:
EntryPage::print_comment()
ReplyPage::print_body()unearthed: (updated in cvs on 2006-03-24 @ 08:03:22 GMT)
Page::print_entry()
EntryPage::print_comment()
ReplyPage::print_body()variable flow:
Page::lay_print_entry_text()
EntryPage::print_comment()s1 shortcomings:
EntryPage::print_comment()
s1_print_entry()to fix the problem, use
EntryLite::print_text() instead of printing EntryLite.text.example, change the red to the green:
"""<div class="entrytext">\n$e.text\n</div>\n""";"""<div class="entrytext">\n"""; $e->print_text(); """\n</div>\n""";and a note to the devs. please, please, please test your stuff. put it on the test server, post to
lj_test and have the zillions of willing pairs of eyes out here on the internet help you squash these bugs before it goes live on the production server. you will have a lot less confused and pissed off users.just an idea.
← Ctrl ← Alt
Ctrl → Alt →
← Ctrl ← Alt
Ctrl → Alt →