Admin Log Search

Admin Log Search [Paid] 2.8.2

No permission to buy ($30.00)
Hello, Xon.
Few issues here

Got this wen search contains symbol '
Code:
XF\Db\InvalidQueryException: MySQL statement prepare error [1064]: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'Бухательная\\'\%') OR (convert(`xf_moderator_log`.`action_params` ...' at line 4 in src/XF/Db/AbstractStatement.php at line 230
XF\Db\AbstractStatement->getException() in src/XF/Db/Mysqli/Statement.php at line 198
XF\Db\Mysqli\Statement->getException() in src/XF/Db/Mysqli/Statement.php at line 41
XF\Db\Mysqli\Statement->prepare() in src/XF/Db/Mysqli/Statement.php at line 56
XF\Db\Mysqli\Statement->execute() in src/XF/Db/AbstractAdapter.php at line 96
XF\Db\AbstractAdapter->query() in src/XF/Mvc/Entity/Finder.php at line 1430
XF\Mvc\Entity\Finder->fetch() in src/XF/Admin/Controller/Log.php at line 125
XF\Admin\Controller\Log->actionModerator() in src/addons/SV/AdminLogSearch/XF/Admin/Controller/Log.php at line 715
SV\AdminLogSearch\XF\Admin\Controller\Log->actionModerator() in src/XF/Mvc/Dispatcher.php at line 352
XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 259
XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 115
XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 57
XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2487
XF\App->run() in src/XF.php at line 524
XF::runApp() in admin.php at line 13
 
And I wanted to ask you about how the search works.
If I search for 1-2 or 3 first words of a phrase, the search finds them correctly.
When I search for a phrase with more words or a unique keyword or post ID within a phrase, I can't find them. Search is done in Cyrillic if it matters
 
W
Hello, Xon.
Few issues here

Got this wen search contains symbol '
Code:
XF\Db\InvalidQueryException: MySQL statement prepare error [1064]: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'Бухательная\\'\%') OR (convert(`xf_moderator_log`.`action_params` ...' at line 4 in src/XF/Db/AbstractStatement.php at line 230
XF\Db\AbstractStatement->getException() in src/XF/Db/Mysqli/Statement.php at line 198
XF\Db\Mysqli\Statement->getException() in src/XF/Db/Mysqli/Statement.php at line 41
XF\Db\Mysqli\Statement->prepare() in src/XF/Db/Mysqli/Statement.php at line 56
XF\Db\Mysqli\Statement->execute() in src/XF/Db/AbstractAdapter.php at line 96
XF\Db\AbstractAdapter->query() in src/XF/Mvc/Entity/Finder.php at line 1430
XF\Mvc\Entity\Finder->fetch() in src/XF/Admin/Controller/Log.php at line 125
XF\Admin\Controller\Log->actionModerator() in src/addons/SV/AdminLogSearch/XF/Admin/Controller/Log.php at line 715
SV\AdminLogSearch\XF\Admin\Controller\Log->actionModerator() in src/XF/Mvc/Dispatcher.php at line 352
XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 259
XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 115
XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 57
XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2487
XF\App->run() in src/XF.php at line 524
XF::runApp() in admin.php at line 13
What version of XF?

And I wanted to ask you about how the search works.
If I search for 1-2 or 3 first words of a phrase, the search finds them correctly.
When I search for a phrase with more words or a unique keyword or post ID within a phrase, I can't find them. Search is done in Cyrillic if it matters
It is a simple text match, it doesn't do anything fancy like use elasticsearch
 
Might have run into a bug, not 100% certain, but going to throw this out there....

XF: v2.2.13 (still on .13 for reasons 😐)
Addon: v2.6.2 (Supporting Dependency: Standard Library v1.18.4)
PHP: v8.1.28
Errors: None reported at the server level or XF error logs that would be related to this report.

Summary of the issue:
In this example case, we're looking at searching through the IP ban log from the XF ACP. We are searching a specific string that would be contained in the reasons field for each banned address, etc.

1715242920757.webp

Using just the search term, and clicking the "Filter" button, we get the results in the next screen (showing the count):

1715242999643.webp

The first page is correct and then we would like to view the following pages by clicking on the pagination numbers in the image below. The problem is, if we click any page number other than "1", the filter is erased and it reverts to showing the whole index. (Below)

1715243095137.webp

If we try to click back to one, the filter still has been reset back to empty.

1715243136287.webp

Expected Result:
We believe that the pagination should carry the filter forward instead of resetting upon trying to view page 2+ of the filtered results.

Workaround:
As the base XF does not offer a filtering/search for this screen, we just export the data in XML and find the data we need in an offline tool.

We did not have a lot of resources available to test other parts of this addon, but I did note personally that the pagination appeared to be working on the server error log page as well as the user change logs, where there are plenty of samples to work with.
 
We believe that the pagination should carry the filter forward instead of resetting upon trying to view page 2+ of the filtered results.
Apologies, I've managed to miss this bug!

It should work but looks like the pagination variables weren't properly updated, I'll have a look into this likely early next week.
 
  • Like
Reactions: ENF
Apologies, I've managed to miss this bug!

It should work but looks like the pagination variables weren't properly updated, I'll have a look into this likely early next week.
Thanks, it wasn't a super big priority since there was a workaround. Appreciate you looking into it when time allows. (y)
 
Apologies, I've managed to miss this bug!

It should work but looks like the pagination variables weren't properly updated, I'll have a look into this likely early next week.
I was reminded of this bug when working on the data for my other post earlier today -- I know you have your hands full, but just a gentle reminder about this one. Thank you!
 
Might have run into a bug, not 100% certain, but going to throw this out there....

XF: v2.2.13 (still on .13 for reasons 😐)
Addon: v2.6.2 (Supporting Dependency: Standard Library v1.18.4)
PHP: v8.1.28
Errors: None reported at the server level or XF error logs that would be related to this report.

Summary of the issue:
In this example case, we're looking at searching through the IP ban log from the XF ACP. We are searching a specific string that would be contained in the reasons field for each banned address, etc.

View attachment 302363

Using just the search term, and clicking the "Filter" button, we get the results in the next screen (showing the count):

View attachment 302364

The first page is correct and then we would like to view the following pages by clicking on the pagination numbers in the image below. The problem is, if we click any page number other than "1", the filter is erased and it reverts to showing the whole index. (Below)

View attachment 302365

If we try to click back to one, the filter still has been reset back to empty.

View attachment 302366

Expected Result:
We believe that the pagination should carry the filter forward instead of resetting upon trying to view page 2+ of the filtered results.

Workaround:
As the base XF does not offer a filtering/search for this screen, we just export the data in XML and find the data we need in an offline tool.

We did not have a lot of resources available to test other parts of this addon, but I did note personally that the pagination appeared to be working on the server error log page as well as the user change logs, where there are plenty of samples to work with.
This affects the banned email/banned ip/discouraged ip lists. Should have a fix for this tomorrow (in the next round of update releases)
 
  • Like
Reactions: ENF
This affects the banned email/banned ip/discouraged ip lists. Should have a fix for this tomorrow (in the next round of update releases)
Thanks, appreciate your time in addressing this one. (y) (Well, appreciate all the fixes an updates!)
 
Back
Top Bottom