You need to re-index ElasticSearch. Make sure you click "optimize" in the setup page (might need todo it multiple times it is dumb), and then do a full-reindex.After installing, i'm having a lot of this in the error log:
- XFES\Elasticsearch\RequestException: Elasticsearch indexing error (queued): failed to parse field [report_state] of type [long] in document with id 'report-3058'. Preview of field's value: 'resolved'
- src/addons/XFES/Elasticsearch/Api.php:409
- Generiert von: Florian_PL
- 9 November 2020 um 23:31
Stack-Trace
#0 src/addons/XFES/Elasticsearch/Api.php(330): XFES\Elasticsearch\Api->request('put', 'planetliebe/_do...', '{
"title": ...')
#1 src/addons/XFES/Elasticsearch/Api.php(348): XFES\Elasticsearch\Api->requestFromIndex('put', '_doc/report-305...', Array)
#2 src/addons/XFES/Elasticsearch/Api.php(152): XFES\Elasticsearch\Api->requestById('put', 'report', 3058, Array)
#3 src/addons/XFES/Search/Source/Elasticsearch.php(54): XFES\Elasticsearch\Api->index('report', 3058, Array)
#4 src/XF/Search/Search.php(40): XFES\Search\Source\Elasticsearch->index(Object(XF\Search\IndexRecord))
#5 src/XF/Behavior/Indexable.php(46): XF\Search\Search->index('report', Object(SV\ReportCentreEssentials\XF\Entity\Report), true)
#6 src/XF.php(318): XF\Behavior\Indexable->XF\Behavior\{closure}()
#7 src/XF/Mvc/Dispatcher.php(156): XF::triggerRunOnce(true)
#8 src/XF/Mvc/Dispatcher.php(55): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#9 src/XF/App.php(2300): XF\Mvc\Dispatcher->run()
#10 src/XF.php(465): XF\App->run()
#11 index.php(20): XF::runApp('XF\\Pub\\App')
#12 {main}
It is likely trying to compute viewable open report counts for a queue. This looks somewhat wrong but I'll try to figure out how this is happeningAlso i'm not be able to look into a report. I get a 500 error and in the errorlog this is showing up:
Server-Fehlerprotokoll
- ErrorException: Fatal Error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 327680 bytes)
- src/XF/Mvc/Entity/Finder.php:1392
- Generiert von: Florian_PL
- 9 November 2020 um 23:38
Stack-Trace
#0 [internal function]: XF::handleFatalError()
#1 {main}
Status der Anfrage
array(4) {
["url"] => string(43) "/reports/queue/allgemeine-meldungen.1/3090/"
["referrer"] => string(67) "https://dev69.planet-liebe.de/reports/queue/allgemeine-meldungen.1/"
["_GET"] => array(1) {
["/reports/queue/allgemeine-meldungen_1/3090/"] => string(0) ""
}
["_POST"] => array(0) {
}
}
I've never had any memory problems at all! It's a huge cluster with lot's of power.
FYI; This was a bug in Report Improvements, where it was trying to load users with a "can update report" with the value of "never" for potential users who can have reports assigned to them. These incorrect users would be would be filtered out by the view check, but there where enough users being loaded this caused an out-of-memory error.Also i'm not be able to look into a report. I get a 500 error and in the errorlog this is showing up:
Server-Fehlerprotokoll
- ErrorException: Fatal Error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 327680 bytes)
- src/XF/Mvc/Entity/Finder.php:1392
- Generiert von: Florian_PL
- 9 November 2020 um 23:38
Stack-Trace
#0 [internal function]: XF::handleFatalError()
#1 {main}
Status der Anfrage
array(4) {
["url"] => string(43) "/reports/queue/allgemeine-meldungen.1/3090/"
["referrer"] => string(67) "https://dev69.planet-liebe.de/reports/queue/allgemeine-meldungen.1/"
["_GET"] => array(1) {
["/reports/queue/allgemeine-meldungen_1/3090/"] => string(0) ""
}
["_POST"] => array(0) {
}
}
I've never had any memory problems at all! It's a huge cluster with lot's of power.
Report Centre Essentials is not compatible with XF 2.2.sorry I have expressed myself unclearly!
We use XF 2.2 and the 4.0.0 Beta 2
- Require php 7.0+
- Require Report Improvements v2.6.0+
- Now depends on Standard Library by Xon (v1.1.0+)
- Compatibility fix for User Essentials for XF2.2+
- Compatibility fix for Report Improvements reaction support
- Fix double-encoding of cache values, which is surprisingly expensive
- Fix that report comment statistics included non-comment actions (ie filter out report comments without a message)
- Improve approval queue finding relevant report for 3rd party content, or defaulting to the user's report
- Conform support for XF2.2
- Reduce memory usage when computing pre-user-per-report-queue counts
- Fix potential infinite recursion when attempting to discover the linked report for an approval queue item
@Joe Link can you try logging out and then back in again? There is some wonky caching that likely needs some kicking.
I've got major update in the works which may help this, but it is still stuck in testing hell.
The counts should only be for reports you can see, but I think I patched that in the next major version.Apologies @Xon, it was due to another addon. There were (a ton of) valid reports in the queue, I just didn't have permission to view them
- Add php 7 type hinting
- Require Report Improvements v2.8.0
- Force global namespace for functions which are known to be optimizable to bytecode in php
- Fix report queue last action column updating
- Now includes recently closed/rejected reports, these will age out (after a day).
- Bulk actions now update it
- Report comments which did not change the report state now update it
- Move report queue read tracking into database instead of session
- Add report...
- Fix "Template error: [E_USER_WARNING] Macro public:svReportCentreEssentials_report_macros:resolve_report is unknown" on deleting a thread
- Fix NF/Discord compatibility
- Require Report Improvements v2.10.0+
- Fix admin 'manage report queues' was not enforced
- Fix " Macro public:svReportImprov_report_macros :: resolve_report() error: Macro argument report is required and no value was provided" on deleting threads
- Fix resolving reports on thread move/delete was offers to moderators would could not resolve reports
- Fix only a single thread of reports could be...
- Require for Report Improvements 2.10.8+
- Improve how report queue feature is bolted onto the Reports controller.
- php 8.2 compatibility fix
- Fix adding a new report queue did not trigger permissions rebuild
- Add "Container owner state" to report queue rules for detecting if the reporter/reported is the owner of a thread (or profile for profile posts/comments)
- Change "All user groups"/"None" option to "Disabled" for reporter/reported user criteria to better represent how matching actually works.
- Fix installer not triggering permission rebuilds are triggered when default permissions are applied.
- Add missing phrase when sorting report queue rules
- Require Xenforo 2.2+
- Add feature "Copy reply bans from a thread", gate behind "Copy reply bans from existing thread" permission permission.
Default granted to groups with "Ban users from replying to a thread" permission
We use essential cookies to make this site work, and optional cookies to enhance your experience.