Code: Select all
Fatal error: Uncaught Error: Call to a member function update_auto_groups() on null in htdocs/forum/ext/david63/privacypolicy/event/listener.php:281
Stack trace:
#0 [internal function]: david63\privacypolicy\event\listener->update_auto_groups(Object(phpbb\event\data), 'core.user_add_a...', Object(phpbb\event\dispatcher))
#1 htdocs/forum/vendor/symfony/event-dispatcher/EventDispatcher.php(184): call_user_func(Array, Object(phpbb\event\data), 'core.user_add_a...', Object(phpbb\event\dispatcher))
#2 htdocs/forum/vendor/symfony/event-dispatcher/EventDispatcher.php(46): Symfony\Component\EventDispatcher\EventDispatcher->doDispatch(Array, 'core.user_add_a...', Object(phpbb\event\data))
#3 htdocs/forum/phpbb/event/dispatcher.php(62): Symfony\Component\EventDispatcher\EventDispatcher->dispatch('core.user_add_a...', Object(phpbb\event\data))
#4 htdocs/forum/phpbb/event/dispatche in htdocs/forum/ext/david63/privacypolicy/event/listener.php on line 281
%sitename%
in various places around my forum, which displays the name of the board. I believe this extension adds that function and is used in the Terms of Service. Specifically: (hereinafter “we”, “us”, “our”, “%sitename%”, “http://www.myboard.com”)
.%siteurl%
to display the root path so I can change the Terms of Service to be: (hereinafter “we”, “us”, “our”, “%sitename%”, “%siteurl%”)
but also use it elsewhere in the forum.%sitename%
is specific to this extensionHi david, thanks for confirming.
%siteurl%
? I don't mind making manual edits.It works just fine in 3.2.2 - I have had it running for six months without a problem.Lord Phobos wrote: ↑Sat Sep 29, 2018 7:28 pm This extension doesn't work anymore after upgrading to 3.2.2.
The link to the policy in the navbar takes to a 404 page.
EDIT: it's a "php.app and url rewrite problem" that manifested itself only after upgrade to 3.2.2...
Please remember that everyone who helps here does so in their spare time and has a real life outside phpBB. I am sure David will get back to you as soon as he is able. You will just have to be patient.
I cannot re-create this problem so your assertion that it is affecting all IOS devices is incorrect.