Opened 14 years ago
Last modified 22 months ago
#14991 new defect (bug)
extra_rules_top should take priority over extra_permastructs
Reported by: | prettyboymp | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.1 |
Component: | Rewrite Rules | Keywords: | has-patch dev-feedback needs-unit-tests |
Focuses: | Cc: |
Description
Since extra_rules_top are specifically added instead of generated like the those from the extra_permastructs which runs through generate_rewrite_ruls(), shouldn't the extra_rules_top take priority in conflicts?
Attachments (3)
Change History (11)
#4
@
14 years ago
- Keywords needs-patch added; has-patch removed
Using array_reverse like that looks like an ugly hack to me, If i'm understanding this correctly, perhaps we can add the permastructs to a separate array, and then merge it after the loop?
Reseting to needs-patch given this will be stale now (I've changed that block)
#5
@
14 years ago
- Keywords has-patch added; needs-patch removed
Added updated patch. I went with dd32's suggestion of using a separate array for permastructs.
I switched to using the '+' operator instead of array_merge in the final rule merging. I would think this is the effect that was originally desired when this when this was created.
Makes sense.