:art: A WordPress plugin for displaying artwork. Artworker adds custom post types, taxonomies, and custom Gutenberg blocks that enable you to turn your site into a beautiful art gallery.
By default a single view of an artwork post type just uses the default single template file from the theme. However, because the art block utilizes the featured image metadata, some themes may display the artwork twice. One as the featured image, and the other within the content as the artwork block.
New images uploaded by dragging and dropping onto the artwork block are not setting within the block attributes. This is caused by the media object not having the extra attributes yet. This is likely because the image is still in the process of being uploaded, and WordPress hasn't yet made all the alternate sizes / metadata of the image.
The artwork block image isn't displaying on the front end in a single view of the artwork post type. This seems to be because the .artwork-block-image class has declared display none. This was to by default hide the artwork block so that it wouldn't take up space when a user has javascript disabled.
The art gallery is supposed to automatically load the next page once the user clicks on the last few art gallery items which will add them to the PhotoSwipe gallery items instead of looping back around to the beginning of the gallery. However, the next page of gallery items is being called twice.
Add a recent artwork gallery block that dynamically updates with the latest x artwork posts. The user should be able to set how many art pieces to display, as well as any options that the jquery justifiedGallery plugin offers. Such as modifying the behavior of the last row, setting the margins, and border of the gallery etc.
PhotoSwipe is not opening the artwork block image. This seems to be due to the recent change in where data is stored and how it is retrieved. We pass data to PhotoSwipe through data attributes within the HTML. Originally I simply passed a JSON string to a data attribute and parsed it in the JS. However, I think it's better to have separate data attributes, and update how the JS parses these attributes accordingly.