[TH] Monetize [Deleted]

Since Patch Level 2 getting spammed with these:

Code:
Server error log
[LIST]
[*]ErrorException: Template error: strtolower() expects parameter 1 to be string, array given
[*]src\XF\BbCode\Renderer\Html.php:516
[*]Generated by: Unknown account
[*]22 May 2019 at 14:51
[/LIST]

Stack trace
#0 [internal function]: XF\Template\Templater->handleTemplateError(2, 'strtolower() ex...', 'D:\\inetpub\\wwwr...', 516, Array)
#1 src\XF\BbCode\Renderer\Html.php(516): strtolower(Array)
#2 src\addons\ThemeHouse\Monetize\XF\BbCode\Renderer\Html.php(69): XF\BbCode\Renderer\Html->renderTagCode(Array, Array, Array, Array)
#3 [internal function]: ThemeHouse\Monetize\XF\BbCode\Renderer\Html->renderTagAttach(Array, Array, Array, Array, Object(ThemeHouse\Giphy\XF\BbCode\Renderer\Html))
#4 src\XF\BbCode\Renderer\Html.php(296): call_user_func(Array, Array, Array, Array, Array, Object(ThemeHouse\Giphy\XF\BbCode\Renderer\Html))
#5 src\XF\BbCode\Traverser.php(61): XF\BbCode\Renderer\Html->renderTag(Array, Array)
#6 src\XF\BbCode\Traverser.php(37): XF\BbCode\Traverser->renderSubTree(Array, Array)
#7 src\XF\BbCode\Traverser.php(20): XF\BbCode\Traverser->renderAst(Array, Object(SV\SignupAbuseBlocking\XF\BbCode\RuleSet), Array)
#8 src\XF\SubContainer\BbCode.php(219): XF\BbCode\Traverser->render('Tach,

unser Fo...', Object(XF\BbCode\Parser), Object(SV\SignupAbuseBlocking\XF\BbCode\RuleSet), Array)
#9 src\XF\Template\Templater.php(2021): XF\SubContainer\BbCode->render('Tach,

unser Fo...', 'html', 'ewr_porta_artic...', Object(SV\UserEssentials\XF\Entity\Post), Array)
#10 [internal function]: XF\Template\Templater->fnBbCode(Object(ThemeHouse\UIX\XF\Template\Templater), false, 'Tach,

unser Fo...', 'ewr_porta_artic...', Object(SV\UserEssentials\XF\Entity\Post))
#11 src\XF\Template\Templater.php(922): call_user_func_array(Array, Array)
#12 internal_data\code_cache\templates\l2\s19\public\EWRporta_articles_macros.php(257): XF\Template\Templater->fn('bb_code', Array, false)
#13 src\XF\Template\Templater.php(701): XF\Template\Templater->{closure}(Object(ThemeHouse\UIX\XF\Template\Templater), Array, Array)
#14 internal_data\code_cache\templates\l2\s19\public\EWRporta_articles_macros.php(86): XF\Template\Templater->callMacro('EWRporta_articl...', 'article_block', Array, Array)
#15 src\XF\Template\Templater.php(701): XF\Template\Templater->{closure}(Object(ThemeHouse\UIX\XF\Template\Templater), Array, Array)
#16 internal_data\code_cache\templates\l2\s19\public\EWRporta_articles_index.php(54): XF\Template\Templater->callMacro('EWRporta_articl...', 'articles_block', Array, Array)
#17 src\XF\Template\Templater.php(1301): XF\Template\Templater->{closure}(Object(ThemeHouse\UIX\XF\Template\Templater), Array)
#18 src\XF\Template\Template.php(24): XF\Template\Templater->renderTemplate('EWRporta_articl...', Array)
#19 src\XF\Mvc\Renderer\Html.php(48): XF\Template\Template->render()
#20 src\XF\Mvc\Dispatcher.php(418): XF\Mvc\Renderer\Html->renderView('EWR\\Porta:Artic...', 'public:EWRporta...', Array)
#21 src\XF\Mvc\Dispatcher.php(400): XF\Mvc\Dispatcher->renderView(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#22 src\XF\Mvc\Dispatcher.php(360): XF\Mvc\Dispatcher->renderReply(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#23 src\XF\Mvc\Dispatcher.php(53): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#24 src\XF\App.php(2177): XF\Mvc\Dispatcher->run()
#25 src\XF.php(390): XF\App->run()
#26 index.php(20): XF::runApp('XF\\Pub\\App')
#27 {main}
 
