post regenerations: replace PostRegeneration model with mod actions.

* Remove the PostRegeneration model. Instead just use a mod action
  to log when a post is regenerated.

* Change it so that IQDB is also updated when the image samples are
  regenerated. This is necessary because when the images samples are
  regenerated, the thumbnail may change, which means IQDB needs to be
  updated too. This can happen when regenerating old images with
  transparent backgrounds where the transparency was flattened to black
  instead of white in the thumbnail.

* Only display one "Regenerate image" option in the post sidebar, to
  regenerate both the images and IQDB. Regenerating IQDB only can be
  done through the API. Having two options in the sidebar is too much
  clutter, and it's too confusing for Mods who don't know the difference
  between an IQDB-only regeneration and a full image regeneration.

* Add a confirm prompt to the "Regenerate image" link.
This commit is contained in:
evazion
2021-01-04 15:59:36 -06:00
parent 913ce88024
commit df44937c57
15 changed files with 34 additions and 189 deletions

View File

@@ -2724,39 +2724,6 @@ CREATE SEQUENCE public.post_flags_id_seq
ALTER SEQUENCE public.post_flags_id_seq OWNED BY public.post_flags.id;
--
-- Name: post_regenerations; Type: TABLE; Schema: public; Owner: -
--
CREATE TABLE public.post_regenerations (
id bigint NOT NULL,
created_at timestamp(6) without time zone NOT NULL,
updated_at timestamp(6) without time zone NOT NULL,
creator_id integer NOT NULL,
post_id integer NOT NULL,
category character varying NOT NULL
);
--
-- Name: post_regenerations_id_seq; Type: SEQUENCE; Schema: public; Owner: -
--
CREATE SEQUENCE public.post_regenerations_id_seq
START WITH 1
INCREMENT BY 1
NO MINVALUE
NO MAXVALUE
CACHE 1;
--
-- Name: post_regenerations_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: -
--
ALTER SEQUENCE public.post_regenerations_id_seq OWNED BY public.post_regenerations.id;
--
-- Name: post_replacements; Type: TABLE; Schema: public; Owner: -
--
@@ -4170,13 +4137,6 @@ ALTER TABLE ONLY public.post_disapprovals ALTER COLUMN id SET DEFAULT nextval('p
ALTER TABLE ONLY public.post_flags ALTER COLUMN id SET DEFAULT nextval('public.post_flags_id_seq'::regclass);
--
-- Name: post_regenerations id; Type: DEFAULT; Schema: public; Owner: -
--
ALTER TABLE ONLY public.post_regenerations ALTER COLUMN id SET DEFAULT nextval('public.post_regenerations_id_seq'::regclass);
--
-- Name: post_replacements id; Type: DEFAULT; Schema: public; Owner: -
--
@@ -4539,14 +4499,6 @@ ALTER TABLE ONLY public.post_flags
ADD CONSTRAINT post_flags_pkey PRIMARY KEY (id);
--
-- Name: post_regenerations post_regenerations_pkey; Type: CONSTRAINT; Schema: public; Owner: -
--
ALTER TABLE ONLY public.post_regenerations
ADD CONSTRAINT post_regenerations_pkey PRIMARY KEY (id);
--
-- Name: post_replacements post_replacements_pkey; Type: CONSTRAINT; Schema: public; Owner: -
--
@@ -6800,20 +6752,6 @@ CREATE INDEX index_post_flags_on_reason_tsvector ON public.post_flags USING gin
CREATE INDEX index_post_flags_on_status ON public.post_flags USING btree (status);
--
-- Name: index_post_regenerations_on_creator_id; Type: INDEX; Schema: public; Owner: -
--
CREATE INDEX index_post_regenerations_on_creator_id ON public.post_regenerations USING btree (creator_id);
--
-- Name: index_post_regenerations_on_post_id; Type: INDEX; Schema: public; Owner: -
--
CREATE INDEX index_post_regenerations_on_post_id ON public.post_regenerations USING btree (post_id);
--
-- Name: index_post_replacements_on_creator_id; Type: INDEX; Schema: public; Owner: -
--
@@ -7582,7 +7520,6 @@ INSERT INTO "schema_migrations" (version) VALUES
('20200520060951'),
('20200803022359'),
('20200816175151'),
('20201121180345'),
('20201201211748'),
('20201213052805'),
('20201219201007'),