https://bugzilla.wikimedia.org/show_bug.cgi?id=43049
--- Comment #4 from Daniel Kinzler <[email protected]> --- (In reply to comment #3) > This is still a valid use case. Just because it can't be fixed right now > doesn't mean it should not be fixed or stay as a longer-term reminder. Yea, I would just have suggested to have a separate entry on bugzilla for that. This is not a bug to fix but a feature to design. > When moving a page we should look if content models are compatible and/or > convertible. If compatible, it should move straight (with > wgContentHandlerUseDB=false, no other changes needed. with > wgContentHandlerUseDB=true we'd have to update the per-page/revision record). It's unclear what "compatible" means, or in what sense JS and CSS are "compatible". They are already considered convertible. But just re-interpreting content without giving the handler the chance to adjust it seems wrong to me. > If not compatible but convertible we can probably show a warning (like we > already do for possibly unintended actions, such as moving to an existing > page > name), and if accepted move it and convert it in a new revision. Showing warnings from the move operation is not currently possible. Adding it isn't hard, but would probably break B/C for extensions calling Title::moveTo. > (In reply to comment #2) > > with $wgContentHandlerUseDB=true, conversion could be done > > as an edit, creating a new revision > > Why would that only be possible with that variable enabled? Afaik that should > work fine but with and without per-page determination. Because with $wgContentHandlerUseDB=false, the older revisions would also get the new content model, without actually being converted. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