Since Patch Level 2 getting spammed with these:

Code:
Server error log
[LIST]
[*]ErrorException: Template error: strtolower() expects parameter 1 to be string, array given
[*]src\XF\BbCode\Renderer\Html.php:516
[*]Generated by: Unknown account
[*]22 May 2019 at 14:51
[/LIST]

Stack trace
#0 [internal function]: XF\Template\Templater->handleTemplateError(2, 'strtolower() ex...', 'D:\\inetpub\\wwwr...', 516, Array)
#1 src\XF\BbCode\Renderer\Html.php(516): strtolower(Array)
#2 src\addons\ThemeHouse\Monetize\XF\BbCode\Renderer\Html.php(69): XF\BbCode\Renderer\Html->renderTagCode(Array, Array, Array, Array)
#3 [internal function]: ThemeHouse\Monetize\XF\BbCode\Renderer\Html->renderTagAttach(Array, Array, Array, Array, Object(ThemeHouse\Giphy\XF\BbCode\Renderer\Html))
#4 src\XF\BbCode\Renderer\Html.php(296): call_user_func(Array, Array, Array, Array, Array, Object(ThemeHouse\Giphy\XF\BbCode\Renderer\Html))
#5 src\XF\BbCode\Traverser.php(61): XF\BbCode\Renderer\Html->renderTag(Array, Array)
#6 src\XF\BbCode\Traverser.php(37): XF\BbCode\Traverser->renderSubTree(Array, Array)
#7 src\XF\BbCode\Traverser.php(20): XF\BbCode\Traverser->renderAst(Array, Object(SV\SignupAbuseBlocking\XF\BbCode\RuleSet), Array)
#8 src\XF\SubContainer\BbCode.php(219): XF\BbCode\Traverser->render('Tach,

unser Fo...', Object(XF\BbCode\Parser), Object(SV\SignupAbuseBlocking\XF\BbCode\RuleSet), Array)
#9 src\XF\Template\Templater.php(2021): XF\SubContainer\BbCode->render('Tach,

unser Fo...', 'html', 'ewr_porta_artic...', Object(SV\UserEssentials\XF\Entity\Post), Array)
#10 [internal function]: XF\Template\Templater->fnBbCode(Object(ThemeHouse\UIX\XF\Template\Templater), false, 'Tach,

unser Fo...', 'ewr_porta_artic...', Object(SV\UserEssentials\XF\Entity\Post))
#11 src\XF\Template\Templater.php(922): call_user_func_array(Array, Array)
#12 internal_data\code_cache\templates\l2\s19\public\EWRporta_articles_macros.php(257): XF\Template\Templater->fn('bb_code', Array, false)
#13 src\XF\Template\Templater.php(701): XF\Template\Templater->{closure}(Object(ThemeHouse\UIX\XF\Template\Templater), Array, Array)
#14 internal_data\code_cache\templates\l2\s19\public\EWRporta_articles_macros.php(86): XF\Template\Templater->callMacro('EWRporta_articl...', 'article_block', Array, Array)
#15 src\XF\Template\Templater.php(701): XF\Template\Templater->{closure}(Object(ThemeHouse\UIX\XF\Template\Templater), Array, Array)
#16 internal_data\code_cache\templates\l2\s19\public\EWRporta_articles_index.php(54): XF\Template\Templater->callMacro('EWRporta_articl...', 'articles_block', Array, Array)
#17 src\XF\Template\Templater.php(1301): XF\Template\Templater->{closure}(Object(ThemeHouse\UIX\XF\Template\Templater), Array)
#18 src\XF\Template\Template.php(24): XF\Template\Templater->renderTemplate('EWRporta_articl...', Array)
#19 src\XF\Mvc\Renderer\Html.php(48): XF\Template\Template->render()
#20 src\XF\Mvc\Dispatcher.php(418): XF\Mvc\Renderer\Html->renderView('EWR\\Porta:Artic...', 'public:EWRporta...', Array)
#21 src\XF\Mvc\Dispatcher.php(400): XF\Mvc\Dispatcher->renderView(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#22 src\XF\Mvc\Dispatcher.php(360): XF\Mvc\Dispatcher->renderReply(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#23 src\XF\Mvc\Dispatcher.php(53): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#24 src\XF\App.php(2177): XF\Mvc\Dispatcher->run()
#25 src\XF.php(390): XF\App->run()
#26 index.php(20): XF::runApp('XF\\Pub\\App')
#27 {main}
Gonna tag @Lukas W. so he can take a look.
 
