Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • mgurtzweiler

    (@mgurtzweiler)

    Same issue happening here. Rolled back to 20.2.1 on WordPress 6.0.3?to get the editor working as expected again.

    Thread Starter mgurtzweiler

    (@mgurtzweiler)

    Thanks I found that yesterday!

    I’m using that plus the ajax_query_attachments_args hook to filter out images created by our Web Stories creators from the web content authors and editors.

    Thread Starter mgurtzweiler

    (@mgurtzweiler)

    Thanks, no you get the gist of my question. We create web stories from exiting posts, so we end up with “cropped-<old name>” in the library.

    Seems like not a big deal until you’re dealing with 1000s of images a month. It doesn’t help that WordPress media search is pretty poor, not being able to filter by size, aspect ratio, etc.

    Are there any hooks available when an image is resized or cropped by the plugin? We track image attribution information in custom fields so we can keep the copyright trolls away and being able to set that information when an existing image is cropped would also be a big help.

    I’ve experienced this issue in previous versions. It seems better in the 1.23.x series.

    I can re-create this by having my window size large enough that it is possible to display more cards than the default number that is loaded. The loading animation will display but more cards will never render.

    I just resize my window to a smaller size so I have to scroll to trigger a load ??

    What matters is that the story has a poster set and is valid AMP.

    Ahh, that is good news.

    So if the <amp-story> tag has a valid poster-portrait-src then we are good to go? The tests I did this morning had the correct image set even know the thumbnail_id was not. I think we can live with this for this existing batch.

    Thank you!

    Thanks for this update.

    I was able to take an existing story that was created after the 1.23 release, “update” the poster image using the media library, and publish. The Poster “Thumbnail” (or featured image) was correctly set, and the archive page renders as expected.

    One issue I found. We have 100s of stories queued up to publish that were created since the 1.23 release that I’ve been sitting on for obvious reasons. They display the correct poster image in the Dashboard, display the correct poster image in the publish preview, however when published the Thumbnail/Featured image is blank… Which means if I were to publish them without going through each and re-selecting the poster image the archive page will appear broken and I’m pretty sure Google discover will ignore these due to a missing poster image.

    I was hoping I didn’t have to go back and fix 100s of stories in order to get them published successfully ??

    1.23.1 does not seem to fix the issue.

    You can update the poster image while in the editor and the new image is shown in the UI. But after you save or submit the story the previous image is still displayed in the dashboard. Opening the story again also displays the old image.

    If it helps we use the “Upload a file” choice to select images from our media library. Odd naming choice for that option IMO.

    • This reply was modified 2 years, 8 months ago by mgurtzweiler. Reason: additional detail
Viewing 7 replies - 1 through 7 (of 7 total)