Not sure if this has been fixed, and it's more of a "feature" than a bug, but..
We recently had a user spam a large number of resources (on request, but that's not important). Some users didn't like the flood, so they ignored this user. This resulted in whole pages of paginated results being...
Suggestion to replace if $template->History and similar:
$hasHistory = $this->finder('XF:TemplateHistory')
->where('type', $template->type)
->where('title', $template->title)
->where('style_id', $template->style_id)
->limit(1)
->fetch()
->count();
And in actionHistory, change this:
if...
After further testing, the root cause of the issue appears to be the TO::MANY relation of $template->History. Again, with indefinite records for each template, this relation will always cause a memory error if the history of edits gets too large.
Additionally, even if the actionHistory is corrected, this line from templateAddEdit also causes a memory error:
'hasHistory' => $template->exists() ? $template->History->count() : false,
@Chris D
The problem is here, in the XF\Admin\Controller\Template.php actionHistory method:
if ($template->History)
{
$list = $template->History;
$list = $list->toArray();
arsort($list);
}
This code is pulling all historical revisions (i.e., every edit ever made) into PHP memory...
I increased the limit in XF.php to 1G, and that let me open the template so I can see what's going on. The template currently only has 900 lines, but at the bottom of the page there are 1200 rows of edit history, hence my guess that this XF bug is caused by edit history, especially with larger...
This just started recently, and yes I had a rather large extra.less with about 9000 lines. I was in the process of breaking it up into separate .less files, when suddenly I hit this error:
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 204800 bytes)
Now, my...
The <xf:upload> button appears on the site as a drab early 2000's gray and white button.
In the template code, it looks like:
<xf:macro name="custom_dependent" arg-id="">
<xf:upload name="upload" accept=".gif,.jpeg,.jpg,.jpe,.png" id="{$id}" />
</xf:macro>
The button does not appear in...
I'm specifically referring to the inline image bbcode button.
Mostly I find we need it for screenshots, similar to above. Some examples would be:
screenshots of content that must be deleted, but is important for context in the note
since "reports" also do not allow image or file...
How would I go about changing reactions so that individual users could leave multiple reactions on the same post, similar to Discord? Where would I begin looking?
I also see this note in the docs:
I'm wondering if that has something to do with why I can't get the "active tab" functionality to work. It would be nice to know what this "important functionality" is...