Another snippet issue: snippet name in MT different from XML entry name

Reply
L3 Networker

Another snippet issue: snippet name in MT different from XML entry name

I defined a snippet named myLogF in MT3.0.3. The XML was simply a place-holder to be able to assign "default" to log-forwarding in rules: <entry name="default"></entry>.


I pulled in snippet into project, and when I attempted to add it to rules using multi-edit, in the log forwarding pop-up chooser, it listed "myLogF" as the profile, which I guess made sense since that's what MT was using.  I assumed (incorrectly) that MT would automatically map that name to the one defined in the XML "snippet" :smileywink:   Unfortunately, that was not the case.  All rules ended-up with a log-forwarding field of "myLogF" instead of "default".


So it's easy to workaround, I'll just rename the snippet as "default" and be done.  But that's not very intuitive.


--Felix


L7 Applicator

Re: Another snippet issue: snippet name in MT different from XML entry name

Hi,

I think you are right, let us change the behaviour for the next release. Thanks for the feedback

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!