Forum Replies Created
-
AuthorPosts
-
January 10, 2024 at 8:22 pm in reply to: Bulk updating 5000 posts #9582
Sent
-
January 10, 2024 at 6:33 pm in reply to: Bulk updating 5000 posts #9579
Hi Szabi,
I tested the Existing Content Editor > Manually Run Post Editing on 3 Post IDs for faster results. I didn’t want to run it on 5000 at once for the first test.
What happened after that circling gif stopped circling is a yellow checkered sign appeared there (at mouseover it returned “status”).
On the bottom, there were no updates seen, but I was likely too late to notice them and they likely disappeared before I got to the bottom of the page to check.
I attached a screenshot.
Because of this, I have no idea what stage the update of the posts is in.
Also, posts haven’t been changed at all.
Also, my OpenAI Usage shows $0 spent, meaning the API wasn’t used.
I have the correct API entered because I was able to import an OpenAI assistant that I created at OpenAI.
What am I missing?
If there’s an issue where the process is stuck and the yellow checkered sign signals a stalled process, it would be nice if the error/problem is returned on the screen so that we know what to fix.
Attachments:
You must be logged in to view attached files. -
January 8, 2024 at 9:05 pm in reply to: Bulk updating 5000 posts #9552
Hi Szabi,
did you have the chance to add some sort of process stage log/indicator for
Existing Content Editor > Manually Run Post Editing
in your last update?
I got back to active work this week so I haven’t tested it yet but would like to know if it has been added and is it ready for testing?
-
December 20, 2023 at 8:04 pm in reply to: Bulk updating 5000 posts #9442
Omniblocks look like a major leap forward in upgrading AI content creation. Exciting times.
Yeah, I hope you do find the time needed to slip some sort of status/progress bar or stage logger for bulk content manual update into this update as this is for now the primary reason I bought the plugin for.
-
December 18, 2023 at 9:39 pm in reply to: Bulk updating 5000 posts #9431
May I suggest, maybe the process should log the stage in a DB, and then a cron can check on the stage change every 5 minutes to see if it’s still active (if the status changed or looks stuck)? If it seems stuck the cron can just restart the process from the last known active position so that this can run in the background. So that we don’t need to be logged in, have a browser open, restart the process, check on it, etc.
You could show a note under Existing Content Editor that a manual process is running in the background, how far it is (how many done out of how many – refreshed every few seconds) have that icon spinning, and have a button available to stop/kill the process.
When do you plan the next update?
-
AuthorPosts