I've received many bug reports like #1239712: Settings page missing from various users and for various different modules, all on D7:

admin/config/administration/admin_menu brings up the general configuration page, ie same as admin/config

i.e., the module is enabled, but none of its menu paths exist.

Further findings:

  1. The module appears on the status report page, if implementing hook_requirements()
  2. The users installed the module with uid 1. No permission issues involved.
  3. The module is shown as enabled on the modules page.
  4. The users tried to uninstall, download a fresh tarball, and re-install from scratch, several times.
  5. The users do NOT use drush.
  6. Some of the users are on PHP 5.2.
  7. Some users are on Drupal 7.4 and some others on 7.6.
  8. Bug reports started to get filed around 3 weeks ago. So maybe a bogus change in 7.4?

I've no idea what's happening. Can't reproduce it myself. Also, some of the modules have tests, which even cover a manual installation procedure (instead of setUp(array($module))).

Actually tempted to mark this critical.

Related issues

CommentFileSizeAuthor
#22 mollom.jpg76.09 KBJuppk1
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tim.plunkett’s picture

I've seen reports of this in #drupal-support, couldn't reproduce myself.

tim.plunkett’s picture

Issue summary: View changes

Updated issue summary.

webchick’s picture

Status: Active » Postponed (maintainer needs more info)

Until we have steps to reproduce, we need more info.

LadyNeptun’s picture

I have this problem with the mollom-module.
I'm now using Drupal 7.7, but the problem was already there on 7.4 (when I first installed the module).

I can install und enable the module without any problems but I cannot configure it...

If there's anything I can do to help solving this problem just tell me.

smscotten’s picture

I've seen this now with both Administration Menu and Autolink. I'm on 7.7.

The only thing I can find in the logs are new "Deprecated function: Call-time pass-by-reference" messages, which I suspect to be unrelated. If so, it's just failing silently.

There is no entry for either the Autolink or Administration Menu config pages found in drupal_menu_links.

I do have the Mollom config pages, but I had Mollom installed on my 6.x site before I upgraded. That could be a significant difference.

I'll do more digging as I can.

smscotten’s picture

OK, this is really weird to me, but maybe it makes sense to someone else:

I saw this same thing happen when installing the Mediafront module. I've got no way to configure it. But now, somehow, Autolink's config pages appear just like they should. And it was nothing I (intentionally) did.

It's as though there's a queue for admission to the the admin interface and D7 is adding whatever is second-to-last rather than the most recent addition. That seems silly to me, but it's more information. Hope it helps.

smscotten’s picture

It gets weirder. Mediafront's config is now there and I haven't done anything to make that happen. I thought it could be a caching problem, but A) are admin pages cached? and B) I cleared the cache as soon as I saw that the config page wasn't where it was supposed to be. Oh, and C) a cache issue wouldn't keep a page from showing when accessing the address directly.

What could be causing the config pages' appearance to be delayed by over three hours? That seems excessive even for an INSERT DELAYED.

This just seems crazy. If I were reading this, I wouldn't believe me.

Oh, I was wrong. The config page didn't appear, just the icon and link to to config page from /admin/structure. /admin/structure/mediafront just shows /admin/structure. Still just as mysterious, but without the happy outcome.

RobAlex’s picture

Title: Module pages, menu paths, "Settings page missing" after module installation » Module pages, menu paths, "Settings page missing" after module installations in

I had this problem with several modules and it all cleared up when I cleared all the caches. Now they all work as supposed to. This included Mollom, Control Access, Google analytics, WYSIWYG. Clearing the cache also caused a mysteriously disappeared Body content to reappear.

NPC’s picture

I may have this problem on 7.8 with Ubercart - not the whole module, but some of its pages are not accessible (trying to go to admin/store/settings/products/edit/fields shows me contents of admin/store/settings/products/). I've raised the issue in Ubercart queue (http://drupal.org/node/1293402), but perhaps it is more relevant to core?

In any case, subscribing. If there is any log etc I can look into to help investigate it - please let me know.

bancarddata’s picture

I am on 7.7 and noticing this with ubercart. At first, I just noticed the "Store" menu not showing up on the admin_menu bar, but it would show up under /admin. Later, it disappeared from admin also and trying to go directly to /admin/store brought me to /admin. I will try upgrading Drupal core tonight to see if that helps.

I have been doing some module customizations lately and thought it might have to do with that - I have had sections of admin pages not show up consistently that were parts defined in the module I was messing with. In this case, it was the Ubercart Flat-rate shipping module. I had made a copy of it and modified it for a different purpose. For some reason, the little admin section that gets added to the quote settings page would not always show up. Also, on the node edit page, the single field settings section would disappear as soon as I defined some data in the field. If I deleted it directly out of the DB and clear caches, the field would show up again. So I figured it was something I did, but I could not find any mistakes in the module for the life of me. And the odd thing was, the same issues were showing up in the flat rate module, which I did not modify and others are using quite successfully. Furthermore, the module I did modify seemed to work other than the randomly disappearing admin elements.

Sorry to say I don't really have any valuable information to help solve this issue for those of us that it seems to be happening to. I am interested to see if this issue progresses and anything else that folks might post here.

sun’s picture

Another report in #1378578: A way to fix: API keys not configured issue which says

  1. this bug can be reproduced repetitively when installing Views module directly before the Mollom module.
  2. this bug does not occur when reversing the installation order; i.e., installing Mollom before Views module.

It's the first particular reference to Views, and I'm not sure whether that is relevant.

