XF 2.2 accessing vars in a dump

[eDaddi]

I'm trying to use the 'Display condition' in a widget to only show the widget when a certain ad is displayed.

I do this:

{{ dump($xf.samAds)}}

and get this:


I can't figure out how to determine if the 'sponsoredText' or 'sponsoredLogo' values are there or not. What are the # lines? '#ads' in this example. I tried treating them as objects and arrays but can't access them.

 

[eDaddi]

The # means protected:

#<span class=sf-dump-protected title="Protected property">ads</span>:

In php it's easy to check if a property exists, how can I do it with XF's syntax so I can use it as a display condition? Clearly it's available to check

 

[Brogan]

I would expect the vars to be something like $xf.samAds.sponsoredText and $xf.samAds.sponsoredLogo but as it's third party code, it's something you will need to ask the add-on author about.

 

[eDaddi]

I would expect the vars to be something like $xf.samAds.sponsoredText and $xf.samAds.sponsoredLogo but as it's third party code, it's something you will need to ask the add-on author about.

That was my first guess too, I wouldn't think that it being 3rd party has anything to do with it as it's being output exactly as the rest of XF's variables. I seen this thread where @Earl used underscores to access these, but I can't get that to work either.

@Siropu , how can I detect if an ad is on a page or not? I have a widget I only want in certain forums, they display ads from your add-on. It's really easy in your add-on to select what forums the ads go in, now I just need the widget to detect if they are on/off for a page in order to display the widget or not. Otherwise I have to make a big in_array with all the forum ids I want or dont want to display it in.

 

[Brogan]

To clarify, you need to post the question in the resource thread, as that is where support for third party resources is limited to.

 

[eDaddi]

To clarify, you need to post the question in the resource thread, as that is where support for third party resources is limited to.

Right, I was hoping he'd chime in here to avoid two of the same issues.