Change Eventful’s HTML by copying a template file into your theme.
This is for developers. For most changes, the Content and Style tabs are enough and survive updates without extra work.
- Find the file in the plugin, in
wp-content/plugins/eventful-pro-for-elementor/src/Frontend/templates/. - Create the folder
eventful-pro-for-elementorin your child theme. - Copy the file into it, keeping the same sub-folders. For example,
templates/item/title.phpbecomesyour-child-theme/eventful-pro-for-elementor/item/title.php, andtemplates/theme/grid/theme-one.phpbecomesyour-child-theme/eventful-pro-for-elementor/theme/grid/theme-one.php. - Edit the copy. Eventful uses it instead of the plugin’s file.
The comment at the top of each template file shows the path to use in your theme.
Which files exist #
| File | What it renders |
|---|---|
| grid.php, list.php, carousel.php, timeline.php, table.php, accordion.php | The wrapper of each layout |
| item/thumbnail.php, item/title.php, item/event-fildes.php, item/content.php, item/read-more.php, item/social-share.php | The parts of a Custom event card |
| theme/grid/, theme/list/, theme/minimal-list/ (theme-one.php, theme-two.php, theme-three.php) | The pre-made templates |
| filter-bar.php, pagination.php, section-title.php, preloader.php | Filters, pagination, section title and preloader |
Icons and stylesheets #
- Eventful loads a small Font Awesome subset with the icons its widgets use. If your override prints other Font Awesome icons, load the full set with the
eventful_pro_for_elementor_fontawesome_fullfilter (free version:eventful_for_elementor_fontawesome_full), for exampleadd_filter( 'eventful_pro_for_elementor_fontawesome_full', '__return_true' );. - Styles are split:
eventful.main.cssfor every widget,eventful.premade.cssonly for widgets set to Pre-made Templates, andeventful.<widget>.cssfor widgets with their own layout styles. Style your overrides in your theme, not in these files.
Keep overrides up to date #
Use a child theme, so theme updates do not remove your files. After a plugin update, compare your copies with the new plugin files (the changelog mentions template changes) and copy across any fixes.