I see this add-on allows daily to monthly communication, is there a way to make it communicate more frequently? Say hourly or even better, 15 minutes??
 
I see this add-on allows daily to monthly communication, is there a way to make it communicate more frequently? Say hourly or even better, 15 minutes??
Monetize relies on the XenForo cron system which doesn't reliably run every minute, fifteen minutes, or hourly for that matter. But this is something we have reviewed before but no official ETA of when it will be integrated within Monetize.
 
Is there a way to differentiate between the no permission and not logged in error? Currently the upgrade page is showing for guests and in my opinion it should prompt them to login first, who knows they may already have the necessary permissions?
 
Hi,
I have just purchased the add-on and I am looking forward starting the setup next days.
Before to start, I have just a basic question.
How payments are managed, where I setup a way of payment (paypal, Stripe,...)?
Thanks
David
 
Is there a way to differentiate between the no permission and not logged in error? Currently the upgrade page is showing for guests and in my opinion it should prompt them to login first, who knows they may already have the necessary permissions?
No, this isn't possible with the error, although you could use the Upgrade Page overlay option instead and use the User Criteria to differentiate between registered users and guests. But I'll go ahead and make an issue on this as well.
Hi,
I have just purchased the add-on and I am looking forward starting the setup next days.
Before to start, I have just a basic question.
How payments are managed, where I setup a way of payment (paypal, Stripe,...)?
Thanks
David
Go to your administrative panel before navigating to Setup -> Service Providers -> Payment Profiles -> Add payment profile -> Select Paypal, Stripe, or any other provider that is provided within XenForo.
 
I already bought this and you need to get this addon if you ever intend to have forum sponsors. It has a lot of potential and I am enjoying it so far.

I would like to make this suggestion, is it possible to do some blending in this area so its more apparent which node is being sponsored? Or perhaps a darker border below the sponsored by row so it seems more 'included' with the node it is bound to?
203615

The sponsored label is below the node which it belongs to, but at first glance it could get confusing.

Second, is it possible to have an option to show the logo below the node name? in the description area? I've found that putting the logo up above doubles the height of the sponsored sections and that can be a bit much. Also, when you're inside this forum, it can be nice to see the company logo at the top of the forum. I think this is another good 'option' for applying this sponsoring logo. Or maybe just removing the forum node names entirely and allowing the logos to do the work? I have clickable nodes enabled or whatever the option is that makes the entire node row a clickable element.
203616
 
Another feature I'd like to see is a rotation group. Where you can add sponsors to a group and set a node (and possibly other locations?) to rotate between them over a period of time.

Lastly, an "Advertise Here" prompt would be nice.
 
Hi all,
It would be great to write a documentation about “Efficient user upgrade monetization strategy” with your add on.
For exemple, you could recommend us an efficient setup with some upgrades and the related communications your upgrade allows.
I will try several things by myself, but I am pretty sure that sharing your experience in marketing automatisation for user upgrades thanks to “[TH] monetize” would be great.
It would clarify to potential customers, what they can expect from the Addons, and it would help customers to start well by implementing best practices efficient communications.
Just an idea :)
Thanks
David
 
Hello,
I am trying to change the setup of "Upgrade page display" this way :
I would like to display the upgrade page as an overlay, only once a week to all members having not yet an upgraded their account.
I have found limitations for alerts, messages & conversations but not for overlay display.
Is it possible to limit upgrade page as an overlay display this way?
Thanks in advance
David
 
Hi all,
It would be great to write a documentation about “Efficient user upgrade monetization strategy” with your add on.
For exemple, you could recommend us an efficient setup with some upgrades and the related communications your upgrade allows.
I will try several things by myself, but I am pretty sure that sharing your experience in marketing automatisation for user upgrades thanks to “[TH] monetize” would be great.
It would clarify to potential customers, what they can expect from the Addons, and it would help customers to start well by implementing best practices efficient communications.
Just an idea :)
Thanks
David
This isn't really something we can help with as every website is different but we did a blog post on usage ideas for Monetize here.
Hello,
I am trying to change the setup of "Upgrade page display" this way :
I would like to display the upgrade page as an overlay, only once a week to all members having not yet an upgraded their account.
I have found limitations for alerts, messages & conversations but not for overlay display.
Is it possible to limit upgrade page as an overlay display this way?
Thanks in advance
David
This isn't something that is doable right now but it is a good idea that I'll mention to our developers along with adding it to our issue tracker as a feature suggestion.
 
Top Bottom