This branch removes seven templates, and changes 6 to match 3.0.
These files are removed. The majority of the diff consists of these. bigjools identified sourcepackagerelease-body-summary.pt as one that could be removed. I identified the other six by looking through .py files and .zcml files to try to find any usage. I did not find any usage, and salgado confirmed that I could remove them.
To test, log in as an admin (<email address hidden>:test) and look at launchpad.dev/+notificationtest1, launchpad.dev/+notificationtest2, launchpad.dev/+notificationtest3, and launchpad.dev/+notificationtest4. I'm not sure why the last three redirect and did not investigate, but the behavior before and after my change seems the same.
The macros these use (addform and editform, respectively) do not actually include the <html> tag of the launchpad-addform.pt and launchpad-editform.pt templates, so the change I made to these templates is really only for statistics: changing it to 3.0 does not affect anything.
Finally, these three templates are all for bugs: hwdb functionality.
I didn't know how to view these, and at least one of them appears to be for machine usage, and deryck didn't know how to view them either, so rather than digging into the code to figure out what was going on so I could see the pages, I opted to make the mechanical changes.
This branch removes seven templates, and changes 6 to match 3.0.
These files are removed. The majority of the diff consists of these. bigjools identified sourcepackagere lease-body- summary. pt as one that could be removed. I identified the other six by looking through .py files and .zcml files to try to find any usage. I did not find any usage, and salgado confirmed that I could remove them.
lib/canonical /launchpad/ templates/ default- editform. pt /launchpad/ templates/ message- add.pt /launchpad/ templates/ sourcepackagere lease-body- summary. pt /launchpad/ templates/ template- addform. pt /launchpad/ templates/ template- editform. pt /launchpad/ templates/ template- form.pt /launchpad/ templates/ template- page.pt
lib/canonical
lib/canonical
lib/canonical
lib/canonical
lib/canonical
lib/canonical
Most of the six template modifications have an exception of one sort or another that I'll mention below. This one is fairly normal though.
lib/canonical /launchpad/ templates/ notification- test.pt
To test, log in as an admin (<email address hidden>:test) and look at launchpad. dev/+notificati ontest1, launchpad. dev/+notificati ontest2, launchpad. dev/+notificati ontest3, and launchpad. dev/+notificati ontest4. I'm not sure why the last three redirect and did not investigate, but the behavior before and after my change seems the same.
These two are only used for their macros.
lib/canonical /launchpad/ templates/ launchpad- addform. pt /launchpad/ templates/ launchpad- editform. pt
lib/canonical
These two templates use the add form:
./lib/lp/ registry/ templates/ signedcodeofcon duct-acknowledg e.pt:11: <div metal:use- macro=" context/ @@launchpad_ addform/ addform" /> blueprints/ templates/ specification- requestfeedback .pt:23: <div metal:use- macro=" context/ @@launchpad_ addform/ addform" >
./lib/lp/
These two use the edit form:
./lib/lp/ registry/ templates/ signedcodeofcon duct-activate. pt:11: <div metal:use- macro=" context/ @@launchpad_ editform/ editform" /> registry/ templates/ signedcodeofcon duct-deactivate .pt:11: <div metal:use- macro=" context/ @@launchpad_ editform/ editform" />
./lib/lp/
The macros these use (addform and editform, respectively) do not actually include the <html> tag of the launchpad- addform. pt and launchpad- editform. pt templates, so the change I made to these templates is really only for statistics: changing it to 3.0 does not affect anything.
Finally, these three templates are all for bugs: hwdb functionality.
lib/canonical /launchpad/ templates/ hwdb-fingerprin t-submissions. pt /launchpad/ templates/ hwdb-submit- hardware- data.pt /launchpad/ templates/ person- hwdb-submission s.pt
lib/canonical
lib/canonical
I didn't know how to view these, and at least one of them appears to be for machine usage, and deryck didn't know how to view them either, so rather than digging into the code to figure out what was going on so I could see the pages, I opted to make the mechanical changes.
Thank you!
Gary