Support

February 21, 2020 at 7:17 am

Hi there,

Was this original feature lost in the plan after the Trello KanBan board began driving features?

No, the ticket scope request is still shown on our roadmap here: https://trello.com/c/zCsClu98/112-promotions-add-ticket-scope-to-promotion

Currently, we are working on recurring events and all of the related changes required for that function correctly/smoothly. To give a quick example recurring events could have many datetimes, the current editor loads all datetimes which then usually exceeds the max_input_vars on most hosts so we refactored the code to prevent that. That may sound like a small change but when you consider that relationships between datetimes, tickets and the event are critical this get much more complex very quickly.

Once the editor and recurring events are ready we can then start looking at other features to add.

I am willing to explore the GitHub snippet that EE has labeled by this name: “bc_ee_ticket_scope_promotions.php” but there is zero description related to where the functional features appear and how to use it.

The functional features do not appear anywhere.

The first few lines of that snippet HERE is a comment explaining what you need to do for that snippet to work.

So if you have a promotion code with ID 100 that you want to only apply to tickets 111 and 112 and then another with ID 200 that applies to tickets 222 and 223 you’d set the array to something like:

$applicable_promotion_tickets = array( 
    100 => array(111, 112),
    200 => array(222, 223),
);

I am in a mission-critical sales season for events and typically do not like adding snippets for fear of introducing difficult to find instabilities. Although I could re-build the whole site from back-ups very quickly…

Generally, if we provide a snippet then that snippet will not make database changes meaning restoring to a backup shouldn’t be required. Having said that snippets aren’t officially supported, so backing up prior is always a good idea just to be safe.

Can you briefly describe how this snippet functions and where I can find the features in the admin panel to get a quick-start on how to put this feature to work?

As mentioned above, it doesn’t add functionality to the admin panel, it simply adds a means you can set promotions applicable to specific tickets through the code itself.

Does it appear in the SCOPE pull-down selector?

No.

How do I use it?

See above, you add the snippet to a custom functions plugin, we have some documentation on creating one here:

https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/

Then you set the Promotion ID’s and ticket ID’s that are applicable in the $applicable_promotion_tickets array.

Promotion Scope it ready for more features because it is a standard part of sales growth, influencing and pushing buzz organically.

Apologies but I don’t follow this sentence.

Shouldn’t these types of code snippets be integrated into the full functionality of the Promotions Plug-In? Or are there down-sides I should consider?

I think its important to explain where are snippets have come from.

If we have provided a snippet it’s to a fill a need, whatever that need may have been (be it something with promotions or something completely unrelated) that may be useful for others. They generally do not provide a ‘polished’ feature and should not be considered the final product of any feature they may add.

So they are unsupported functions that may or may not work for your use case which we provide as an alternative to simply stating ‘no, we don’t support that’. Usually, they have been provided by the support team and have not reviewed by our developers with all of the involvement that would go along with that (delaying the snippet/functions/feature and pulling them from whatever they are working on).

They may well end up included in the add-on they are intended for although will be much more heavily tested by the team, polished, reviewed, a UI added to handle updates (if applicable) and so on. Obviously that then delays the process and requires developer reviews, planning the UI and discussing any additional features/issues that may come from adding it.

In short, snippets give you additional functionality we don’t officially support, they have been created and tested for the specific use case they were designed for but that’s all. They may help you (or any user) with the same request which is why we provide access to them.