vonn.new’s picture

I'm having the same issue on Drupal 6.22, with Mollom 1.16 & Backup and Migrate. (these are the only 2 modules I've tried enabling since I've noticed the problem.

I tried disabling Views (and all its dependents), then enabling Mollom as this thread suggests, but that did not resolve it.

If I go to admin/by-module, Mollom shows up but only Configure Permissions and Get Help are available.
I'm logged in as admin.

This is a complex site with a lot of modules installed.
Please let me know what information I should provide to be helpful in tracking this down.

bluestarstudios’s picture

I don't even have Mollom installed and I have the same issue. Menu for admin/config/content/Wysiwyg doesn't exist. I'm on 7.10 Sorry. Turned out to be an incorrect initial installation of the entire system. Fixed.

rieraney’s picture

Version: 8.x-dev » 7.7

I'm having this issue with Mollom on D7.7. It happens on my production instance, but not dev or test who have all the same versions. For mollom the result is, of course, that I can't use the module - so it does seem critical in that sense. Some differences from the issue summary:

5.The users do NOT use drush. NO - I Do Use Drush

7.Some users are on Drupal 7.4 and some others on 7.6.- I'm on Drupal 7.7

Clearing cache DOES NOT help.

rieraney’s picture

Version: 7.7 » 7.12

Problem persists on 7.12. Still can't get to admin/config/content/mollum/settings - no mollum settings to be selected on that page. Interestingly, although my test and dev instances have same PHP, same Drupal version, same mollumn etc - it only happens on production. Test and Dev are fine.

shunshifu’s picture

Subscribing

rieraney’s picture

Finally resolved - seems to be related to menu cache problem. We had gotten to a point on production where we could no longer clear the menu cache - just white screen and never cleared them. Fix:
-- with backup and migrate, copied db to test machine
-- Did FULL restore from test, including caches, using mysql to redo database for production. This restored database with cleared menu caches - and mollum pages now come up. Still can't clear menu cache, so that problem persists, but at least it no longer affects mollum settings.

drdave17’s picture

Drupal 7.12 same problem even after clearing cache. Admin/Configure no mollon entry. Then from the reports page I only get "The Mollom API keys are not configured yet. "

sun’s picture

FWIW, I find it interesting that most (but not all) of the mentioned modules are mine or maintained by me ;)

That said, those modules definitely do not share any common parameters. That's why we need more information about your system environment, OS/platform, installed modules, themes, installation profile, and any other conditions.

vonn.new’s picture

Post # 17 gave me the clue I needed to fix this.
I cleared the menu and administrative menu caches and that solved it. I'm still a bit puzzled because I had cleared the overall cache before to no effect, but I'm just glad it's working now.

sun’s picture

Title: Module pages, menu paths, "Settings page missing" after module installations in » Module pages, menu paths, settings page missing after module installation

Reverting bogus title change.

sun’s picture

Issue summary: View changes

Updated issue summary.

Juppk1’s picture

Version: 7.12 » 7.17
Assigned: Unassigned » Juppk1
Status: Postponed (maintainer needs more info) » Active
FileSize
76.09 KB

Hello,

I am having a problem where i cannot see where to put the Api keys after installing mollom. I have uninstalled it and reinstalled it and still cannot put in the Api keys. Is this a bug? How can I fix it? I have attached a print screen of what I see when I go to the mollom settings page.

Many thanks.

webchick’s picture

Status: Active » Postponed (maintainer needs more info)

Once again, we need clear steps to reproduce this bug from a fresh Drupal installation in order to fix this problem.

Leonardo Gutierrez’s picture

I suffered a lot with this problem, but after reading some reviews I decided to try to clear the cache and disable / enable the module.

The cache emptied it in

admin / config / development / performance

After this worked Mollom module

MY installation was carried out in:

Commerce Kickstart (commerce_kickstart-7.x-2.8)

Leonardo Gutierrez’s picture

Issue summary: View changes

Updated issue summary.

RgnYLDZ’s picture

Issue summary: View changes

I have the same problem with Organc groups. After I enable OG modules some of my modules admin pages dissapear. They got redirected to the root admin page. To enable all modules again I have to disable and enable all modules again.

DrupalFrank’s picture

I've been struggling on and off in Drupal7 with menu cache issues when creating menus in custom modules over the past few years using hook_menu. Clearing the caches is clearly not enough. The only thing that works is uninstall and then reinstall the module(s) that create the menu entries.

This is a server-side issue; not browser side. The content of menu_tree_all_data("navigation") does not properly nest submenus into their parents if the parents already existed some time before the submenus were created. (E.g., If parent menu has link_path "a/b" then adding link_paths "a/b/s1" and "a/b/s2" should produce a submenu with s1 and s2 but after initial menu build it will not show changes; the "below" member of the "a/b" menu item will not contain new additions if you later update code to create item "a/b/s3" etc.)

Summary:

  1. Clearing all documented caches is NOT enough. (drush cc all --- not enough, performance page clear caches --- not enough, manually truncating the cache tables in db --- not enough)
  2. Uninstalling and then re-installing the module(s) that create the menus resets the menus to have the correct content.

Clearly something is being cached somewhere other than the official cache locations, but where I do not know.

philsward’s picture

Totally random suggestion, but check views. If you're overriding an admin page with a view (like admin views) it's possible the menu is disabled. I chased my tail for 2 hrs trying to figure out why "People" went missing and wasn't in the Management menu. It was as simple as adding the People to the view menu.

Version: 7.17 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.