-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rt-fulltext-indexer error #37
Comments
Hi, yes this happens since the latest Perl upgrade but haven’t got an update on the bug tracker on this one yet (https://rt.bestpractical.com/Ticket/Display.html?id=37702) |
Thank you |
Here's my current crontab for reference:
|
Thank you, that help a lot. Dunno why best practical disabled github issues. I googled the error message. Because of the authentication used by their bugtracker your ticket is not showed 😕 |
I think they disabled it because the github repo seems just to be a clone of their internal svn. There is also almost no way to reach out to them to report bugs because the issue tracker is full of spam. |
Oh I see. I've also an open PR with them since 6 month (bestpractical/rt#365). No answers from them. Yeah let's hope. 🙏 |
Hi,
I just upgraded my dev environment to 5.0.5 from 5.0.4.
After the update rt-fulltext-indexer command is triggering this error:
Attempt to call undefined import method with arguments ("1.40") via package "DBIx::SearchBuilder" (Perhaps you forgot to load the package?) at /opt/rt5/sbin/../lib/RT/SearchBuilder.pm line 75.
Same error popped up after upgrade command:
perl ./sbin/rt-setup-database --action upgrade --upgrade-from 5.0.4
I'm currently failing to find some infos from official request tracker forum.
Anyone here issuing the same error?
Thank you
Edit: without this line https://github.com/bestpractical/rt/blob/stable/lib/RT/SearchBuilder.pm#L75 no errors are shown. Idk perl, so really don't know what is happening. For sure something is wrong with the version stated in SearchBuilder.pm (https://github.com/bestpractical/rt/blob/stable/etc/cpanfile#L25)
The text was updated successfully, but these errors were encountered: