@jaredc
Disabling the PHx Plugin solved my problem indeed. I guess there is a problem with the processing order (PHx processes source before EasyEvents does).
I just had PHx installed for testing purposes, therefore i’m fine with just disabling it. There might be others that need PHx though, so it’s probably worth the effort to find a workaround?
Other than that, i have some feature requests/propositions for EasyEvents:
Support for multiple Languages. Especially the easyEvents.config.php and the Snippet Params should be translatable. For example: Pass a (optional) language id to the Snippet and it will load a language-specific config file. Most likely the config would have to be split into global-configuration and translatable parts.
Custom placeholder fields. It would be really nice, if one could put custom fields into the templates.
Example:
<div class="easyEventsList_item">
<div class="easyEventsList_time">[+eventTime+]</div>
<div class="easyEventsList_title">[+title+]</div>
<div class="easyEventsList_description">[+description+]</div>
<div class="easyEventsList_introtext">[+introtext+]</div>
<div class="easyEventsList_myTv">[++myTv++]</div>
</div>
The snippet would then have to parse the template and get all the required fields either from the document or from template variables. In my example i distinguish template variables from the "regular" placeholders with a different syntax ([++tvname++]). Could be different ofc.
Most likely i’m going to hack some of the functionality into your existing code. At first, this is going to be a translation of the config files.
