Closed conkonig closed 2 months ago
Hey @conkonig,
Please do not use that script, there's a number of issues with it, and the Add Metadata tool is built to properly verify the metadata it creates.
As you're a licensed customer, please contact support through the plugin's Support tab for help with getting the Add Metadata tool working.
Although, given that your site is reporting that all media is offloaded, I suspect you do not need to use the Add Metadata tool. It may be that you've found a bug whereby the tool gets confused as there's nothing to be processed, so please explain to support why you're trying to run the tool when everything is already offloaded so that they can help you better.
Add Metadata tool hangs on 0% with endless repeating API response showing no progress. I have manually added the metadata to the table wp_as3cf_items with a short script manually instead. Still the tool shows the same issue hanging on 0%
The response pictured keeps repeating and stays on 0% progress:
The admin area of the plugin is locked out while the loop runs endlessly see below:
Steps to reproduce: 1) Install plugin and activate pro license 2) Connect to existing bucket with existing media on digitalocean spaces 3) Enable the add metadata from existing media tool by adding
define( 'AS3CF_SHOW_ADD_METADATA_TOOL', true );
to wp-config.php 4) Try to run the add metadata tool 5) Observe hanging and locked out of plugin admin areaFurther steps: 6) Cure lockout by clearing rows from wp_options 7) Run WP CLI command in plugin below to manually rectify bucket URL's for existing bucket media
Hanging and lockout can be cured by manually deleting the rows from wp_options relating to the add_metadata_tool. Just search for rows containing "%as3cf%"
It would be nice to have this working for those who paid for a pro license and have to work with it across multiple websites with multiple staging / production environments. Otherwise have to rely on hacky script workaround from chatgpt below:
Finally if no one has time to debug this can someone confirm if workaround script above will be okay with the plugin and not cause further issues? Thank you