Automattic / Automattic/bulk-user-management

Screenshots not appearing on wp.org

Open
#12 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
40
Forks
11
PR merge metrics
No merged PRs in 30d

Description

I think you need to create an /assets folder in the wp.org SVN repo for your screenshots to appear on wp.org

http://make.wordpress.org/plugins/2012/06/09/the-plugins-directory-and-readme-txt-files/

> Assets: The last optional directory doesn’t exist by default (Edit: It does now, older plugins may be missing it, but all newly added plugins will get it by default.) You can create it yourself though. Just make a directory called “assets” next to those other three directories. Assets currently only has one use, which is to store the banner image to be displayed on your plugin page. We may use it for more things in the future. For now, you can just make an image, name it banner-772x250.png or banner-772x250.jpg, and put it in there. Easy.
>
> Additional Info: Since creating this post, some new files have been added to the assets folder. You can create a banner-1544x500.png or banner-1544x500.jpg now too. This high-resolution banner will be shown to users with high-resolution displays, such as phones or tablets or certain newer laptops. Additionally, screenshots which once lived in the plugin’s own directory can now be moved from there into the assets directory. This allows the screenshots to be shown on the plugin page, but not included in the download of the plugin, reducing file size. It’s recommended to put screenshot files in /assets."

Contributor guide

No contributing guide indexed for this repository

Research direction

Check the plugin's WordPress SVN layout and the screenshot locations, then compare them with the /assets guidance quoted in the issue. Done means the screenshots are stored in the expected assets location and appear on the wp.org plugin page.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
content
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.