EntryWizard
EntryWizard was developed to cater to the needs of camera club competitions. In these competitions members may submit multiple images with titles and other data attached. Administrators use the software to design web forms, asking for information as text inputs and/or drop-down menu items as well as image files. They may set up any number of different “layouts” ( specifications of what information to ask for and what limits to enforce ), assigning an identifier to each. Here is one example of the sort of rules a layout is able to specify: Each image must have: a short title; a “Category”, which must be one of “Nature”, “Photojournalism”, “Still Life” or “Portrait”; a “Format”, which must be one of “Digital”, “Slide” or “Print” Up to 6 entries may be submitted, each with or without a digital version Any image of type “Digital” must have an uploaded digital version At most 2 of the 6 images may be in the “Nature” category. The images must be in jpeg format, with maximum dimensions of 1280 x 1024 pixels, longest dimension no less than 900 pixels, and size no greater than 1M. Each webform is given a unique alphanumeric identifier, and this identifier is used within a shortcode to insert the webform in a page or post. Any number of different webforms may be created, and one of the layouts is assigned to each one. Multiple webforms may appear on one page, although currently they have to be submitted individually. Each webform separately may be set as “open for upload” or “closed”. If it is open, the shortcode is replaced by the upload form. If it is closed, the shortcode is replaced by a message saying that the upload is closed. A closed webform may also be opened temporarily to specified members only, and an open webform may be set to close automatically at a specified time. When items have been uploaded, the administrator may either view the items online, or download them. The downloaded image files may be renamed in various ways. A spreadsheet (in comma-separated .csv format) showing the uploaded data together with some optional information about the users, may also be downloaded. The uploaded images may be attached to pre-existing pages for display in a gallery. There is a fine-grained permissions system allowing administrators to grant an individual user various levels of control over the webforms and layouts. Only logged-in users may see the webform. Users of this plugin may also be interested in using Flexishow (https://sourceforge.net/projects/flexishow/) to run a slideshow using the information in the spreadsheet to select the images displayed. EntryWizard has a companion plugin called Ewz-Rating (https://wordpress.org/plugins/ewz-rating/). It is designed for display and online judging of items uploaded via EntryWizard. Privacy This plugin does not send any data to external servers. It does store in the wordpress database whatever data is requested in the forms designed by the administrator. Viewing of such data using the plugin’s shortcodes is always restricted to logged-in users, and is usually further restricted by the administrator.
Top keywords
- webform6×1.17%
- data5×0.98%
- images5×0.98%
- uploaded5×0.98%
- closed4×0.78%
- digital4×0.78%
- image4×0.78%
- information4×0.78%
- items4×0.78%
- users4×0.78%
- administrator3×0.59%
- entrywizard3×0.59%
Image Prioritizer
This plugin optimizes the loading of images (and videos) with prioritization to improve Largest Contentful Paint (LCP), lazy loading, and more accurate image size selection. The current optimizations include: Add breakpoint-specific fetchpriority=high preload links (both as LINK[rel=preload] elements and Link response headers) for image URLs of LCP elements: An IMG element, including the srcset/sizes attributes supplied as imagesrcset/imagesizes on the LINK. The first SOURCE element with a type attribute in a PICTURE element. (Art-directed PICTURE elements using media queries are not supported.) An element with a CSS background-image inline style attribute. An element with a CSS background-image applied with a stylesheet (when the image is from an allowed origin). A VIDEO element’s poster image. Ensure fetchpriority=high is only added to an IMG when it is the LCP element across all responsive breakpoints. Add fetchpriority=low to IMG tags which appear in the initial viewport but are not visible, such as when they are subsequent carousel slides. Lazy loading: Apply lazy loading to IMG tags based on whether they appear in any breakpoint’s initial viewport. Implement lazy loading of CSS background images added via inline style attributes. Lazy-load VIDEO tags by setting the appropriate attributes based on whether they appear in the initial viewport. If a VIDEO is the LCP element, it gets preload=auto; if it is in an initial viewport, the preload=metadata default is left; if it is not in an initial viewport, it gets preload=none. Lazy-loaded videos also get initial preload, autoplay, and poster attributes restored when the VIDEO is going to enter the viewport. Responsive image sizes: Ensure sizes=auto is set on IMG tags after setting correct lazy-loading (above). ~~Compute the sizes attribute using the widths of an image collected from URL Metrics for each breakpoint (when not lazy-loaded since then handled by sizes=auto).~~ (This has been removed due to an issue; use Enhanced Responsive Images instead.) Reduce the size of the poster image of a VIDEO from full size to the size appropriate for the maximum width of the video (on desktop). This plugin requires the Optimization Detective plugin as a dependency. Please refer to that plugin for additional background on how this plugin works as well as additional developer options. 👉 Note: This plugin optimizes pages for actual visitors, and it depends on visitors to optimize pages. As such, you won’t see optimizations applied immediately after activating the plugin. Please wait for URL Metrics to be gathered for both mobile and desktop visits. And since administrator users are not normal visitors typically, optimizations are not applied for admins by default. Your site must have the REST API accessible to unauthenticated frontend visitors since this is how metrics are collected about how a page should be optimized. There are currently no settings and no user interface for this plugin since it is designed to work without any configuration.
Top keywords