AmyMovie

Showtime is the load-bearing feature, not a sidebar widget

A film page on AmyMovie is incomplete without a second record behind it. The vendor describes the showtime function as a link between three things: a movie, the cinema showing it, and the date and time of the screening. On a movie detail page, a visitor picks a cinema and the exact times for that venue appear beside it. That single interaction is the centre of the theme's design.

From there the same data spreads outward. In the Movie List layout, the showtime function shows the times a film plays at a cinema on the current day. In the Movie Grid layout, the hours and minutes are printed on the poster itself, but only for films screening that day, so a grid silently becomes a picture of today's programme rather than a general catalogue. A dedicated Showtime page reverses the order: the visitor picks a movie first, then a cinema, and gets the date and time back.

Before you buy, that is the cost to weigh. The theme gives you the machinery for these queries, but the times themselves are entries you make. A single-venue site with two screens and one week of listings is manageable; a five-venue complex with rolling schedules is a data-entry project, and nothing in the description suggests the theme pulls schedules automatically.

The cinema record and what it publishes

Cinemas are their own content type in the vendor's description, and the fields are the ones a venue page actually needs. You enter a short description, a banner, a gallery that displays as a carousel, and contact details: address, phone, website and email. The cinema detail page can also carry a Google map of the location.

This is where the showtime choices come from, so the quality of the venue pages limits the usefulness of everything above. If you only fill in a name, the venue selector in the showtime widget has little to distinguish one location from another. Adding the map and gallery is what turns a dropdown entry into a page a visitor might bookmark.

The vendor does not describe opening hours or holiday schedules for a cinema, only the showtimes attached to individual movies. If you expect a venue's weekly timetable to live on the cinema page itself, that is not something the listing promises.

Movie fields, detail layouts and the streaming switch

The movie record is described as carrying release date and duration, IMDB rating, MPAA certificate and language. Galleries take multiple images and trailers can be embedded from YouTube or Vimeo; the description says the counts of images and videos appear on the movie detail page, which is a small editorial signal that a film has more than a poster. Genre, actor and director selections tie the movie to the people and category pages built around the same data.

The detail page comes in three layouts the vendor names: left sidebar, right sidebar and full width, and you can also choose the sidebar for an individual movie rather than inheriting one setting everywhere. Custom fields let you add attributes the default record does not cover, which matters if you track format, subtitles or a local rating alongside the IMDB figure.

Two switches deserve attention before launch. The theme options include an enable/disable control for the streaming system, so a site that only lists screenings can leave that layer out. The vendor also mentions that theme options can enable or disable the custom rating part, and separately that a global setting decides whether visitors may rate a movie at all. Those are different toggles, and turning off visitor rating does not remove the IMDB value you entered.

Ratings lists, and how top-rated orderings are built

The Showrate function is a listing mode rather than a badge. The vendor describes it as displaying a list of movies with rating information only: number of votes, pointed rate and star rate. Combined with an Order By option, the same mechanism produces a top-rated list.

For an entertainment site this is the difference between a static archive and a page that changes as votes accumulate. It also tells you what to plan for: a top-rated block is only as meaningful as the ratings beneath it, whether those come from imported IMDB values or from your visitors. If visitor rating is disabled globally, the ordering rests on whatever rating data you entered by hand.

There is no claim in the listing about moderation, vote fraud, or how votes are stored, so treat the rating layer as a presentation feature and test its behaviour on a staging copy if user-submitted scores are central to your plan.

Actors, directors and genre pages as a connected index

Person and category pages are not decorative. The vendor says actor and director pages hold a name, summary, biography, avatar and banner, plus birthday, birthplace, gender and nationality. The useful part is what sits underneath: a person's detail page lists the movies credited to them, so a cast member's page becomes a small filmography.

Genre pages have their own global settings: the number of movies per page and whether the page uses a sidebar or not. That is a practical control for large catalogues, where twenty films on a genre page would bury the pagination.

Taken together, these records mean the theme asks for real editorial effort beyond the movie entries. A thin cast list produces thin pages, and the description offers no automation for populating them. The IMDB import claim in the theme options is described as importing multiple movies, not people, so it is worth checking exactly what that import covers before relying on it to fill a cast database.

Populating content and building pages

AmyMovie's theme options include a setting described as importing multiple movies from the IMDB website, which the vendor presents as a way to fill a catalogue quickly. That is a vendor claim about what the option does. Because an import touches field mapping, images and duplicate handling, the sensible test is a small batch on a staging install before you commit a catalogue to it.

Page building is described through Elementor, WPBakery Page Builder and Visual Composer, and Breadcrumb NavXT is named for breadcrumb navigation. The marketplace attributes recorded on 4 November 2026 list Elementor, Visual Composer and WPBakery as compatible, along with WooCommerce 6.x through 9.x. Gutenberg Optimized is recorded as No, which does not mean the block editor is broken here; it means the vendor's documented editing path runs through the theme's own options and a page builder rather than blocks. If your team works in Gutenberg, budget for that mismatch or look at themes that lead with blocks.

Theme options also cover the site chrome: custom image sizes, Google Fonts and typography, a skin colour setting, three header layouts, a topbar that accepts widgets, and a footer with one to ten widget columns. The package is listed as containing PHP, CSS, SCSS and JS files, and the theme is marked responsive and widget ready.

One boundary is worth naming because the vendor's own summary blurs it. The description mentions support for online ticket bookings, while the concrete compatibility list only names WooCommerce versions. If selling tickets is the point of the site, confirm how booking and payment actually work rather than assuming a ticketing system ships with the theme.

Questions & answers