ed33811
Forum Replies Created
-
Yes you have all that correct. Old posts are published posts that have not yet hit expiration. When opened with “quick edit” the “replace” category is the original post category, not the one selected to set upon expiration. Thank you
good morning. thanks for working on this.
the beta fixed soem of the problem, but not all….
1. the post category replaces, by adding a new one.
2. the original category is “sticky” in the interface – that is, if you indicate “replace” as the action, select another category, the previous one stays selected (easiest to see in Quick Edit. even unselect, save, go back, still selected.
3. when default plugin action is “replace” and category selected, then new post created, the interface looks correct, but the post is saved with no category to replace
4. tried to fake it out by updating post to another action (“draft” for example) then re-update with “replace” – same situation – new category added, but old is sticky.
5. BTW, “stickiness” isn’t simply display in interface, let the expirator run, and sure enough, post gets new category AND old.
6. also, all old posts created with prev expirator show with original category as replacement category when edited. for example, old posts had been setup to replace category as “expired”. if their original category was “fishlips”, when updating, expirator shows “replace” category as “fishlips” rather than originally configured “expired”hope this helps debug a bit. thanks for working this.
ed