Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hey guys,
So I installed Botcha and all its dependencies and the modules page reported it was enabled. However, I followed instructions in the Botcha page about where to find it (Under user management in D6) but I cant find it. Any ideas?
Comment | File | Size | Author |
---|---|---|---|
#8 | botach_noadmin.png | 51.65 KB | boabjohn |
Comments
Comment #1
iva2k CreditAttribution: iva2k commentedTry to clear all caches.
Comment #2
iva2k CreditAttribution: iva2k commented[Duplicate post deleted]
Comment #3
pauln60 CreditAttribution: pauln60 commentedI can't find it either - installed the 'dev' D6, version, cleared the cache, logged in as admin - still not there. Any ideas?
Thanks,
Paul
Comment #4
pauln60 CreditAttribution: pauln60 commentedSo if the dev admin interface is broken / doesn't exist, is there any way to do this directly in the database?
Paul
Comment #5
iva2k CreditAttribution: iva2k commentedPlease check if #1969736: Error message on install applies to your situation and report here.
Comment #6
pauln60 CreditAttribution: pauln60 commentedThere doesn't seem to be an error on install - as for 'the BOTCHA configuration page'... where is that?
Comment #7
boabjohn CreditAttribution: boabjohn commentedSame effect here with a slightly different history.
We had D6 version installed and running effectively for about 6 months (thanks, excellent module!)
No change on the server or config that I am aware of...this weekend we got flooded with spam comments on nodes.
Investigating this morning, I noted BOTCHA in the admin menu, but when I tried to select it, it disappeared and I got taken to the correct url: /admin/user/botcha but there was no botcha UI.
Did a complete uninstall, and re-installed with latest dev. This time we don't even get a BOTCHA menu entry, and yes, nothing on the admin page either.
Under Modules, botcha shows as being installed with all dependencies. There are no missing items under site status.
Nothing in the Watchdog.
How next to troubleshoot?
Kind regards,
JB
Comment #8
boabjohn CreditAttribution: boabjohn commentedScreenshot attached
Comment #9
csc4 CreditAttribution: csc4 commentedHave you checked your PHP log files? I suspect that's what you might see with my issue https://drupal.org/node/2039611 - the latest packages on the site don't have the botcha.admin.inc (I've tried the 3 and 3 dev they're both missing).. I reported it two weeks ago but it doesn't seem to have got picked up...
Comment #10
boabjohn CreditAttribution: boabjohn commentedYou're probably right. We ran into a bunch of other issues (CTools related I think?) in the move to PHP5.4 and eventually had to downgrade back to 5.3 in order to get this D6 site to run.
Cheers.
Comment #11
csc4 CreditAttribution: csc4 commentedCould anyone out there with a working 6.3 possibly post a link to a download of a working package including botcha.admin.inc? even the Github link only seems to have .4
Comment #12
PatchRanger CreditAttribution: PatchRanger commentedCould be the reason of the problem: #2039611: botcha.admin.inc: failed to open stream: No such file.
Comment #13
PatchRanger CreditAttribution: PatchRanger commentedLooks like it is due to a bug in Moopapi module, which is a dependency for BOTCHA.
I am going to look into it at this weekend.
Comment #14
PatchRanger CreditAttribution: PatchRanger commentedI have fully debugged Moopapi module: see https://travis-ci.org/PatchRanger/drupal-moopapi/builds/9828543 .
New releases are available - so now it should be fixed.
Please note that both branches of Moopapi module (1.x and 2.x) require patches to be applied, 2.x also requires external library: use .make-file inside the module as installation instruction.
Please update and clear all caches. Re-open in case if the problem persists.
Comment #15
kshall CreditAttribution: kshall commentedInstalled latest 6.x.3.x dev modules and Botcha menu option under User management still does not display.
Comment #16
PatchRanger CreditAttribution: PatchRanger commentedCurrent state of debugging process is available here: https://travis-ci.org/PatchRanger/drupal-botcha .
It is not so easy, there is also core issue involved: see https://drupal.org/node/399642#comment-7723125 from #399642: Replace drupal_install_modules() with an improved module_enable().
Comment #17
kshall CreditAttribution: kshall commentedWhat is status on this issue? Does core patch to Drupal 6.x in post #16 need to be applied for menu to work? I am not seeing any spam being caught. Botcha counter under status report always shows 0 count. Can you provide a patch update for us to apply?
Comment #18
AlfTheCat CreditAttribution: AlfTheCat commented@patchranger
Which patches?
I updated to moopapi 1.x-dev because I was hoping that would fix #2039611: botcha.admin.inc: failed to open stream: No such file but now my interface has entirely.
It looks like BOTCHA 6.x-3.x is not usable atm.
Comment #19
smd_ksu CreditAttribution: smd_ksu commentedSubscribe
Comment #20
NPC CreditAttribution: NPC commentedDowngrading to MoopAPI 1.2 (from 1.3) for Botcha 6.x-3.0 helped in my case.
Comment #21
ehowland CreditAttribution: ehowland commented#20 worked for me. From botcha.info
version = "6.x-3.0+12-dev"
core = "6.x"
project = "botcha"
datestamp = "1380556789"
I am running php 5.2.7.
I did, however, see a warning from drush:
Invalid argument supplied for foreach() moopapi.module:21 [warning]
But that warning did not stop the appearance of the config page.
Comment #22
ippy CreditAttribution: ippy commentedYep, as per #20, downgrade to moopapi-6.x-1.2 did the trick for us too
php 5.3.3
Drupal 6.29
Botcha 6.x-3.0
No warnings on install
Comment #23
rwohleb@PatchRanger is a maintainer on both botcha and moopapi. As far back as April the botcha maintainer @iva2K said he was aware that moopapi after 1.2 had an API change that broke botcha 3.x:
https://drupal.org/comment/7344756#comment-7344756
... so why has no one updated the project page or README to mention this? There have been commits against the 6.x-3.x branch since April, so it's not like people haven't gotten back around to touching this version. This is burning new users of the module, which is a sure fire way to get them using a different module :(
Comment #24
iva2k CreditAttribution: iva2k commentedI updated the project page with an installation note.
So far it sounds that for this issues a workaround is to downgrade Moopapi to 6.x-1.2.
Comment #26
my-family CreditAttribution: my-family commentedI can confirm that downgrading moopapi to 6.x-1.2 solved the problem. Should we move this issue to moopapi project (and how)?
Comment #27
mubiesam CreditAttribution: mubiesam commentedHow about in D7, should it be the same step...
Comment #28
Stagger Lee CreditAttribution: Stagger Lee commentedIt is still happening, even in 7.x versions. Seems as cache deleting trigger dissapearance and visibility with no apparent logic. Need to be fixed, despite it is not something one use often.