Tuan,
Perhaps I am overthinking this, but I am having doubts about including the surrounding text in the generation of that tag. On the one hand, the use of that tag is pretty specific - it is only useful if the ZOOM registration URL has been entered in the Registration Completed URL. The experience on this particular site is that users often do not realize that they have to complete the ZOOM registration form when it is first presented to them after they submit the EB registration so they have no unique ZOOM event URL to use - and others somehow lose track of the confirmation email they receive from ZOOM that contains the unique URL they need to join the ZOOM event.- In both scenarios they have to (re)register with ZOOM in order to participate in the ZOOM event . I understand that implementation of the full integration between EB and ZOOM would eliminate the first problem as the ZOOM event registration is automatically performed for them. I am not sure (as I have not fully digested the docs on this) that the problem of losing the unique URL for joining the ZOOM event is somehow eliminated. In any case, implementing that integration, looks somewhat daunting - time consuming, involving the use of multiple tools from ZOOM and new (to me) stuff from EB - which is likely to lead to a frustrating process of finding and correcting errors... all with an end result that, as far as I can tell, may still result in some registrants losing track of their unique URL to join the Zoom event.
That is why it seemed like a good idea to include some text surrounding the ZOOM event registration URL explaining why it is appearing wherever it appears.
On the other hand, that explanatory text could be left to to the Admin to enter. I'm still undecided as to whether the generation of that text in the function interpreting the REQUEST_COMPLETE_URL is overstepping the bounds of what should be done within the function, but I am unable to see a downside to doing it - other than the fact that it is not modifiable by, for example, new text defined in the Translation part of the component. It would be good if a string (called, for example, "EB_ZOOM_REGISTRATION_REMINDER" could be created there that included the tag (something like "text that comes before [REGISTRATION_COMPLETE_URL] text that comes after ) and the function could use the text in that string to construct the link to the unique URL to register with the ZOOM event surrounding by the before and after text. That seems like something that is probably reasonably easy to implement, and which would allow an Admin more flexibility in creating the exact text that they feel is appropriate. How would the function get the value of what I presume is a CONSTANT to perform this magic?
thanks again for your patience and your willingness to be helpful and flexible in order to meet the incredibly varied needs of your users.
Dave Ascher
