API key not stored

so that is the root cause why you are not able to store the api key.

it seems like for some reason main table (wp_wpaicg) is not created in your db. sometimes this happens when the plugin is installed on multisite network.

so you need to create that table and insert data (make sure to backup you db before performing below command)

CREATE TABLEwp_wpaicg` (
ID mediumint NOT NULL,
name text COLLATE utf8mb4_unicode_520_ci NOT NULL,
temperature float NOT NULL,
max_tokens float NOT NULL,
top_p float NOT NULL,
best_of float NOT NULL,
frequency_penalty float NOT NULL,
presence_penalty float NOT NULL,
img_size text COLLATE utf8mb4_unicode_520_ci NOT NULL,
api_key text COLLATE utf8mb4_unicode_520_ci NOT NULL,
wpai_language varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL,
wpai_add_img tinyint(1) NOT NULL,
wpai_add_intro tinyint(1) NOT NULL,
wpai_add_conclusion tinyint(1) NOT NULL,
wpai_add_tagline tinyint(1) NOT NULL,
wpai_add_faq tinyint(1) NOT NULL,
wpai_add_keywords_bold tinyint(1) NOT NULL,
wpai_number_of_heading int NOT NULL,
wpai_modify_headings tinyint(1) NOT NULL,
wpai_heading_tag varchar(10) COLLATE utf8mb4_unicode_520_ci NOT NULL,
wpai_writing_style varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL,
wpai_writing_tone varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL,
wpai_target_url varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL,
wpai_target_url_cta varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL,
wpai_cta_pos varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL,
added_date datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
modified_date datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

—
— Dumping data for table wp_wpaicg
—

INSERT INTO wp_wpaicg (ID, name, temperature, max_tokens, top_p, best_of, frequency_penalty, presence_penalty, img_size, api_key, wpai_language, wpai_add_img, wpai_add_intro, wpai_add_conclusion, wpai_add_tagline, wpai_add_faq, wpai_add_keywords_bold, wpai_number_of_heading, wpai_modify_headings, wpai_heading_tag, wpai_writing_style, wpai_writing_tone, wpai_target_url, wpai_target_url_cta, wpai_cta_pos, added_date, modified_date) VALUES
(1, ‘wpaicg_settings’, 1, 1500, 0.01, 1, 0.01, 0.01, ‘1024×1024’, ‘sk…’, ‘en’, 1, 0, 0, 0, 0, 0, 3, 0, ‘h2’, ‘infor’, ‘formal’, ”, ”, ‘beg’, ‘2024-02-29 15:44:04’, ‘2024-02-29 15:44:04’);`

pls forget about options table.

the issue is wp_wpaicg table..

i didnt understand this part “Changing settings changed values in the options table – not in the new one.”

what do you mean?

if you already created that table then you should be able to store the api key now.

yes pls dont explain to me how it works, i am the one who wrote it 🙂

the point is: master api key is stored in wp_wpaicg table. if that table dont exist then nothing is going to work.

i am not blaming you. i am trying to help. but pls forget about options table. it has nothing to do with the issue.

lets try to troubleshoot.

can you open “developer tools” in google chrome and try to update the api key again and see if there is any error in the console log or network tab?