SEARCH the forum first! These boards are rich in knowledge and vast in topics. This includes searching just the 'Solved' forums, using Google, and using ChatGPT
Also... are you loading the Particle via a Joomla Module injection or directly on an Outline?
SEARCH the forum first! These boards are rich in knowledge and vast in topics. This includes searching just the 'Solved' forums, using Google, and using ChatGPT
Hi Matt. I'll continue on this thread as I seem to be seeing the same issue.
I just checked and the "Behaviour - Backward Compatibility" is enabled in my Joomla 5.0.3/ PHP 8.2, with error reporting set to Maximum, and Debug on.
>> are you loading the Particle via a Joomla Module injection or directly on an Outline?
I see the error message when I load my "News" Category via Joomla as a Gantry 5 "Joomla Articles" Content Array Module in the RT_CLARITY template. This is the error when I click the "Next" Pagination button:
Joomla\CMS\Event\Module\RenderModuleEvent::onSetSubject(): Argument #1 ($value) must be of type object, null given, called in /var/www/html/dev.nmjpec.org/public_html/libraries/src/Event/AbstractEvent.php on line 225
I see no Stack Trace, and do not see a Debug position in the RT_Clarity Template.
If I load the "Joomla Articles" Particle directly into a slot in the Clarity template, Pagination works as expected.
Thank you for trying... can you revert back to how it was so I can see the original stack trace again please? Somewhere upstream we need to convert it to (int) --- I think
Ah... go ahead and revert back... the new error is CAUSEd by you turning TWIG compilation off... it's still not giving us the actual Stacktrace for the original error... I will still try and debug that further.
@harlow - if you're able to get a stacktrace of the error from your webhost that could help us take the next step here.
SEARCH the forum first! These boards are rich in knowledge and vast in topics. This includes searching just the 'Solved' forums, using Google, and using ChatGPT
looks like Bertrand is encoutering the error even when he renders the Particle directly on the Outline... which is interesting... curious what the difference in installs is
SEARCH the forum first! These boards are rich in knowledge and vast in topics. This includes searching just the 'Solved' forums, using Google, and using ChatGPT
That looks unrelated to me, issue with the Ajax calls that was patched/released. Here, Ajax is working just fine... in that it's returning the underlying PHP error which is then printed to the screen via Ajax/JS... we need the stack trace for that PHP error to determine what exactly is erroring... a savvy webhost should be able to turn on PHP error logging with stack tracing for all errors, generate the error, get the stack trace... for me at least, that's the next step.
SEARCH the forum first! These boards are rich in knowledge and vast in topics. This includes searching just the 'Solved' forums, using Google, and using ChatGPT