Recent content by D33_UK

Oddly enough we got no issues with RC2 - errors started with 3 and now 4

We seem to be getting a problem with 2.3 Release Candidate 4. ErrorException: Fatal Error: Declaration of MaZ\PotentialTagHelper\Job\RebuildPotentialTagWords::complete() must be compatible with XF\Job\AbstractJob::complete(): XF\Job\JobResult...

Lol - please patch RC3/release rc4 ! THanks I'll look there

Don’t worry about it. It’s no longer active

I've got the same problem regarding age old threads being 'trending' and so making this panel irrelevant. So how do I: disable view tracking See these options - I only see the main widget setting

OK I've enabled the switch and tested our two variants as-is. The lighter (default) scheme is unreadable when forced to 'dark'. The Darker scheme is unreadable when forced to 'alternate'. So I guess that means we need to change our style to be 'variant-compatible' but I haven't a clue how to go...

Is there an idiot's guide to help me get this working on my site? I have a default style (light) and a selectable 'dark'. How do I get this working to auto swap to align to OS?

I completed the delist tool which is for office365 - it said I'd no problem but then queried if my problem was with hotmail/live/outlook (which it is) and provided me with a second form to fill. I've done this and am awaiting feedback

Being a bit thick here. I've upgraded to 2.3RC2 do I need to do anything to allow 'auto dark mode' switching by the OS? I have a default style that is 'light' and a selectable 'dark mode' in 2.2

Thanks for the response I get 84 "ok"s and 2 timeouts checking my domain - sixcrazyminutes . com

Evening All. Hope this is the right place for my request for help. At the end of last year I jumped in to help the last admin on a board I’ve been posting on for years. Short story is we’d lost all bar one of the techies that set up the place back in 2006 and migrated to XF in 2012. The server...

Getting two constantly reported in the log after upgrade (test system) 1: ErrorException: [E_DEPRECATED] Return type of Laminas\Feed\Reader\Feed\AbstractFeed::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily...

Well just to leaving my thinking here in case it helps. SELECT xf_conversation_message.username, xf_conversation_message.message FROM xf_conversation_message JOIN xf_conversation_user ON xf_conversation_message.conversation_id = xf_conversation_user.conversation_id WHERE...

I was going to suggest a bit of SQL as a solution but then realised that "Conversations" can have multiple parties and so deleting all the messages in a conversation would not just cover those to/from a particular individual but between all parties. Also, might be a bit dodgy deleting data...

Understood I can report 2.18.2 Report Improvements has to be disabled in beta 7 due to: Fatal error: Declaration of SV\ReportImprovements\XF\Repository\Report::getModeratorsWhoCanHandleReport(XF\Entity\Report $report) must be compatible with...