I like to stay close to the XF core
I believe this is the issue.Tested that on my staging server with 30mln posts without issues...
xf-rebuild:search --truncate
got killed for me (twice) because it used too much memory:--- a/src/XF/Job/AbstractJob.php
+++ b/src/XF/Job/AbstractJob.php
@@ -99,7 +99,7 @@ abstract class AbstractJob
if ($percentSpent > 1)
{
-...
Under these conditions 2.3.1 would never be released because not all plugins will be updated by their authors.2.3 The most affected plugins right now. 2.3.1 should never be released before the 2.3 update of the plugins is completed.
The vital structure of many forums is related to plugins.
It will be updated.Under these conditions 2.3.1 would never be released because not all plugins will be updated by their authors.
A 2.3.1 release would be bug fixes, and any plugin updated for 2.3.0 should work on it.
I don't think you understand what I was saying.It will be updated.
That much labor and time cannot be wasted.
Xf has prepared the ground, what else will it do?
#metoo3.0.1![]()
And me although I'll run up a 3.0.0 test site. I'm just keeping my fingers crossed that the new editor will cater better for different devices and browsers.3.0.1![]()
I'll most likely wait until the stable release of 3.0 is around before upgrading because we will all be able to see it on here.And me although I'll run up a 3.0.0 test site. I'm just keeping my fingers crossed that the new editor will cater better for different devices and browsers.
We use essential cookies to make this site work, and optional cookies to enhance your experience.