By ErikaChristine on

Hello,

I recently have had 2 problems. First, my site seems to be creating nodes without me doing anything...particularly articles. If I go to content>find content I see a list of 10+ articles (all of which I did not create). If I delete all of these, they pop up again. Please help!

My second issue is that now when I go into my menu I get this error: Undefined index: access in _menu_link_translate, you can go to my site: www.erikacmaldonado.com to see.

Any help on this matter would be greatly appreciated.

Signed,

NOOB.

⋅ Categories: Drupal 7.x

Comments

microsoftpay.com’s picture

microsoftpay.com commented

ChakDeIndia.in

* Notice: Undefined index: access in _menu_link_translate() (line 911 of /home/{sitename}/public_html/includes/menu.inc).
* Notice: Undefined index: access in _menu_tree_check_access() (line 1445 of /home/{sitename}/public_html/includes/menu.inc).

ErikaChristine’s picture

ErikaChristine commented

Did you figure out the problem? I noticed your site is in maintenance mode, so I'm hoping you found a majestic fix :/

johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented

I was getting this same error on every page.

Then I went to admin/config/development/performance and hit the "clear all caches" button. And that fixed it.

  - John (JohnAlbin)

hakankahraman66’s picture

hakankahraman66 commented

I did "Flush All Caches", but nothing changed.
I first saw this messages after updating Views 7.x-3.x-dev (dated 2011-Mayıs-13)
I do not like to upgrade any modules because of their dependence problem somethimes occurs to lock my site.
So, I am going to wait for a short time.
If I get any good news I'll share with you.

Another problem which has not solved yet is
http://drupal.org/node/1118028

PDOException: in _menu_router_save() (line 3674 of /path/drupal/includes/menu.inc).
I wrote a post but I haven't got a reasonable info. to solve the problem yet.
This error fulls my log everday.

lafingguy’s picture

lafingguy commented

I got the same error message after using the migrate module for Drupal7 to copy my database to another developer's dev box.
Running the cache clear took care of the issue.

solartoasting’s picture

solartoasting commented

This fixed it for me. Worked great. Thanks

kamranzafar’s picture

kamranzafar commented

I was getting same error by flushing the cache error was resolved.

SimonEast’s picture

SimonEast commented

I was getting this error after I disabled the "Rules" addon module. It seems to be required by some other modules, even though the dependency isn't mentioned in the modules screen.

Re-enabled the "Rules" module and error went away.

akkawi’s picture

akkawi commented

in my case it was the entity Api after activating it, and before setting it too..

geriman’s picture

geriman commented

I got this warnings after removing a module directory from filesystem without disabling and deinstalling the module from drupal first (module name was "support").

luxosstudios’s picture

luxosstudios commented

Yep this worked for me also

damien_vancouver’s picture

damien_vancouver commented

I had this error as a result of a coding error in a hook_menu entry.

I accidentally put my 'access arguments' (permissions for the page) into the 'access callback' key, causing this error and others.

If you're developing and you suddenly start seeing this and you just added a menu item.. then check you didn't get them backwards.


  // wrong:
  $items['admin/config/system/my_settings'] = array(
     'title' => 'My settings',
      'page callback' => 'drupal_get_form',
      'page arguments' => array('my_settings_admin'),
      'access callback' => array('administer site configuration'),   // Incorrect!  This should be  function name!
  );

  // right:
  $items['admin/config/system/my_settings'] = array(
     'title' => 'My settings',
      'page callback' => 'drupal_get_form',
      'page arguments' => array('my_settings_admin'),
      'access arguments' => array('administer site configuration'),   // Correct - this is an argument
  );
jkurrle’s picture

jkurrle commented

Problem for me was similar, but it was because of using Git. It's a bit complicated, but worth the read for Git users.

When you use Git on a server and also clone the repository locally with the same login id, you cannot be checked into the server and the local at the same time. If you are, you cannot commit code remotely to the server. To get around this, you simply create a temporary branch on the server and checkout the branch, like thus:

Git checkout -b tmp

This creates a branch called tmp and checks it out, moving you off the master branch. After this, you can upload code to the server remotely.

The problem comes after uploading modules. When going to the Drupal setup to activate the modules, they aren't there. I had to checkout the master branch on the server to see the modules (git checkout master). After doing so, I could enable modules and use them. The problem came when I checked out the tmp branch I had created. After doing so, I'd see the error message in the lead post. This is because the tmp branch wasn't updated with all the new code, so there would be module errors.

To fix this, I check out the master repository on the server. I then delete the tmp branch by issuing the following command:

git branch -d tmp

Then, I recreate the tmp branch and check it out. tmp is updated with all the latest code, I don't see error messages, and I can continue to work locally and commit to the server. Just have to switch to master, delete the temp repository, recreate it and check back in.

Hope this helps someone.